Wietse Venema wrote:
Sean Reifschneider:
On 03/24/2010 10:36 AM, Randy wrote:
EX:
<r...@theholycat.com>: Sender address rejected: Domain not found (in
reply to RCPT TO command))
I'd be tempted to set up a milter or policy filter that for each rcpt
would connect to the Exchange server (assuming that's where it's destined)
and see if that server will accept it. There's probably a better way to do
it, but that's what comes to my mind.
You could also use Postfix's built-in recipient address verification feature.
http://www.postfix.org/ADDRESS_VERIFICATION_README.html#recipient
Wietse
The recipient is a real recipient. The m$change server is rejecting on
on the sender domain part, where the postfix setting
"reject_unknown_sender_domain" does not fit here since these domains do
have a MX record. The problem really boils down to determining what
criteria m$change is using to reject the sender domain. Keep in mind
that these mails are spam.
dig theholycat.com MX
;; ANSWER SECTION:
theholycat.com. 600 IN MX 20 mail13.theholycat.com.
dig mail13.theholycat.com
;; ANSWER SECTION:
mail13.theholycat.com. 589 IN A 208.43.143.111
dig -x 208.43.143.111
;; ANSWER SECTION:
111.143.43.208.in-addr.arpa. 3600 IN PTR
208.43.143.111-static.reverse.softlayer.com.
Forward and reverse do not match for the mail server, and I think I am
seeing "unknown" regarding the connection ip because of this. Should I
look into rejecting on these grounds? Or is that, to intrusive and
subject to false positives?
Note: We are rejecting many because of the
"reject_unknown_sender_domain" but not all.
Thanks,
Randy Ramsdell
