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.

The problem :
Everything is ok when the memory is less than 1000mo, the nigth the memory is about 700mo.
In the day the problem started, the memory increases up to 1600mb, and then we have a lot error.

the problem occurs every day, especially in the morning when users open Thunderbird

There are well known limitations of 32bit programs like hmailserver. No idea when 64 bit will be made available. Generally hmailserver uses very little memory. Mine is normally no more than 120MB after months. But I have very few IMAP users & IMAP can definitely consume a lot of RAM especially if users have crazy amount of messages in INBOX and/or open very large emails (entire email must be read into memory). That is why I limit who can use IMAP & the size of messages and warn people who have too many in INBOX.

Your hmail logs should give you a hint as to what is going on at the time. You might need to split some users up between multiple servers to avoid it.
Bill

hMailServer build LIVE on my servers: 5.4-B2014050402#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

Hmailserver.exe was about 1.9go this afternoon. I wait 1 week, an see if errors occur again.

I think martin should put this flag before releasing the next version of hmailserver.

With this flag hmailserver can handle 4Gb memory, so the problem wil occur again in several year

Our users need to send large email, so I set the size limit of mail to 40MB. This increases the problem!

In the future there will be only 64bit OS.
I think it would be interesting to do a 64bit version and drop the 32bit version so that martin does not have 2 software to maintain.

Thanks for the info. Interesting that helps & more so that it does not cause problems. You can be the guinea pig.
The 64 vs 32 bit thing has been over so many times it's not even funny. Truth is 99.999% of hmail users have no need for 64bit hmail and there are many users who are still on 32bit so not like we could dump them. Obviously the day is nearing where we need to look harder at releasing a 64bit version of hmail as more people run into memory limitations. Let us know how your experiment goes & if you run into any problems. I'll look into what it takes to build that flag into hmail and post a special build.
Thx
Bill

hMailServer build LIVE on my servers: 5.4-B2014050402#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

hMailServer build LIVE on my servers: 5.4-B2014050402#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

hMailServer build LIVE on my servers: 5.4-B2014050402#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

Before april 17 : between 200 and 2000 error each days in logs, and I restart the service regularly!
april 17 : I tweak the hmailserver.exe with the flag LARGEADDRESSAWARE

After april 17 : 0 errors, 0 restart!

Max Working Set Memory : 2.6gb !!!!

That's good news. You sure there were no other issues such as memory corruption? Did you see I posted up a build with the large aware flag set during build?
Thx
Bill

hMailServer build LIVE on my servers: 5.4-B2014050402#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

I have been having hundreds of this " OutofMemoryHandler - hMailServer has run out of memory" Error
Any further advise or development on solving this problem or of using this back to enable /Largeadresssaware?

If your Mac Apple Mail clients have avast anti-virus, it cause MAJOR issues with memory consumption. Hmailserver will run out of memory, and lost emails, etc.
Now this was back in January 2016 that I discovered this. Maybe an Avast update has solved this I don't know.

I have verified 100% that Avast and Apple Mail causes hmailserver to run out of memory causing serious issues with hmailserver. It just takes ONE user with this to cause out of memory errors. Not sure why this is not stickied in the forum. Avira will work fine.

Martin has not fixed the issue that I know of (no new releases). I tried to contact him about it, but no success.

With about 100 users with HEAVY use (many large file attachments), I consistently get ~150-200MB mem usage. With ONE Apple Mail / Avast user It would quickly ramp up over 1GB and start causes issues. These users were on IMAP.

I never used hms as a production mailserver, but if a Windows program (like hms) calls an external program as child process, it can harm the parent process in many ways. So your observation makes sense and you need an Avast update or configure Avast as Service.

Dravion wrote:I never used hms as a production mailserver, but if a Windows program (like hms) calls an external program as child process, it can harm the parent process in many ways. So your observation makes sense and you need an Avast update or configure Avast as Service.

Avast sit between the Server and Client like a Proxy... No matter how well behaved your Client is, if your Proxy is dirty, your communication sucks and ressources are hogged from the server...

SørenR.

The quantum rule of insecurity which states that the act of observing how vulnerable a host or service is changes the insecurity level of the service.

Dravion wrote:I never used hms as a production mailserver, but if a Windows program (like hms) calls an external program as child process, it can harm the parent process in many ways. So your observation makes sense and you need an Avast update or configure Avast as Service.

I believe he's talking about this post. viewtopic.php?f=7&t=29081&p=183179#p182496
In that case, there's no other process running on hmailserver machine. hmailserver simply could not defend itself well from an ill behaved client.

Upgraded to 5.6. Got the same error message as OP recently. Checked windows server 2012 resource monitor memory tab, hmailserver used about 1GB under Commit and 300MB under Working Set.
A reboot of sever seems fixed it for more than 24hours, don't know when will it come back, currently used about 200MB under Commit and Working Set.
Still need to set the flag?
Thanks.

Upgraded to 5.6. Got the same error message as OP recently. Checked windows server 2012 resource monitor memory tab, hmailserver used about 1GB under Commit and 300MB under Working Set.
A reboot of sever seems fixed it for more than 24hours, don't know when will it come back, currently used about 200MB under Commit and Working Set.
Still need to set the flag?
Thanks.

Just checked with dumpbin /headers command. Looks like my hmailserver.exe doesn't have the lin 'Application can handle large (>2GB) addresses'
Is it safe to run editbin /largeaddressaware hmailserver.exe to set the flag? Any risk? Thanks.

I've not tried that, but then neither have I had need to.
That solution seems to have worked for others, butthen there is an alpha or two of hMailsever 5.7 about that you could try (although not recommended on a live system)

Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

I've not tried that, but then neither have I had need to.
That solution seems to have worked for others, butthen there is an alpha or two of hMailsever 5.7 about that you could try (although not recommended on a live system)