[143107] in North American Network Operators' Group
Re: [BULK] Re: SORBS contact
daemon@ATHENA.MIT.EDU (William Herrin)
Fri Jul 29 09:50:28 2011
In-Reply-To: <12207.1311921969@turing-police.cc.vt.edu>
From: William Herrin <bill@herrin.us>
Date: Fri, 29 Jul 2011 09:48:44 -0400
To: Valdis.Kletnieks@vt.edu
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Fri, Jul 29, 2011 at 2:46 AM, <Valdis.Kletnieks@vt.edu> wrote:
> And you might want to fix it, since your users will never get a bounce no=
tice
> from any RFC-compliant mailer - even if they *wanted* to know that their =
mail
> wasn't delivered. =A0<> is the RFC-standard way to denote "this mail is a=
bounce
> report or other programmatically generated mail, and if it bounces itself=
, do *not*
> generate another bounce, as that may start a bounce loop".
Correction: It's a standard way to denote that "this mail is a bounce
report." Any other sort of programmatically generated email is
supposed to use an email address capable of receiving a reply so that
the sender becomes aware that it failed to be delivered. One defense
against so-called blowback spam is to refuse bounce reports which do
not, somewhere within the message, contain an email address that the
bounce recipient recently sent to.
Regards,
Bill Herrin
--=20
William D. Herrin ................ herrin@dirtside.com=A0 bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
