I've not seen the difference in the result of greylisting and requiring rDNS records except that with rDNS someone has to be accountable for their mail server and greylisting doesn't require this. Reverse DNS checking at the smpt level would be more effective at bandwidth reduction now and later I would think. There are negative opinions about rDNS though also.

Basically though rDNS and SPF really require larger scale implementation to be effective while greylisting would not.

On Mar 6, 2004, at 9:26 PM, LuKreme wrote:

On 05 Mar 2004, at 03:23, Andy Blanchard wrote:
While the technique described in this article is intended for
implementation at the MTA level,

My prediction is that this is going to be bad.

During the initial testing of Greylisting in mid-2003, it was observed that the vast majority of spam appears to be sent from applications designed specifically for spamming. These applications appear to adopt the "fire-and-forget" methodology. That is, they attempt to send the spam to one or several MX hosts for a domain, but then never attempt a true retry as a real MTA would.

Great, so the next wave of spammers will be firing off multiples of every single spam, probably by processing their list twice (to give some time between the two attempts).


Just what we need, a doubling of traffic.

As a temporary stop-gap I'm sure it will be astonishingly effective. long-term it's really gonna suck.

--
Because you can't cotton to evil. No Sir. You have to smack evil on the nose with the rolled-up newspaper of justice and say,'Bad evil. bad BAD evil'"




Kindest regards,

Ron

"What shall we do? What shall we do?" he cried, "Escaping goblins to be caught by wolves!" - Bilbo Baggins

The Hobbit by J. R. R. Tolkein
http://www.apple.com/trailers/newline/returnoftheking/trailer_large.html



Reply via email to