Are you providing a list of locally hosted domains with the
local-domains-file or local-domains-entry options? The
reject-missing-sender-mx filter will not function without a list of
local domains.
-- Sam Clippinger
r...@comunica2.net wrote:
Faris,
it is confirmed that your idea was
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
: 07 August 2009 09:13
To: spamdyke-users@spamdyke.org
Subject: [spamdyke-users] Testing DNS tests
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
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.
___
...@comunica2.net
Sent: 07 August 2009 16:13
To: spamdyke users
Subject: Re: [spamdyke-users] Testing DNS tests
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