9 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Bounce email in .mail...
FromSent OnAttachments
Christian LerrahnJun 13, 2005 7:48 am 
Sam VarshavchikJun 13, 2005 8:13 am 
Casey Allen ShobeJun 16, 2005 3:39 pm 
Sam VarshavchikJun 16, 2005 4:23 pm 
moussJun 16, 2005 4:50 pm 
Casey Allen ShobeJun 17, 2005 1:14 am 
Jure KorenJun 17, 2005 1:28 am 
Tony EarnshawJun 17, 2005 2:41 am 
Sam VarshavchikJun 17, 2005 6:56 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Bounce email in .mailfilterActions...
From:Casey Allen Shobe (lis@seattleserver.com)
Date:Jun 16, 2005 3:39:00 pm
List:net.sourceforge.lists.courier-maildrop

On Monday 13 June 2005 15:11, Sam Varshavchik wrote:

2) You should avoid bouncing mail after it's already accepted by your mail server. What you're doing might've been tolerable years ago, but on today's Internet, where an estimated 75% of all E-mail is spam with forged return addresses, sending backscatter bounces to forged return addresses -- especially in situations where they are easily preventable -- is considered abusive.

I'm sorry, but what??? Bounce messages are a normal and reasonable part of the E-mail infrastructure, and are *not* considered abusive. We see lots of mail coming in to local accounts that don't exist, and then the server automatically sends out bounce messages. These bounces all typically bounce themselves, and eventually disappear out of the queue. What would you propose instead?

I certainly expect to receive a message if I accidentally typo an E-mail address, otherwise I'll have no idea the recipient did not receive the message.

Cheers,

-- Casey Allen Shobe | http://casey.shobe.info csh@seattleserver.com | cell 425-443-4653 AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523 SeattleServer.com, Inc. | http://www.seattleserver.com