Qmail
[Top] [All Lists]

Re: Question about Qmail relating to MX retry processing

To: qmail@list.cr.yp.to
Subject: Re: Question about Qmail relating to MX retry processing
From: Charles Cazabon <qmail@discworld.dyndns.org>
Date: Fri, 24 Nov 2006 22:10:44 -0600
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-qmail@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list qmail@list.cr.yp.to
In-reply-to: <45679726.9080600@perkel.com>
Mail-followup-to: qmail@list.cr.yp.to
Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
References: <45676987.2050808@perkel.com> <456789E5.3000508@gatworks.com> <45678E43.5030508@perkel.com> <45679170.1040203@gatworks.com> <45679726.9080600@perkel.com>
User-agent: Mutt/1.5.11
Marc Perkel <marc@perkel.com> wrote:
>
> But Qmail won't send the email to the backup MX?

Not if it is able to make a tcp connection to a higher-priority/lower-distance
one.

> There's a spec - everyone else follows the spec - except qmail.

Your assertion is incorrect.  Re-read RFC 974:

  If the list of MX RRs is not empty, the mailer should try to deliver the
  message to the MXs in order (lowest preference value tried first).  The
  mailer is required to attempt delivery to the lowest valued MX.
  Implementors are encouraged to write mailers so that they try the MXs in
  order until one of the MXs accepts the message, or all the MXs have been
  tried.

Only trying the lowest-distance MX is permitted.  If you think otherwise,
you're discarding mail, and you've got no noe to blame but yourself.

If you want to make your hare-brained scheme work, don't accept the connection
in the first place, rather than accepting it and not accepting the message.

Charles
-- 
--------------------------------------------------------------------------
Charles Cazabon                               <qmail@discworld.dyndns.org>
Read http://pyropus.ca/personal/writings/12-steps-to-qmail-list-bliss.html
My services include qmail consulting.  See http://pyropus.ca/ for details.
--------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>