On Tue, Mar 30, 2010 at 12:52:28PM -0400, Jon Giles wrote:
> So I set this up in the main.cf file.
>
> relay_domains = maildomain1 maildomain2 maildomain3
> relayhost = to the DNS name of the email archiving service
> fallback_relay = to the second DNS name of the email archiving service
DO NOT use fallback_relay here. Rather use internal DNS MX records, to
specify a single relayhost domain name with multiple underlying hosts.
> In a transport file:
>
> maildomain1 :[mailboxserverIP]
> maildomain2 :[mailboxserverIP]
> maildomain3 :[mailboxserverIP]
> Etc.
>
> Everything works fine, except when we have a problem with the mailbox server.
> When the mailbox server can not accept email for any reason we get mail
> loops on incoming mail.
>
DO NOT use fallback_relay, and the problem will go away.
If you simply cannot configure DNS, use a separate relay_transport,
with "-o smtp_fallback_relay=..." in master.cf for the dedicated
transport.
--
Viktor.
P.S. Morgan Stanley is looking for a New York City based, Senior Unix
system/email administrator to architect and sustain our perimeter email
environment. If you are interested, please drop me a note.
