On Thu, May 30, 2002 at 03:32:55PM +0200, Tony L. Svanstrom wrote: | | I stopped /dev/null:ing e-mails a day or so ago, just to check if there are | any false hits there (partly due to spam passing SA and going to my inbox). | | Today when I sent a question regarding the number of hits a certain e-mail got | by the CVS-version things started going wrong... Someone had an autoreply- | system set up, and since this list wasn't whitelisted a message was sent to my | e-mailaddress, which of course meant that the keywords in it triggered my auto- | reply... and when I wrote a message to their autowhitelist-system I didn't do | anything about the keywords, so then I got another autoreply which in turn | triggered an autoreply from me...
The solution is to not use broken autoresponders.
AUTO-RESPONDERS MUST NOT SEND MESSAGES TO ANY ADDRESS OTHER THAN THE
ENVELOPE SENDER. THEY ALSO MUST NOT REPLY TO "DSN" MESSAGES (sender
is '<>').
If you pick addresses by any other means to autorespond to, then
you're just asking for trouble. In addition, you SHOULD add some
X-Loop header to your automessage for detecting, and breaking, loops
like that.
The problem is not in SA but in your setup.
-D
--
A Microsoft Certified System Engineer is to information technology as a
McDonalds Certified Food Specialist is to the culinary arts.
Michael Bacarella commenting on the limited value of certification.
GnuPG key : http://dman.ddts.net/~dman/public_key.gpg
msg05652/pgp00000.pgp
Description: PGP signature
