Alas, I spoke too soon. It wasn't a real return address which got added to my whitelist after all... here's what happened:

1) Got a spam apparently from [EMAIL PROTECTED]

2) TMDA sent a challenge to that address

3) The mail daemon replied to the "Reply-to" and not the envelope

This hasn't happened to me before. Is there a good way to avoid this happening again? In other words "how can I detect forged email addresses and not send challenges to them?" or "How can I detect a bounce sent to the reply-to instead of the envelope and have TMDA not even consider those for releasing a message?"

Here are some relevant headers from the bounce itself:

Return-path: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
Subject: Undeliverable: Returned mail: see transcript for details
Message-id: <[EMAIL PROTECTED]>
X-Loop: [EMAIL PROTECTED]

Do you think I can reliably filter on any of that stuff to detect "bad" bounces?

Furthermore, is there an RFC I can quote to the site admin for that bad daemon telling him/her to reconfigure to reply to the envelope instead of reply-to?

--
Jim Ramsay

_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users

Reply via email to