> On Monday 12 January 2004 05:30, Patrick O'Reilly wrote: > > 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. > > OK, I'm showing my ignorance here. I don't follow this. I thought in order > to be a backup MX you needed an entry in "acceptmailfor" and specifically NOT > in locals or hosteddomains. If I am "example.com" and I want to function as > a backup server for "domain.com", then I put "domain.com" into > /etc/courier/acceptmailfor. Then my machine accepts mail for all addresses > at "domain.com" and tries to ship it back out since this domain is not > actually hosted on my machine. > > If I put "domain.com" into locals then when any mail arrives for this domain > won't it be rejected by courier with "550 - user unknown" since this account > does not exist on my machine? > > What have I missed here? >
Oops - I omitted mentioning 'esmtpacceptmailfor'. Here's a quaestion posted on this list some time ago, and the answer which was from Sam: > I have a machine which is the secondary mail server for "domain1.com" > and "domain2.com". The machine is known as "mail2.domain1.com" and > "mail2.domain2.com" in the MX records. What is the proper way to > configure Courier so that it will spool the mail and then deliver it to > the primary mail servers when they are available? domain1.com and domain2.com in esmtpacceptmailfor mail2.domain1.com and mail2.domain2.com in locals MX records for mail2.domain1.com and mail2.domain2.com indicating a higher priority than the MX records for the primary MX. The process is very simple. When sending mail via ESMTP, MX records are read and sorted. Each record is checked against the local domain list. If a record is found that's naming the local machine, all MX records with the same, or higher, priority are removed. HTH - Patrick. ------------------------------------------------------- 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
