<blockquote><div>but the backup server handles mail for some other domains ... would that not forward ALL incoming mail to the remote server?</div><div> </div></blockquote><div>Nope, a domain mailbox is exactly that, a mailbox hold all mail for a specific domain.  You create a domain pointing to a local username (DM=username : domain.name) and all mail for that domain goes to the users new mail directory.   Now when the other Mercury/32 system using MercuryD comes in to get the mail via POP3 it only gets mail for the specified domain.</div><div> </div>

<DIV>Howdy,</DIV> <DIV> </DIV> <DIV>Need a little ASAP action, here!</DIV> <DIV> </DIV> <DIV>We have 2 servers setup with mercury for one organization's email (ie. one domain). What we want is to have redundancy built-in such that if one mail server dies, the other one can pick-up where the first one left off.</DIV> <DIV>Server 2 is currently acting as the preference=0 mail server in the dns settings and server 1 is preference=30. So what we want is to have server 1 forward any mail it receives for the entire domain to server 2. and if something happens to server 2, then we can stop that quickly and have server 1 collect mail for the domian.</DIV> <DIV> </DIV> <DIV>the only other problem is that server 1 is collecting mail for several other domains at the same time.</DIV> <DIV> </DIV> <DIV>while the dns settings are correct, and most mta's will correctly first try to send mail to server 2, it has been my experience that this does not occur all the time and that some legitimate email is attempted to be delivered to a higher preference #. this is the reasoning behind this setup.</DIV> <DIV> </DIV> <DIV>thanks in advance!</DIV> <DIV>gw</DIV>

<p>The common procedure would be to have a domain mailbox on the backup server, and use the Mercury POP3 client on the main server to collect mail from it.</p><p>/Rolf </p>

[quote user="Rolf Lindby"]<p>The common procedure would be to have a domain mailbox on the backup server, and use the Mercury POP3 client on the main server to collect mail from it.</p><p>/Rolf </p><p>[/quote]</p><p>And use the X-Envelope-To: header added by Mercury/32 core when delivering to the POP3 domain mailbox in the MercuryD setup.   In this case the original RCPT TO: address is being used for delivery. </p>

[quote user="Rolf Lindby"] <P>The common procedure would be to have a domain mailbox on the backup server, and use the Mercury POP3 client on the main server to collect mail from it.</P> <P>/Rolf </P> <DIV>[/quote]</DIV> <DIV> </DIV> <DIV>but the backup server handles mail for some other domains ... would that not forward ALL incoming mail to the remote server?</DIV> <DIV>thanks, gw</DIV>

[quote user="airyt"][quote user="Rolf Lindby"] <P>The common procedure would be to have a domain mailbox on the backup server, and use the Mercury POP3 client on the main server to collect mail from it.</P> <P>/Rolf </P> <DIV>[/quote]</DIV> <DIV> </DIV> <DIV>but the backup server handles mail for some other domains ... would that not forward ALL incoming mail to the remote server?</DIV> <DIV>thanks, gw</DIV> <DIV>[/quote]</DIV> <DIV> </DIV> <DIV>sorry, just re-reading your post. i understand it now. thanks, gw</DIV> <DIV> </DIV>