Date: Wed, 21 Apr 2010 00:19:59 -0700 From: perryh@pluto.rain.com To: m.seaman@infracaninophile.co.uk Cc: freebsd-questions@freebsd.org Subject: Re: [SPURIOUS] Delivery Status Notification(Failure) (fwd) Message-ID: <4bcea71f.2GWYHPZ3ZYYB6t8t%perryh@pluto.rain.com> In-Reply-To: <4BCD5F2B.4050705@infracaninophile.co.uk> References: <20100420154455.G14495@sola.nimnet.asn.au> <4bcd52f8.05g7tnWntHqFWB7u%perryh@pluto.rain.com> <4BCD5F2B.4050705@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Seaman <m.seaman@infracaninophile.co.uk> wrote: > One bounce is bad enough if it goes back to the whole list > -- but that could be excused as a momentary aberration. > Any more than that is grounds for reporting the message to > postmaster@freebsd.org and having the sender blacklisted: > anyone that configures a mail server to send error notifications > to an entire mailing list needs a) to spend some quality time > studying the SMTP RFCs and b) to step away from the keyboard > /now/ as they are clearly not competent to run a mail server > on the Internet. I've seen no indications of the bounces going to the list, only to the sender (i.e. I posted 4 messages to freebsd-questions@ and got back 4 bounces; I didn't get bounces that seemed related to anyone else's posts). However, it does look as if someone needs to teach that mailserver about the Errors-To: header. > Thoroughly recommend using relaydb(1) to teach your mail system > where you've received spam from in the past and make sure it > doesn't happen again ... I let my uucp(!) upstream's Red Condor spam filter deal with that sort of problem :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4bcea71f.2GWYHPZ3ZYYB6t8t%perryh>