Mails rejected as spam false-positive

[buddeel]

Hello!

We have a mail-Monitoring-Service from mxtoolbox.com which send uns mails from ip 208.123.79.59. These are blocked, because hostkarma.junkemailfilter.com said - its listed.

Here the result from Hostkarma:

Code: Select all

Looking up Reverse DNS for IP Address: [208.123.79.59]

RDNS for 208.123.79.59 is: [outbound-a2.mx-route.com] - (PTR record - 59.79.123.208.in-addr.arpa)
IP Address for outbound-a2.mx-route.com is: [208.123.79.59]
SUCCESS! - Forward Confirmed Reverse DNS is CORRECT!
The IP address for the reverse lookup name matches the original IP

and

Code: Select all

IP address 208.123.79.59 returned DNS result code 127.0.0.1.
208.123.79.59 is White listed - This is a good listing!
White listing means that we pass email from 208.123.79.59 without any further testing.

Logentry:

Code: Select all

2016-01-29 17:22:10 magicspam-daemon[390]: SPAM[block_rbl_lists (hostkarma.junkemailfilter.com)]: mua=no,ip=[208.123.79.59:outbound-a2.mx-route.com],helo=<outbound-a2.mx-route.com>,from=<monitor@tools.mxtoolbox.com>,rcpt=<mailflow@tt#########>

What's going wrong here?

Greetings from Germany
Thomas

[magicspam]

Hello Thomas,

Thank you for your post.

The custom RBL support in MagicSpam only supports two return values - listed or not listed.

This list appears to have its own system for returning the status of entries based around the localhost address;

127.0.0.1 = whitelisted
127.0.0.2 = blacklisted

and so on, but as far as MagicSpam is concerned, it received a reply and the address is therefor listed and should be blocked.

Until there is a widely adopted standard for these alternative return values, we do not have the ability to implement custom interpretation rules for every possible RBL out there.

That said, you should be able to add a Sender IP White List entry in MagicSpam for 208.123.79.59 that will accept the message before any RBL check.

Please let us know if that information helps or if you have any further questions.