Date: Tue, 15 Feb 2005 07:06:23 -0500 From: "Matt Emmerton" <matt@gsicomp.on.ca> To: "Ted Mittelstaedt" <tedm@toybox.placo.com>, "Adi Pircalabu" <apircalabu@bitdefender.com>, <freebsd-questions@freebsd.org> Subject: Re: mx2.freebsd.org in SORBS, AGAIN! Message-ID: <009001c51356$c5bbc6a0$1200a8c0@gsicomp.on.ca> References: <LOBBIFDAGNMAMLGJJCKNKEGNFAAA.tedm@toybox.placo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > On Sat, 12 Feb 2005 03:18:17 -0800 > > "Ted Mittelstaedt" <tedm@toybox.placo.com> wrote: > > > > > A spammer is forging several of SORBS spamtrap e-mail > > > addresses on their outgoing spams. The spams hit freebsd.org > > > which of course is bouncing them back to the sender, which > > > is in this case is the spamtrap e-mail addresses. This > > > triggers the SORBS autolisting. > > > > Well, in this case, how about avoiding bounces completely? Better yet, why doesn't SORBS clean up it's act and only accept bounces for messages that were sent by their systems? Some kind of simple token in the test messages (much like how mailing list software uses unique IDs) would avoid these kinds of fake-bounces-causing-blacklisting errors. -- Matt Emmerton
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?009001c51356$c5bbc6a0$1200a8c0>