Hi. Am Mittwoch, 10. Oktober 2007 schrieb Gordan Bobic: > I've been using courier for a while now and I'm generally quite happy with > it. I quite like being able to use just one package, rather than mixing > and matching one SMTP daemon with another IMAP daemon with another POP3 > daemon, etc. But one thing really annoys me. It always seems to accept > email, provided it accepts email for that domain - even if the user > doesn't exist, and the email is thus undeliverable. This means my outgoing > spool fills up with spam bounces. > > 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?
Make sure the "mail" useraccount (or whoever the ESMTP-daemon runs as) is able to see your .courier-files. Courier checks during the SMTP dialog if your address exists. But if it can't read your directory, it will accept everything for that domain. cu, Bernd -- Und ihr wundert wuch, dass es euch schlecht geht? - Dirk Bach bei der Echo-Verleihung 2004 zur Musikindustrie
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- 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
