Matt Kettler wrote:
Steve Martin wrote:
Some trojan/whetever sent an email to a nonexistent address
([EMAIL PROTECTED])
The return address was spoofed as one of my addresses ([EMAIL PROTECTED])
Their brain-dead mailer daemon then sent the failure back to me.
That's not really all that brain-dead.
Of course, they'd be smarter to check the recipient domain at delivery time,
instead of queuing then bouncing later, but VERY few mailservers check this kind
of thing.
The ones I hate are the viruses that forge addresses like
[EMAIL PROTECTED], then try to send to [EMAIL PROTECTED] We reject
incoming mail claiming to be from [EMAIL PROTECTED] and similar
addresses with a "Forgery detected!" error, since we know we'll only
ever send that mail from inside our network.
So what happens? The relay reads our error and generates a bounce,
sending it to [EMAIL PROTECTED], complete with the "Forgery detected"
error we gave them!
The worst part is, I can't convince myself that they *shouldn't*
generate the bounce. It's just really annoying!
--
Kelson Vibber
SpeedGate Communications <www.speed.net>
