Download Latest 5.7 Release

[blandyuk]

I've been trying to find a release for hMailServer v5.7 beta, but there are no release packages on GitHub any more.

https://github.com/hmailserver/hmailserver/

Anyone know where I can download it? Or do I have to go through and compile it from source, (prefer not as cannot simply do from VS2019).

We are getting the "OutOfMemoryHandler - hMailServer has run out of memory, clearing caches." issue which was discussed on another thread, so I'm hopeful the latest v5.7 beta resolves it.

Thanks.

[gotspatel]

using any type of Apple iOS(crap) device??

Refer HERE

[blandyuk]

Perfect thanks that's what I needed. Mainly the builds here:

https://d-fault.nl/files/hMailServer-Builds

We have some users using iOS yes, hence the issue. I don't, Thunderbird all the way in Linux/Win.

[darkdude]

Any chance we get a 32 bit version?

[gotspatel]

Any chance we get a 32 bit version?

5.6.9 is 32 bit

[blandyuk]

Just an update for users upgrading from 32bit 5.6.9 to 64bit 5.7.x

Firstly, you need to uninstall the 32bit version, (this will not remove your Logs, Data or Events folders).

As the location of the installation changes from "C:\Program Files (x64)\hMailServer\" to "C:\Program Files\hMailServer\", you will be required to move the above folders manually, or if you have a custom location setup in hMailServer.INI, then remember to edit/update the .INI file after install, (remember to STOP the hMailServer service while making these changes. Start again once done).

NOTE: If you are moving a HUGE Data folder, I suggest doing this via command-line as faster. Doing via copy/paste in Windows will take forever! Example below via command-line, move is instant:

move "C:\Program Files (x64)\hMailServer\Data" "C:\Program Files\hMailServer\"

Do the same for the Log folder so you keep them, and remember to copy your "EventHandlers.vbs" script if needed.

I use MSSQL Server and told it to use an existing one, which it successfully found and updated, BUT when hMailServer started, the Log showed errors relating to EnableImapSASLPlain and EnableImapSASLInitialResponse being missing.

Found easy solution by running MSSQL script below, unsure why it did not do it thou:

Code: Select all

IF NOT EXISTS(SELECT settingname FROM hm_settings WHERE settingname = 'EnableImapSASLPlain')
INSERT INTO hm_settings (settingname, settingstring, settinginteger) VALUES ('EnableImapSASLPlain', 'none', 0);
GO

IF NOT EXISTS(SELECT settingname FROM hm_settings WHERE settingname = 'EnableImapSASLInitialResponse')
INSERT INTO hm_settings (settingname, settingstring, settinginteger) VALUES ('EnableImapSASLInitialResponse', 'none', 0);
GO

I also did the "5.7.0-B2643.17-OpenSSL-3.0.15-Experimental.7z" update which worked OK, but also remember to run the MSSQL.sql update on top of the above. So far, it seems to be working OK with no more "bad allocation" errors, but admittedly, this server is just a stepping stone for the main production server just to make sure we have no major issues with the update.

I'll let you know how that goes, as we have numerous iOS users using that one.

[jim.bus]

Just an update for users upgrading from 32bit 5.6.9 to 64bit 5.7.x

Firstly, you need to uninstall the 32bit version, (this will not remove your Logs, Data or Events folders).

As the location of the installation changes from "C:\Program Files (x64)\hMailServer\" to "C:\Program Files\hMailServer\", you will be required to move the above folders manually, or if you have a custom location setup in hMailServer.INI, then remember to edit/update the .INI file after install, (remember to STOP the hMailServer service while making these changes. Start again once done).

NOTE: If you are moving a HUGE Data folder, I suggest doing this via command-line as faster. Doing via copy/paste in Windows will take forever! Example below via command-line, move is instant:

move "C:\Program Files (x64)\hMailServer\Data" "C:\Program Files\hMailServer\"

Do the same for the Log folder so you keep them, and remember to copy your "EventHandlers.vbs" script if needed.

I use MSSQL Server and told it to use an existing one, which it successfully found and updated, BUT when hMailServer started, the Log showed errors relating to EnableImapSASLPlain and EnableImapSASLInitialResponse being missing.

Found easy solution by running MSSQL script below, unsure why it did not do it thou:

Code: Select all

IF NOT EXISTS(SELECT settingname FROM hm_settings WHERE settingname = 'EnableImapSASLPlain')
INSERT INTO hm_settings (settingname, settingstring, settinginteger) VALUES ('EnableImapSASLPlain', 'none', 0);
GO

IF NOT EXISTS(SELECT settingname FROM hm_settings WHERE settingname = 'EnableImapSASLInitialResponse')
INSERT INTO hm_settings (settingname, settingstring, settinginteger) VALUES ('EnableImapSASLInitialResponse', 'none', 0);
GO

I also did the "5.7.0-B2643.17-OpenSSL-3.0.15-Experimental.7z" update which worked OK, but also remember to run the MSSQL.sql update on top of the above. So far, it seems to be working OK with no more "bad allocation" errors, but admittedly, this server is just a stepping stone for the main production server just to make sure we have no major issues with the update.

I'll let you know how that goes, as we have numerous iOS users using that one.

I think you don't know the better way to do the 'move' of your Program Files (x86) data to Program Files data. But you didn't say how much data you are moving. You apparently used the Windows copy/paste function. yes that could take quite a while to copy. But you are 'moving' this data to the same Drive which 'cuts' out a lot of the time that copy/paste would take. You should use the Cut/Paste function as the data doesn't need to be 'copied'. With Cut/Paste the data doesn't physically move or get copied since you are 'moving' the data to the same drive. Only the directory entries change plus adjustments to permissions and other meta type data. You should probably of course have a backup of that data especially if it is quite large as you say but then you should've already had that data backed up to begin with.

Then you can make the appropriate .ini file entries if needed to point to the new 'location' (Directory entries) on the same drive. Furthermore if you had set up a custom location to begin with which was located outside of Program Files (x86) Folder, you wouldn't have had to 'move' anything and just change the .ini Folder Paths to point to the custom location. You could have even kept the data inside the same folder and only change the .ini location entries though I think it would be better to not keep that data within the Program Files (x86) or the Program Files Folders.

The same could have been done with you Log file entries as well.

[blandyuk]

Yes, I meant "move", not copy as this would be crazy on a huge data folder.

Command-line based "move" is quicker, unless you are moving to another drive. I don't have another drive on the server, so all runs on local drive.

Note that "moving" via cut/paste on Windows is crazy slow also on the same logical drive. It checks the whole file structure which can take a very long time if dealing with huge Data folder.

I suspect most users using hMailServer will have left the default folder location, thus will have this issue.

[jim.bus]

Yes, I meant "move", not copy as this would be crazy on a huge data folder.

Command-line based "move" is quicker, unless you are moving to another drive. I don't have another drive on the server, so all runs on local drive.

Note that "moving" via cut/paste on Windows is crazy slow also on the same logical drive. It checks the whole file structure which can take a very long time if dealing with huge Data folder.

I suspect most users using hMailServer will have left the default folder location, thus will have this issue.

Which is one reason why I would suggest not keeping the folders such as Data, Data Base, Event, Logs, etc. in a folder outside the Program Files Folders. The next time you do something which would require you to move these folders, you wouldn't have to move the folders. Yes I know most people probably would keep these Folders where the installer places them but I always found it a good idea to move these Folders elsewhere.

Another tip not necessarily for just email servers, is that you could (in the case of a single drive system), partition the C drive and then keep all your Data type Folders versus application folders on a separate partition from the C partition. This would mean if you ever had to restore your C partition (meaning Windows), then you wouldn't have to worry about possibly losing your Data Folders unless of course if the whole drive was lost but you could separately backup up your Data Folders on an external drive and the restoration should be easy even if these Data Folders were lost. I have multiple actual drives so I don't need to do partitioning but the concept is the same.

[DrmCa]

Yes, I meant "move", not copy as this would be crazy on a huge data folder.
Note that "moving" via cut/paste on Windows is crazy slow

Only if you mistakenly do copy/paste instead of cut/paste. Then it is about the same. Both use the same NTFS API.

[RvdH]

Just an update for users upgrading from 32bit 5.6.9 to 64bit 5.7.x

Firstly, you need to uninstall the 32bit version, (this will not remove your Logs, Data or Events folders).

As the location of the installation changes from "C:\Program Files (x64)\hMailServer\" to "C:\Program Files\hMailServer\", you will be required to move the above folders manually, or if you have a custom location setup in hMailServer.INI, then remember to edit/update the .INI file after install, (remember to STOP the hMailServer service while making these changes. Start again once done).

NOTE: If you are moving a HUGE Data folder, I suggest doing this via command-line as faster. Doing via copy/paste in Windows will take forever! Example below via command-line, move is instant:

move "C:\Program Files (x64)\hMailServer\Data" "C:\Program Files\hMailServer\"

Do the same for the Log folder so you keep them, and remember to copy your "EventHandlers.vbs" script if needed.

I use MSSQL Server and told it to use an existing one, which it successfully found and updated, BUT when hMailServer started, the Log showed errors relating to EnableImapSASLPlain and EnableImapSASLInitialResponse being missing.

Found easy solution by running MSSQL script below, unsure why it did not do it thou:

Code: Select all

IF NOT EXISTS(SELECT settingname FROM hm_settings WHERE settingname = 'EnableImapSASLPlain')
INSERT INTO hm_settings (settingname, settingstring, settinginteger) VALUES ('EnableImapSASLPlain', 'none', 0);
GO

IF NOT EXISTS(SELECT settingname FROM hm_settings WHERE settingname = 'EnableImapSASLInitialResponse')
INSERT INTO hm_settings (settingname, settingstring, settinginteger) VALUES ('EnableImapSASLInitialResponse', 'none', 0);
GO

I also did the "5.7.0-B2643.17-OpenSSL-3.0.15-Experimental.7z" update which worked OK, but also remember to run the MSSQL.sql update on top of the above. So far, it seems to be working OK with no more "bad allocation" errors, but admittedly, this server is just a stepping stone for the main production server just to make sure we have no major issues with the update.

I'll let you know how that goes, as we have numerous iOS users using that one.

I think you also will be missing the 'ImapMasterUser' db entry with the upgrade path you have chosen, not?

[RvdH]

https://github.com/hmailserver/hmailser ... SSQLCE.sql

Code: Select all

IF NOT EXISTS(SELECT settingname FROM hm_settings WHERE settingname = 'ImapMasterUser')
INSERT INTO hm_settings (settingname, settingstring, settinginteger) VALUES ('ImapMasterUser', '', 0);
GO

FYI, ImapAuthAllowPlainText is NOT used anywhere, it shouldn't exist