[70523] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Barracuda Networks Spam Firewall

daemon@ATHENA.MIT.EDU (Majdi S. Abbas)
Tue May 18 13:11:56 2004

Date: Tue, 18 May 2004 10:11:20 -0700
From: "Majdi S. Abbas" <msa@samurai.sfo.dead-dog.com>
To: "Jared B. Reimer" <jared@theriver.com>
Cc: nanog@merit.edu
In-Reply-To: <6.0.0.22.2.20040517142019.02a454f8@LOCALHOST>
Errors-To: owner-nanog-outgoing@merit.edu


On Mon, May 17, 2004 at 02:26:37PM -0700, Jared B. Reimer wrote:
> This is a pretty serious flaw IMHO, if it is (in fact) true.  qmail isn't 
> the only mailer that behaves this way.  It looks like they may have tried 
> to kludge their way around this with LDAP in the case of MS Exchange, which 
> also does asynchronous bouncing of undeliverable mail IIRC.

	Quite frankly, I'm at a loss as to why anyone would wish to accept
and queue mail that they cannot deliver.  Queuing everything just allocates
disk unnecessarily and results in a lot of delayed bounce backscatter, 
almost always directed at a third party (in the common case of spoofed from: 
headers).

	Accepting everything simply because you don't wish to give away
valid addresses doesn't work; the spam bots just jabber more loudly at you.
In the past year I've had two domains joe jobbed, generating thousands of
those helpful delayed bounce messages per hour for my role accounts.

	If, after RCPT TO, you do not have a valid destination, just 
refuse it.  My role accounts thank you.

	--msa

home help back first fref pref prev next nref lref last post