On Tue, 28 Feb 2006, Seth Goodman wrote:
I remember that you had a case where one of your customers corresponded
to a brain-dead MTA that did CBV's on your mail using a RFC822 address
instead of MAIL FROM. For some reason, rejecting after DATA caused
their CBV to pass, while rejecting after RCPT TO caused it to fail.
Well, it's already broken. Couldn't you just whitelist that bad boy and
assume other MTA's are run by sentient beings?
The problem is building 15 gazillion whitelists for various creative
forms of braindamage. I had a similar problem doing EDI with the
airlines. Each airline had weird bugs/extensions in their EDI software.
So, for instance, Lufthansa required you to send dimensional weight
on an FAWB or they would reject it. But they only accepted an
earlier syntax level that did not support dimensional weight - a
classic catch 22 (you had to use a proprietary format for dimensional
weight that was not recognized by any other airline). So that, and 20
other bugs for other airlines, each got their own flag in an AIRLINE.QUIRKS
table.
So I need to organize all these MTA quirks in a general table, by both
MFROM domain and HELO domain (and perhaps IP). This information would
be useful for other mail filter projects, so some way to make it
generally useful is a plus. Is such a table already available?
I would likely use sendmail access file format.
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
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.
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com