Hi,
The change to the 'No such user' response has what appears to be an
unintended side-effect.
I have several virtual domains that are set up to be handled by a local
user with .courier-* files; where there is no .courier*default file for
that user. That has the effect of reporting "No such user" if there is
no .courier-$localpart file for [EMAIL PROTECTED]
One such example:
@netnautics.com: netnautics
The error message for these cases looks like this example:
Oct 4 08:47:44 werkt courieresmtpd: error,relay=::ffff:89.123.135.140,
from=<[EMAIL PROTECTED]>,
to=<[EMAIL PROTECTED]>: 550 User <netnautics> unknown
(reformatted for legibility).
That is wrong in two ways: User <netnautics> does exist; and it was
'[EMAIL PROTECTED]' that didn't exist, causing the error
message to be wrong. If courier has lost the original address when it
fills in that value, I'd prefer it if no specification was given at all;
but providing the correct non-existant address would be even better.
-------------------------------------------------------------------------
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
