-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nick Smith wrote: >>>ive read through all the man pages pertaining to the subject, and >>>searched google, which pointed me back to the man pages, but my users >>>are virtual, and i dont want an entire domain going to one user, i >>>have several users defined, i want "all the rest" going to a specific >>>account. can this be done? how?
By "all the rest" do you mean that if you host "domain.com" then you want ANY address "@domain.com" to be accepted by courier and delivered somewhere? This is generally a very BAD idea as you will receive literally thousands of spam messages. If a machine is connected to the internet you should *never* accept mail for any user. But if you have a machine that is not connected to the internet and you need to do something like this then you have several options. One is what Sam described - alias the whole domain to a single user and then use ".courier-user" files to specify where mail should be delivered. So you could still keep your "defined" users and have separate ".courier-user" files for each of them which would tell courier to store mail in their existing INBOX. But then you also have a ".courier-default" file which tell courier what to do with "all the rest" (i.e. any addresses at the domain which are not defined by a ".courier-user" file.) If your domain, "domain.com", is a hosted domain then you can create a catch-all account - "[EMAIL PROTECTED]". Now all mail to undefined users "@domain.com" will be delivered to "[EMAIL PROTECTED]". Of course then you probably have to use a ".courier" file or some such to tell courier what to do with all that mail assuming don't just want it all to pile in the "alias" account. You can also use a general ".courier-default" file. When courier is trying to deliver a message the last place it looks for instructions is in courier's "aliasdir" directory. And the last file it reads in there is the ".courier-default" file. So you could put instructions in that file telling courier what to do with users in your domain who are not defined. See the 'makealiases' man page for instructions on aliasing a domain to a single user and then using ".courier-user" and ".courier-default" files. See the 'makehosteddomain' man page for instructions on the "[EMAIL PROTECTED]" catch-all account. And see the 'dot-courier' man page for instructions on the ".courier-default" file in the "aliasdir" directory. But again, do NOT do this on server that receives mail from the internet. You really do not wanted to accept mail for any user at your domain if you are connected to the internet. You will only drown in spam and other problems. HTH Jeff Jansen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDtbFiZxtYeNk78A8RAgFcAJ9LM715VuiaEwQLawitCWpHP3lJ6QCgmgjk Ae/gr5kAqO+bKMXS43ZAuYo= =eLeI -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
