HMailserver as Backup-MX - and another HMS with ASSP
Posted: 2014-01-30 16:22
Hello Bill,
again me who needs your advice!
Maybe you remember our discussion from last year about hMailServer and ASSP and the Problem of "MaxAuthErrors" etc.
You had a nice solution and it works well.
Now I set up another configuration:
Server 1 with public IP xxx.yyy.zzz.59 running HMS and listening on port 25 - configured as an Backup-MX
Server 2 with public IP xxx.yyy.zzz.60 running ASSP listening on port 25 and HMS listening on port 2525.
I think the Server 1 is now (with your help and after discovering the SEP/clamAV-Problem etc.) well configured and worked without any problems with the old HMS on Server 2 (without ASSP).
I set up Server 2 like discussed some month ago:
ASSP listens on port 25 and forwards incoming messages to HMS on the same machine to port 2525.
I edited the assp.pl in AASP 2.3.3 like adviced:
Changed line:
to:
and added the following lines to the eventHandler.vbs:
.
As far as I can see after just one day running this configuration is fine as long as just the main-server 2 is involved.
But if mails were routed through the Backup-MX on Server 1 to port 25 (ASSP) of the main server 2 all mails are rejected getting back the following information:
What did I wrong?
Greetings from Germany again!
Gruenie
again me who needs your advice!
Maybe you remember our discussion from last year about hMailServer and ASSP and the Problem of "MaxAuthErrors" etc.
You had a nice solution and it works well.
Now I set up another configuration:
Server 1 with public IP xxx.yyy.zzz.59 running HMS and listening on port 25 - configured as an Backup-MX
Server 2 with public IP xxx.yyy.zzz.60 running ASSP listening on port 25 and HMS listening on port 2525.
I think the Server 1 is now (with your help and after discovering the SEP/clamAV-Problem etc.) well configured and worked without any problems with the old HMS on Server 2 (without ASSP).
I set up Server 2 like discussed some month ago:
ASSP listens on port 25 and forwards incoming messages to HMS on the same machine to port 2525.
I edited the assp.pl in AASP 2.3.3 like adviced:
Changed line:
Code: Select all
if ($MaxAUTHErrors && $AUTHErrors{$ip} >= $MaxAUTHErrors) {
Code: Select all
if ($MaxAUTHErrors >= 999 || ($MaxAUTHErrors && $AUTHErrors{$ip} >= $MaxAUTHErrors)) {
Code: Select all
'Block AUTH'd from ASSP IP
If (oClient.IPAddress = "xxx.yyy.zzz.60" And oClient.Port = "25" And oClient.Username <> "") Then
Result.Message = "AUTH FAILED. You must be authenticated to send."
Result.Value = 2
EventLog.Write("ASSP AUTH attempt rejected:"+Chr(34)+vbTab+oClient.IPAddress+vbTab+Chr(34)+oClient.Username)
End If
As far as I can see after just one day running this configuration is fine as long as just the main-server 2 is involved.
But if mails were routed through the Backup-MX on Server 1 to port 25 (ASSP) of the main server 2 all mails are rejected getting back the following information:
If I route the mails from the Backup-MX on Server 1 to the port 2525 (HMS) bypassing ASSP on port 25 all is fine.The following recipient(s) could not be reached:
webmaster@domain.com
Error Type: SMTP
Remote server (xxx.yyy.zzz.60) issued an error.
hMailServer sent: AUTH LOGIN
Remote server replied: 521 ASSP.nospam does not accept mail - closing transmission - too many previouse AUTH errors from network xxx.yyy.zzz.0
What did I wrong?
Greetings from Germany again!
Gruenie