Use this forum if you have installed hMailServer and want to ask a question related to a production release of hMailServer. Before posting, please read the troubleshooting guide. A large part of all reported issues are already described in detail here.

we're using hms 5.3.2 with SpamAssasin on the same machine.
Following appeared several times and randomly:

hMailServer stopped fetching SOME external mails from one single account via POP3. But he stopped not generally fetching. Half of the messages of this single account were fetched and other accounts were not affected. This appears randomly. Another time all accounts were affected, sometimes only some accounts are affected. Sometimes the pop3connector was generally dead, sometimes some external mails came through. Internal delivery was never affected.

^DooM^ wrote:someone mentioned issues with large headers which has yet to be investigated fully.

Yeah, I remember to have read something like this in the forum.... or the issue tracker?! Before I switch on debug logging which makes my server busy it would be nice to be able to examine the description of the known issues more closely. Do you have a link? I haven't found anything...

Good idea regarding the external webmailer. Yes, I have access. I'll definitely try this the next time and analyse the email.

But there're some things that make me believe the header problem isn't the problem:

1. The last successful attempt to fetch external mail had the result of 0 messages. After this no further attempts were made. Before this attempt the result was also 0. This means there was no email with a long header which could cause this problem.
2. After the user recognized that he wasn't able to receive external mail, I did a simple "net stop/start hmailserver" and the messages were all fetched. If it had to do with the header of an email catching this mail wouldn't furthermore be possible, would it?

It seems to be more like a dead timer thread or a wrong read or unread property for this account...

Or do you know from experience that it nevertheless could have to do with the header problem?

hmmm... without reason... I could imagine a reason. The day the problem appeared I now know for sure that there have been connectivity problems to the internet. Possibly the fetching thread for this account got stuck because of a lost IP connection. A lost connection can happen always, so this shouldn't lead to a misbehaviour... but...

Within this context: What's the best log to activate? Debug logging or application?

Depends how busy your mailserver is. I would suggest application for the moment. If it happens again, check logs for last successful check and see if anything useful in there. If not, switch to debug. I know it's not ideal but it's not the sort of thing easy to replicate.

If at first you don't succeed, bomb disposal probably isn't for you! ヅ

Checked the performance, is OK. Logfiles are zipped every night, so... debug logging would be OK... I hope I miss no information with debug logging. I assume debug logging is just more verbose than application?