On Wed, 10 Oct 2007, Jerry Amundson wrote: > On 10/10/07, Gordan Bobic <[EMAIL PROTECTED]> wrote: >> On Wed, 10 Oct 2007, Lisa Muir wrote: >> >>>> I'm assuming this is due to my having misconfigured it in some way, but >>>> I'm not sure where to look for the problem. How can I ensure that the >>>> undeliverable recipients are identified and the connection dropped as >>>> soon as the RCPT TO: command is received? >>> >>> sounds like you are using a very old version of courier. Try using an >>> up to date one. >> >> Interesting - any info on when this behaviour was changed? I just tested >> it on a box running 0.56, and yes, it rejects right after RCPT TO:. > > I don't recall any version which accepted [EMAIL PROTECTED] by default. > Sounds like you may have a catch-all somewhere. Check .courier files, > etc/courier/alias*, and so on.
There were aliases, but definitely no catchalls. Otherwise the message would be deliverable, rather than bounce back. It was version 0.4x that I was running, but I'm not sure which one exactly. The mail server in question expired recently, hence why I'm looking into my upgrade options. But if this is now working I think I'll stick with Courier. :-) Gordan ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
