Gordan Bobic wrote: > 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
Yes, that is likely. However, since you haven't told us how the domain in question is configured, we can only guess as to what's wrong. I might venture a guess that you've created a virtual domain alias (@domain: user), and that user's home directory isn't readable by the user as which courier runs. In that case, courier can't check for the dot-courier files in the user's home directory during the SMTP conversation, and it has to accept everything. You'd need to add read and execute permissions to the user's home directory to fix that problem. If that's not it, you need to tell us whether the domain is local or hosted, how the users are configured, whether or not there are any .courier-*default files in /etc/courier/aliasdir, and anything else that might be relevant to the domain's configuration. The version shouldn't matter; Courier's smtp service has never behaved the way you describe unless specifically configured to do so. ------------------------------------------------------------------------- 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
