I now repeatedly see SPAM from a source that has no MX record in their
rDNS domain and they apparently know how to by-pass greylisting.
I decided to follow the example in this mailing list and used telnet
mailserver 25 to test my server.
I started with all DNS Tests active and first I got
It is OK -- it is working as it should be.
The no MX test applies to the domain of the email address in the From:
address in the header of the received email and not the rdns-resolved domain
of the IP address used to connecting to your mailserver.
e.g. if you are connecting from
Faris, I doubt that what you wrote is true.
The “no MX” test applies to the domain of the email address in the
“From:” address in the header of the received email and not the
rdns-resolved domain of the IP address used to connecting to your
mailserver.
1. From addresses are faked in SPAM
Faris,
it is confirmed that your idea was wrong. I used a fake mail from in
telnet, l...@sflie.com. The domain doesn't exist and therefore has no MX
record and still Spamdyke permits the smtp session.
This looks more and more like a bug to me.
___
From spamdyke.org docs:
reject-missing-sender-mx Check the domain name of the sender's email address
for a mail exchanger (an MX or an A record). If neither are found, reject
the connection.
Maybe you had authenticated for this test, in which case it would be let
through?
It definitely
