Karma test always failed and can not get correct ip when using smtp tls mode

[Ovear Jiang]

Hello, I found that the karma test always failed which caused really low score to my client. I have check the log, but still not sure what happened, And i can only send a few(1-3) mail with my client(Foxmail and Mozilla Thunderbird).

Every time i send mail, the karma fails, and the score will decrease, the log only tell me "too bad karma".

The only log related karma is

2018-08-29 20:08:40.874926500 [INFO] [*] [karma] score: -8, good: 0, bad: 1, connections: 1, history: -1, awards: 086, asn_score: -13, asn_connections: 13, asn_good: 0, asn_bad: 13, msg:deny:dnsbl, fail:asn:all_bad

And i noticed a keyword "dnsbl", and i found a page describe that "Some mail servers will not accept mail from IP addresses with no rDNS/PTR record or a generic PTR record."[1]

It seems that poste will block all ip that didn't have a rDNS record? If this is correct, is there any way to turn off this feature, because many ip didn't have rDNS.

Secondary, poste can only get the gateway ip through SMTP 465 port.

Thanks.

[1]https://www.dnsbl.info/dnsbl-database-check.php

[Ovear Jiang]

After review log carefully, i found this problem caused by the dnsbl service. Due to my ip are listed in some dnsbl service, it will always decrease my score.

Poste use haraka's plugin to check dnsbl, which will search spamsources.fabel.dk and b.barracudacentral.org and spamcop.net at the same time.

May be Poste can tell admin that this ip has been listed in dnsbl, which will significant increase user experience. Meanwhile, may be there a better way to calculate karma.

[1]https://haraka.github.io/manual/plugins/dnsbl.html

[Scott MacDonald]

Easiest way to fix is to get your IP delisted.

As disabling the service will result in more SPAM being delivered to your server.

[Ovear Jiang]

Hi,

Yes, but how to fix the second problem?

Thanks

[Scott MacDonald]

Are you using version 2.0.15?

[Ovear Jiang]

Yes

[Scott MacDonald]

Are you running a software firewall on your VM? Is port 587 opened?

For email clients ... port 25 is usually blocked by ISP because ports 465 and 587 are to be used.

[Ovear Jiang]

Nope, i use docker default bridge network. And i can confirm that all the port that poste needs are open. I can manually set the port to 465 to reproduce it. Thanks.

[Scott MacDonald]

Manually set port on the client side.. to access poste.io?

[Ovear Jiang]

Manually to set 465(TLS) port for smtp on client side. It means force client to use TLS for smtp.

[Scott MacDonald]

And it doesn't work? Does 587 work?

[Ovear Jiang]

It works, but the server can only get the gateway(172.17.0.1)'s ip, the server will use that ip as all users' ip, But port 587 works fine.

[SB]

I don't know if this will help, but I recently set this up on an Azure VM server, and although the required ports were open, I had to request that SMTP traffic was allowed to flow over them for it to connect properly on anything other than 587.

https://blogs.msdn.microsoft.com/mast/2017/11/15/enhanced-azure-security-for-sending-emails-november-2017-update/

[Scott MacDonald]

If this is still an issue .. as indicated check with the VM provider to ensure they are not blocking any ports needed by Poste.io.

[SH]

Once you are using email client, you are required (well, not realy) to use port 587 or 465 AND authenticate - these ports do not use karma. For other cases please look at https://your-mailserver/admin/server/connection if your installation is working.