-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stuart D. Gathman wrote:
On Wed, 1 Mar 2006, Julian Mehnle wrote:
Stuart D. Gathman wrote:
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?
Without commenting on the other issues, this seems just plain wrong to
me. We (there is no "we") shouldn't keep BCP documents for how to best
work around standards incompatibilities in various software, or things
will go the "browser wars" way. That way lies madness. If some
software behaves odd, we should file bug reports or stop cooperating
with it.
So, how do I explain to my clients that they can't send email to Verizon
because Verizon is "braindead"? And why should every developer have to
kludge together a workaround independently?
Have you tried sending a bug report to Verizon and asking them to fix it?
And wouldn't being on an official list of "braindead" ISPs put some
public relations pressure (the only kind they understand) on Verizon to
actually fix it?
Ok, I can see that it might be necessary to resort to that kind of pressure
to get the Verizon bug fixed. But I don't subscribe to the idea of
working around Verizon's bugs _just_ because they are unwilling to move
their ass. If such a work-around-braindead-organizations'-bugs list
serves more to exerting pressure on them than to actually compensating
their ignorance, then I agree.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFEBap0wL7PKlBZWjsRApueAJ9guIfAh7G6b7ew3YKDsC/dZn4m6QCfdvgQ
hlm1mmZTNgoG5DbC7yh4/vI=
=K/WC
-----END PGP SIGNATURE-----
-------
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