stuart at bmsi
Jan 14, 2007, 9:29 PM
Post #2 of 6
On Mon, 15 Jan 2007, Chris Sweeney wrote:
> OK I have to ask for help now. I have a user that is unable to send
> email because of what I consider broken call back. When this particular
> place does call back its coming from a real email address instead of a
> <> null address. In this case when you send email to
Yup. That is real broken. Unclear on the concept, even.
> something [at] epronar it calls back with
> sender_verification [at] sandiegort Is there away to get around this
> broken call back problem?
Pymilter has a feature to work around such braindamage. It is called
banned_users, and whenever the local part is one of the banned_users,
the MAIL FROM is considered equivalent to <>, including requiring
a valid SRS sig in RCPT. I usually include 'postmaster' in the
banned_users, and you would include 'sender_verification'. Of course,
this means that postmaster [at] anydomai can't send me email directly.
This is usually not a problem because postmaster is normally redirected to
some other user, who responds from that account.
self.is_bounce = (f == '<>' or t.lower() in banned_users)
'Banned_users' is maybe not the best name for the config option, but
that is in effect what it does.
Stuart D. Gathman <stuart [at] bmsi>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1129