Tim Hosking writes: 

> That's odd. I have a similar set-up and it just works. I don't have to do
> anything to have the mail relayed to the primary when it comes back online.
> Assuming that the backup server has an entry for the primary's domain in
> esmtpacceptmailfor.dir/accept and that domain is not listed in locals or
> hosteddomains then the forwarding should be automatic. 
> 
> I don't pretend to know exactly how this is achieved or indeed if I am
> correct in the above statements, but it sounds to me as if you have a

This is correct.  This is achieved simply by following the instructions in 
INSTALL: 

Define local domains 

  The  configuration  file  /usr/lib/courier/etc/locals is a list of all
  the  domains  that  are  considered  local. Mail to any address in any
  local  domain  is  handled  as a local delivery. If this file does not
  exist  Courier  will use the contents of the me configuration file, or
  it will obtain its machine name from the operating system.

  This  file contains a list of domains, one per line. In most cases you
  need  to initialize this file to contain every hostname that has a DNS
  A,  or  AAAA,  record  pointing  to  any  IP  address assigned to this
  machine,  including  "localhost". 

... 

Create a list of domains to accept mail for 

  If  you  would like your server to function as a backup mail relay for
  other domains, create /usr/lib/courier/etc/esmtpacceptmailfor. This is
  a  plain  text  file, containing a list of domains, one per line. This
  file  lists all domains your server will accept mail for. NOTE: if you
  create this file, you MUST include all your local domains. Usually you
  can  simply  append  what  you have in /usr/lib/courier/etc/locals. 

If you've followed these instructions to the letter, Courier will correctly 
function as a backup MX. 

The most common cause of backup MX misconfiguration is forgetting to list 
all hostnames with one of your A/AAAA records in locals (or hosteddomains). 
If that happens, Courier may not see itself listed as an MX for a given 
domain, and treat it no differently than any other remote domain, and ending 
up looping all mail to itself, until it bounces. 

-- 
Sam 


_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to