hMailServer 4.3, build 229
hMailServer 4.3, build 229
This build tries to address the problem with randomly stopping SMTP servers. I have been able to reproduce the problem myself and think I've found the problem that caused it.
Build available here:
http://dev.hmailserver.com/hMailServer-4.3-B229.exe
Build available here:
http://dev.hmailserver.com/hMailServer-4.3-B229.exe
Last edited by martin on 2006-08-22 08:20, edited 5 times in total.
It's not solved yet.. for sure...
I've simulated hundreds of thousands of conenctions without getting the problem now, but I had to rewrite some central parts of the code to get it to work so I might have introduced a new issue. But now I think I got a complete picture of how it works. Even those parts left out in Microsofts documentation..
And yes, for a few minutes now and then I've felt like giving up on this issue and revert the code. But after resting for a few hours and coming to my senses again, I've started working on it again. =)

And yes, for a few minutes now and then I've felt like giving up on this issue and revert the code. But after resting for a few hours and coming to my senses again, I've started working on it again. =)
Re: hMailServer 4.3, build 229
After testing B225 briefly with only 1 domain and I did not encounter the SMTP problems, I decided to update to this build today on my real server with several domains. The upgrade was very smooth.martin wrote:This build tries to address the problem with randomly stopping SMTP servers. I have been able to reproduce the problem myself and think I've found the problem that caused it.
Build available here:
http://dev.hmailserver.com/hMailServer-4.3-B229.exe
Martin, thank you very much for all hard work.
The main reason for me to upgrade are the new features for the distribution list and spamming. I would like to get rid of the messages with invalid line endings so I unchecked the line "Allow incorrectly formatted line endings" in SMTP tab.
I also saw the next line saying "Disconnect client after too many invalid commands". I do not understand the meaning as well as why the default max number of invalid is set to 100. Can somebody explain to me what invalid commands are?
Thank you.
Ah, I see. You probably refer to the folowing messages in the logAldoir wrote:I'm not sure, but I think it is to prevent spammers to do brute force attacks against your SMTP server trying to discover addresses..
I think this number should be lower by default, eg 10 times, and plus black list its IP address for at least 1 min
SENT: 550 unknown user <name1@yourdomain.com>
SENT: 550 unknown user <name2@yourdomain.com>
...
And yes, there are a few in my log. One sender is looking to send to a bunch of invalid names.
I will turn it on.
Thanks.
Was trying to do an install on a machine at work and while building the database (external MySQL) it came up with an error (and sorry I don´t have the exact wording here) to the effect of "The specified key was too long, MySQL limits the length to 1000 bytes". I couldn´t go any further with the database creation, although it did appear to be created. Not sure why this error because I went back to a stable build and it installed with absolutely no problems (I had tried a clean install with the alpha two times with the same results). Anyway, sorry there isn´t more info but just thought I better post this. Oh, and this was on a W2003 server with MySQL 5.0.19.
I got a strange error with B229. Yesterday I telnet from the outside to send mail manually for quick testing the ASSP greylisting feature. The message format is not correct because lack of headers.
Then when I checked mail with MS Outlook, it always stopped in between with the message
Task 'MyMail - Receiving' reported error (0x800CCC0F) : 'The connection to the server was interrupted. If this problem continues, contact your server administrator or Internet service provider (ISP). The server responded: +OK 487 octets'
I scratched my hair until I used WebMail and saw ill-formatted message. When I moved that message out of Inbox fokder, then I could get mail.
Not sure if that a bug in Hmailserver or MS Outlook. I think probably Outlook because WebMail (squirell) works OK.
Martin, in case you want, I can send the bad message to you for checking.
Cheers.
Then when I checked mail with MS Outlook, it always stopped in between with the message
Task 'MyMail - Receiving' reported error (0x800CCC0F) : 'The connection to the server was interrupted. If this problem continues, contact your server administrator or Internet service provider (ISP). The server responded: +OK 487 octets'
I scratched my hair until I used WebMail and saw ill-formatted message. When I moved that message out of Inbox fokder, then I could get mail.
Not sure if that a bug in Hmailserver or MS Outlook. I think probably Outlook because WebMail (squirell) works OK.
Martin, in case you want, I can send the bad message to you for checking.
Cheers.
Yeah, please send it to me at martin@hmailserver.com so that I can have a look at it.
Hi,
I don't know if that is important (maybe it's not).
Got a (for me) strange error log yesterday:
"ERROR" 3760 "2006-08-19 18:51:10.890" "Source: MimeBody::LoadFromFile, Code: HM4228 Description: An error occured while loading message. File: C:\Programme\hMailServer\Data\{E62F5CDB-7436-4C33-A3D6-3A238C0F6075}.eml"
But that file doesn't exist anymore.
I don't know how to find that message and check it.
Database delivery log was off, sorry.
cu
random
I don't know if that is important (maybe it's not).
Got a (for me) strange error log yesterday:
"ERROR" 3760 "2006-08-19 18:51:10.890" "Source: MimeBody::LoadFromFile, Code: HM4228 Description: An error occured while loading message. File: C:\Programme\hMailServer\Data\{E62F5CDB-7436-4C33-A3D6-3A238C0F6075}.eml"
But that file doesn't exist anymore.

I don't know how to find that message and check it.
Database delivery log was off, sorry.
cu
random
Nope, there is no file named "{E62F5CDB-7436-4C33-A3D6-3A238C0F6075}". Sorry.martin wrote:Perhaps you can find the message if you search the sub folders for it.
But I use the forwarding-feature (with "keep original message"). Maybe that was a forwarded message?
And I have to confess that I did send about 4.000 mails from that instance of hMailServer (B229) to another hMailserver (B199) using that forwarding-feature of B229, just to try something out.

cu
random
Edit: The other instance of hMailserver (B199) does not show any error log.