The problem was never mail directed to the domain that it was a backup MX for. The problem is mail directed at the mail server itself.
So in a more condensed form:
* Does it check in 'me' when comparing MX records if 'locals' doesn't exist?
* How can I block/redirect mail addressed to the mail server (_not_ the domain it's handling) without having to put up an alias for every user on the machine?
Regards Pierre
Patrick O'Reilly wrote:
Pierre,
all you need for the secondary MX server is the hostname entry in 'locals' (which must match the hostname listed in the MX record exactly, of course).
When courier accepts the email and then recognises that this email address is not held locally it will consult the dns itself, see that there is another preferred MX record, and try to relay the email to that hostname. Presumably that host is temporarily unavailable, so the email will just sit in the mailq as usual until the primary MX is available again.
Regards, Patrick.
----- Original Message ----- From: "Pierre Ossman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 09, 2004 9:47 PM Subject: [courier-users] Backup MX configuration
Hi!exist?
I've been using courier for awhile now and I think it's a great piece of software. I am, however, not quite clear about how to configure it as a backup MX server. From the FAQ I can read that:
"Furthermore, the hostname in the MX record must be one of the hostnames in the |locals| configuration file."
Is it absolutely crucial that this hostname exists in 'locals' or does
it follow normal semantics and defaults to 'me' when 'locals' doesn't
Also, I'd prefer to not have any mail delivered to the machine acting ascatch-all.
a backup MX. But the constraint above makes it consider any mail to
<[EMAIL PROTECTED]> to be a local mailbox. If it is possible
I'd like it to forward this mail to <[EMAIL PROTECTED]> instead. Setting
up an alias for every user is not an option. I need some kind of
If this is not possible, then can I configure it to bounce all mail heading for <[EMAIL PROTECTED]>? There are user accounts on the machine but I don't want them to receive mail.
I don't know if you're supposed to retain some accounts going to specific mail servers (<[EMAIL PROTECTED]> comes to mind). If so, I'd appreciate any pointers on what's customary to have set up. Maintaining aliases for some system critical stuff is acceptable, having to put up a new reject rule for each new user on the machine is not.
Regards Pierre Ossman
PS. Could you cc any replies to this address since I'm not subscribed to courier-users, thanks.
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
