Bradon tells me he's unsubscribed, and asked what was broken.
FYI, I did email him the last time this happened, *as well as* the folks
the broken autoresponder said to email*.
But the same, still-broken auto-responder was used again. It's broken
because it violates several suggestions in RFC 3834. 3834 has several
suggestions that will keep autoresponders from sending mail to mailing
lists. IN ADDITION, spamcop.net clearly explains what's wrong with
Bradon's auto-responder via a prominent link on their home page to
http://www.spamcop.net/fom-serve/cache/329.html
Still, yeah, I overrreacted a bit. We don't want to ban Paul Judge...
Case closed.
*To: bradon(_dot_)rogers(_at_)ciphertrust(_dot_)com, mark(_at_)ciphertrust(_dot_)com,
akuehn(_at_)ciphertrust(_dot_)com
Subject: Re: [Asrg] Collaborative real time spam blocking
References:
<DAB35AC199E7D14BAF265C1D188583687A434A(_at_)ct-ex01(_dot_)ciphertrust(_dot_)com>
In-Reply-To:
<DAB35AC199E7D14BAF265C1D188583687A434A(_at_)ct-ex01(_dot_)ciphertrust(_dot_)com>
Your autoresponder is fubarred.
On 10/22/2004 3:30 PM, bradon(_dot_)rogers(_at_)ciphertrust(_dot_)com sent forth
electrons to convey:
...
If you require sales assistance please contact Mark Caldwell at 678-570-1571
or mark(_at_)ciphertrust(_dot_)com(_dot_)
If you require sales engineering assistance please contact Aaron Kuehn at
678-904-9250 or akuehn(_at_)ciphertrust(_dot_)com(_dot_)
Lastly if you require technical assistance please contact CipherTrust
Support at 678-867-2999 or support(_at_)ciphertrust(_dot_)com(_dot_)
Thank you very much,
Bradon
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg