27 messages in net.sourceforge.lists.courier-users[courier-users] generating bounce for...
FromSent OnAttachments
Vlad MarchenkoSep 10, 2001 10:04 am 
Sam VarshavchikSep 10, 2001 3:20 pm 
Tim HunterSep 10, 2001 3:49 pm 
Vlad MarchenkoSep 10, 2001 10:53 pm 
James KnightSep 11, 2001 12:34 am 
Alexei Batyr'Sep 11, 2001 2:20 am.patch
Oliver BlasnikSep 11, 2001 4:05 am 
Vlad MarchenkoSep 11, 2001 4:11 am 
Mogens ValentinSep 11, 2001 4:46 am 
Sam VarshavchikSep 11, 2001 5:05 am 
Sam VarshavchikSep 11, 2001 5:08 am 
Tracy SnellSep 11, 2001 5:40 am 
Oliver BlasnikSep 11, 2001 5:51 am 
Oliver BlasnikSep 11, 2001 5:56 am 
Alexei Batyr'Sep 11, 2001 6:59 am 
Sam VarshavchikSep 11, 2001 10:51 am 
Sam VarshavchikSep 11, 2001 10:51 am 
David BSep 13, 2001 3:20 pm 
Alexei Batyr'Sep 14, 2001 7:34 am.Other
David BSep 20, 2001 2:14 pm 
Sam VarshavchikSep 20, 2001 2:52 pm 
David BSep 20, 2001 3:53 pm 
Sam VarshavchikSep 20, 2001 4:13 pm 
David BSep 20, 2001 4:29 pm 
Sam VarshavchikSep 20, 2001 5:17 pm 
David BSep 21, 2001 10:20 am 
Sam VarshavchikSep 21, 2001 2:31 pm 
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] generating bounce for invalid addressesActions...
From:David B (dav@oinkleburger.com)
Date:Sep 13, 2001 3:20:40 pm
List:net.sourceforge.lists.courier-users

I'm using Courier 0.35 with custom authentication. My custom authentication code is calling an Oracle procedure to validate the username/password.

When a mail client connects and sends mail to an invalid local address, the mail server gives an immediate error message saying that the address does not exist (as would be expected). I'm dealing with a mail client that does not parse that error but gives a generic error message to the user ("there was a technical problem trying to send your message"). Is it possible to configure courier to accept these mail messages, but to generate a bounced reply to the sender with the cause of the error? What would be the best way to do this?

The alternatives are to either live with the inaccurate error message or to try to get the maintainers of the mail client to release a fix.

Thanks,

David