hMailServer 5.1, build 331 (Alpha)

[martin]

A new hMailServer 5.1 alpha is available:
http://download.hmailserver.com/dev/hMa ... 1-B331.exe

The following changes have been made.

• Core: The log setting Mask passwords in log has been removed - passwords are now always replaced with *** in the log.
• SMTP: A v= attribute is now added to the DKIM-Signature header.
• SMTP: In some (many) cases the DKIM signing was incorrect.
• WebAdmin: The log setting Keep files open has been added to the web interface (was added to hMailServer Administrator in v5.0).

I have tested this build successfully with the following DKIM reflectors. Have tested both simple and relaxed canonicalization and both SHA1 and SHA256.

• dkim-test (at) testing (dot) dkim (dot) org
• check-auth (at) verifier (dot) port25 (dot) com
• sa-test (at) sendmail (dot) net
• autorespond+dkim (at) dk (dot) elandsys (dot) com
• dktest (at) blackops (dot) org

[GlenC]

DKIM... all good for me now. Thanks Martin!

[bigcrawdaddy]

Working like a champ!!!!! Passed all test at all test sites. I have only one last question. LOL
Do I leave it in test mode?

[rjvrijn]

OK, installed without problems. Just curious, why you removed the mask passwords option?

[martin]

bigcrawdaddy,
I would definitively recommend that you leave it in test mode for a while. There are some strange things which I haven't had the time to look into yet. For example, some of the email I received does not pass DKIM-verification so I'm guessing there may be something wrong in the implementation. While this doesn't affect signing, the signing and verification uses the same algorithms so there may be something wrong in signing as well. (It could very well be that this is an error on their side since their domains are in test mode but I want to look into it).

rjvrijn,
Many companies does not trust their mail server administrator enough to give him access to end-user passwords. Also, admins sometimes posts log in the forum containing passwords. The idea is that if you as an administrator need access to end-user passwords, you're doing it wrong.

[Meister]

"The log setting Mask passwords in log has been removed - passwords are now always replaced with *** in the log"

Why?

In some cases it helped me a lot, when one of my stupid users called me.

[^DooM^]

Many companies does not trust their mail server administrator enough to give him access to end-user passwords. Also, admins sometimes posts log in the forum containing passwords. The idea is that if you as an administrator need access to end-user passwords, you're doing it wrong.

[mbach]

May I add the announcement of a wonderful feature:

As I just read in the archived feature list, you added support for changing the delimiter.

Thank you very much for that feature, Martin!!!
I will test it as soon as possible.

Cheers, Markus

[Meister]

Martin, my mania is the global, per domain limit, without per account limit setting. May you implement that? I know, you replied once me, that it would need more CPU, but I think, if I need this function, I could upgrade my server to use it.

[^DooM^]

Martin, my mania is the global, per domain limit, without per account limit setting. May you implement that? I know, you replied once me, that it would need more CPU, but I think, if I need this function, I could upgrade my server to use it.

And what about everyone else? Will you upgrade their servers too?

[Meister]

Martin, my mania is the global, per domain limit, without per account limit setting. May you implement that? I know, you replied once me, that it would need more CPU, but I think, if I need this function, I could upgrade my server to use it.

And what about everyone else? Will you upgrade their servers too?

If you could, please do it as an option. But I don't kknow why eat more cpu, if you check the current account limit, or the domain limit.

When a mail arrives, you insert a record to the messages table.
How do you check the limits?
I think:
select sum(messagesize) from hm_messages where messageaccountid= X

But, if you implemented my suggestion, you could add the size of actually received message to a new column in hm_domains table, or simple you can put a new column into hm_messages messagesaccountdomainid, which contains the domainID. (I know, it would be a kind of denormalisation!), and then you could summarise with this:
select sum(messagesize) from hm_messages where messagesaccountdomainid=X

[Meister]

Martin, my mania is the global, per domain limit, without per account limit setting. May you implement that? I know, you replied once me, that it would need more CPU, but I think, if I need this function, I could upgrade my server to use it.

martin: you have to know, this is a daily problem in our server, that my users ask me, why they need to set up limit per account, if they purchased from me a fix 1GB mail store.

[rjvrijn]

Martin,

A few differences in the Anti spam section between the hmailserver administrator and phpwebadmin:

In phpwebadmin:
The DKIM option is missing under the spam test tab.
The spam test tab is the thirth tab instead of the second in the administrator
Also the sorting in the spam test tab differs from that in administrator (check host in helo)
The last tab is named "tarpitting" while in the administrator it is named "Advanced"
(since there are only tarpitting related options tarpitting looks the best choise if you ask me

Ok, enough for now. Seeya

[^DooM^]

web admin is usually updated after alpha testing. too many changes taking place to keep updating the web admin as well.

[rjvrijn]

Ofcourse, why didn't I realized that?

Still, the tab tarpitting vs Advanced looks an old one to me. But I'll wait, I'll wait...

[andyp]

I am really looking forward to the autoban feature. In case a bot net tries to hack into the system different IPs are used. What about blocking the account login for a certain time? Or both for the first 5 tries the ip gets blocked and after 10 total times the account gets blocked?

[martin]

Yes, the auto-banning can be improved but it won't be extended more in 5.1. I can't recall having seen any user which have had large bot nets trying to log on the server using a lot of different IP addresses. I want to see how the 5.1-version works before I try to implement smart unnecessary features.

[andyp]

OK, how its implemented now will be very useful feature. Thank you.

[steve`]

Hi Martin,

after upgrading to 5.3 build 331 on my test machine I get the following error after downloading emails from a external POP3 Server:

"ERROR" 3932 "2009-02-25 16:50:27.195" "Severity: 3 (Medium), Code: HM5136, Source: TCPConnection::HandleRead, Description: An error occured while parsing buffer. Remote IP: (IP of the POP3 Server)"

Has this something todo with hmailserver or is it a problem with the External POP3 Server?

Thank you