hMailServer 5.7

Use this forum if you want to discuss a problem or ask a question related to a hMailServer beta release.
Post Reply
User avatar
martin
Developer
Developer
Posts: 6834
Joined: 2003-11-21 01:09
Location: Sweden
Contact:

hMailServer 5.7

Post by martin » 2014-12-11 18:47

Just an updates on things which will be included in hMailServer 5.7.
  • Reduced memory usage in large installations.
  • 64-bit support (there will be two separate installations, one 32-bit and one 64-bit). This will also help with high-memory scenarios in large installations since it will be able to consume any memory available.
  • SQL Compact Edition upgraded to 4.0 SP1 (this was required for 64bit support). This version can be used for commercial hosting (which the previous could not according to license agreement)
I'm still working on these things and I'm sure there will be more stuff coming, but this is at least what I'm up to now. The current builds are very very unstable, because I'm still fixing stuff related to the x64 support, so I suggest you don't install those builds now. :)
Martin Knafve
martin@hmailserver.com
https://twitter.com/knafve

bcpaul
Normal user
Normal user
Posts: 31
Joined: 2014-07-17 23:32

Re: hMailServer 5.7

Post by bcpaul » 2015-12-09 19:46

Any updates on the 5.7 release date? I keep running into 1.7GB memory limit errors. I will (sadly) have to switch software if I cannot resolve this soon.

Thanks.

User avatar
Dravion
Senior user
Senior user
Posts: 1688
Joined: 2015-09-26 11:50
Location: Germany
Contact:

Re: hMailServer 5.7

Post by Dravion » 2015-12-12 16:12

Hi Martin
We missed you allready, glad to see you :)
It would be awsome if you could create a Stable AND a Development branch at GitHub for hMailserver.In the Development Branch we can enque the patches and fixes while the Stable branch stays untouched until the Development branch matures and becomes a ready Release quality. The Devbranch would be the Ideal place to merge/reject the enqueded HMS-Community and Thirdparty patches and fixes.

Development and Release builds
As you may allready know, on GitHub it is possible to upload the compiled Binaries in a
extra Section called "Releases" (take a look at my GitHub page https://github.com/Dravion/hmailserver/releases ) here are the GitHub Description for the Release Feature: https://github.com/blog/1547-release-your-software It would be awesome if you could upload your used Libboost and OpenSSL shared Libraries and resource files) to the Release section on Github to, to steamline the Setupprocess for a new Developementsystem (i think we need both
Win32/x64 Debug AND Release Binaries of your compiled, shared libs).

OpenSSL-Path
I noticed there is a hardcoded folder path to the openssl libs inside the solution file and if
you build hmailserver.exe with a more recent version of openssl you run into unresolved linker errors
and other nasty situations. Can you change the path from c:\dev\libraries\openssl-x.x.123
to just c:\dev\libraries\openssl\ ?

PS:
I think a automated Sourcecode Documentation Tool like Doxygen would be great enhancement for
Developers http://www.stack.nl/~dimitri/doxygen/manual/index.html

All the Best,
Dravion

User avatar
jimimaseye
Moderator
Moderator
Posts: 8680
Joined: 2011-09-08 17:48

Re: hMailServer 5.7

Post by jimimaseye » 2015-12-12 19:53

Hi Martin
We missed you allready, glad to see you
You do know that his post was 1 year ago?
5.7 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

User avatar
Dravion
Senior user
Senior user
Posts: 1688
Joined: 2015-09-26 11:50
Location: Germany
Contact:

Re: hMailServer 5.7

Post by Dravion » 2015-12-13 01:26

jimimaseye wrote: You do know that his post was 1 year ago?

Arrrrgggh! A Trap :wink:

User avatar
martin
Developer
Developer
Posts: 6834
Joined: 2003-11-21 01:09
Location: Sweden
Contact:

Re: hMailServer 5.7

Post by martin » 2016-01-01 22:29

Dravion,

There already is separate branches for stable and dev branches. Take a look at the branch section.

The master branch is unstable (version 5.8 or 6.0).

5.7.0 contains the version which will be 5.7.0, for example. Same applies to other versions. They are listed here:

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

I'm not sure what hardcoded path you're referring to. The project file uses a environment variable (hMailServerLibs). This is described in the readme in the github acocunt.
Martin Knafve
martin@hmailserver.com
https://twitter.com/knafve

User avatar
martin
Developer
Developer
Posts: 6834
Joined: 2003-11-21 01:09
Location: Sweden
Contact:

Re: hMailServer 5.7

Post by martin » 2016-01-02 16:33

Just as an example, here's the changes for 5.7.0. When that version is released as stable, then no more commits are made to it, and the changes in the branch is merged into 5.7 and master.
https://github.com/hmailserver/hmailser ... mits/5.7.0
Martin Knafve
martin@hmailserver.com
https://twitter.com/knafve

User avatar
Dravion
Senior user
Senior user
Posts: 1688
Joined: 2015-09-26 11:50
Location: Germany
Contact:

Re: hMailServer 5.7

Post by Dravion » 2016-01-06 10:00

Hi Martin,
Awsome. But how can i submit a patch to the unstable/dev branch so you can pull the code, review it and merge it into the unstable/dev branch? Right now, i forked your hms repo and publishing my own 32/64-Bit UTF-8 builds on Github (see https://github.com/Dravion/hmailserver/ ... 6.4-B2283u ) but i think this doesnt help the project very much. A little howto on submitting patches to the Github for me and other programmers would be verry cool :wink:

Features and Patches
Right now my understanding of the development process is, thadt new features will only be accepted as part of a pre-planned feature Request for comments period (RFC). If the RFC vote period is over, a officual document about the upcomming features is published by you so anybody knows whats we can expect in upcomming version, is this correct?

Ps:
It would be very cool if a official todo programming task list would exist so i just can pickup a task, nail it down, test and finally submit the patch into the official hms github patch que where you can review
and merge the code if anything is ok.

Post Reply