17 messages in net.sourceforge.lists.courier-usersRe: [courier-users] RE: How to remove...
FromSent OnAttachments
Robert PfisterOct 25, 2004 6:25 pm 
Julian MehnleOct 26, 2004 4:44 am 
Robert PfisterOct 26, 2004 10:14 am 
Gordon MessmerOct 26, 2004 10:45 am 
Robert PfisterOct 26, 2004 11:40 am 
Julian MehnleOct 26, 2004 2:19 pm 
Martijn LievaartOct 26, 2004 2:34 pm 
Julian MehnleOct 26, 2004 2:52 pm 
Robert PfisterOct 26, 2004 4:41 pm 
Julian MehnleOct 26, 2004 6:26 pm 
Robert PfisterOct 26, 2004 9:33 pm 
Martijn LievaartOct 27, 2004 12:20 am 
Sam VarshavchikOct 27, 2004 4:08 am 
Martijn LievaartOct 27, 2004 4:12 am 
Robert PfisterOct 27, 2004 9:14 am 
Martijn LievaartOct 27, 2004 11:57 am 
Vincent SchonauOct 28, 2004 4:18 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: [courier-users] RE: How to remove singlequotes from incoming/outgoing mailActions...
From:Martijn Lievaart (m@rtij.nl)
Date:Oct 26, 2004 2:34:45 pm
List:net.sourceforge.lists.courier-users

I agree fully except:

Julian Mehnle wrote:

Robert Pfister [x1pf@adelphia.net] wrote:

2nd choice would be to out-right remove the address with a trailing apostrophe, as they won't be delivered anyhow.

That would be against the standards.

When the sending mail client says "RCPT TO: <'fo@bar.org'>", and Courier replies with an error message, the client could just skip this address and continue with the next "RCPT TO:" command. Of course, many clients are broken and stop the sending process at the first error message, even if the error message in question is definitely non-fatal. But why does *Courier* have to be fixed to accomodate those clients?

Think about how difficult it is to get that right. Sure, the client (MUA) could sent to the others and after the user corrected the address send it to the address that was originally faulty. It could even include the full cc list in that message. However, it has no way to get the cc list correct in the first messages sent, one address is not correct. Think about the suprise the users face when the same mail has different cc-lists when delivered to different addresses. No, not sending the message at all in the first place is correct (as in prinicple of least surprise).

I do fully agree that courier should reject the recipient outright. In fact, one client now relays through my courier so these addresses are rejected outright instead of generating a DSN somewhere later along the line (has something to do with the mailsetup from my otherwise excelent ISP). Educating the users is a pain, but as long as there are broken MUAs one always has to decide to educate or mechanically fix. This is a case where education pays in the end, as there is no end to the problems these broken MUAs create imho.

<rant> Another case of this is outlook that lets users copy email addresses with the '[]' around them. These addresses are wrong underneath -- just open the properties pane -- but are visually identical to correct addresses otherwise. Another reason why I hate outlook, one I have to deal with on a regular basis. </rant>

Cheers, M4