17 messages in net.sourceforge.lists.courier-users[courier-users] Checking for single q...
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:[courier-users] Checking for single quotes (was removing them)Actions...
From:Robert Pfister (x1pf@adelphia.net)
Date:Oct 26, 2004 9:33:40 pm
List:net.sourceforge.lists.courier-users

Julian writes:

If your users complain about your mailserver not working well with Microsoft products, and if that is because Microsoft products are incompliant to established internet standards, tell your users about it and suggest not using Microsoft

products.

We've all got to play the cards we are dealt. Since we are unlikely to reach consensus on this, lets move on.

I think adding such checks and issuing a syntax error in the <xyz@domain'>

case would be the way to go. >But maybe there's a good reason why Courier doesn't do that?

This would solve my problem nicely. It would add a bit more time and CPU cycles to the connection overhead. This would be plausibly offset by the CPU cycles of sending a reject later on.

I could potentially collaborate on some code changes {sounds of Sam shrieking}.

I haven't seen any cases where courier rejects an address in this fashion, to figure out where to shoe-horn the code in. Any ideas?