Qmail
[Top] [All Lists]

Re: Qmail is clearly out of compliance with RFC282.

To: qmail@list.cr.yp.to
Subject: Re: Qmail is clearly out of compliance with RFC282.
From: Markus Stumpf <maex-lists-qmail@leo.org>
Date: Tue, 28 Nov 2006 00:22:53 +0100
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: <456B69D4.3080005@perkel.com>
Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
Organization: LEO - Link Everything Online, Munich, Germany
References: <45676987.2050808@perkel.com> <456789E5.3000508@gatworks.com> <20061125.101809.193764004.hanche@math.ntnu.no> <45686D69.5040003@perkel.com> <20061127143127.GA29898@discworld.dyndns.org> <456B03BA.1060303@perkel.com> <456B5418.10708@blackpacket.net> <456B69D4.3080005@perkel.com>
User-agent: Mutt/1.5.12-2006-07-14
On Mon, Nov 27, 2006 at 02:42:28PM -0800, Marc Perkel wrote:
> What this says is that if you decide to have some limits that the limits 
> should be set at 2 or more. Since Qmail doesn't have a configurable 
> limit then the MUST part applies.

Read on in the same section:

   Although the capability to try multiple alternative addresses is
   required, specific installations may want to limit or disable the use
   of alternative addresses.  The question of whether a sender should
   attempt retries using the different addresses of a multihomed host
   has been controversial.  The main argument for using the multiple
   addresses is that it maximizes the probability of timely delivery,
   and indeed sometimes the probability of any delivery; the counter-
   argument is that it may result in unnecessary resource use.  Note
   that resource use is also strongly determined by the sending strategy
   discussed in section 4.5.4.1.

Now look at "4.5.4.1 Sending Strategy"

   The sender MUST delay retrying a particular destination after one
   attempt has failed.  In general, the retry interval SHOULD be at
   least 30 minutes; however, more sophisticated and variable strategies
   will be beneficial when the SMTP client can determine the reason for
   non-delivery.

All that you cite is that a sending MTA must have the capability to use
different/alternate MX hosts. It says nothing about using them, when
using them and in which interval and for what reasons.

For standards it doesn't help to grep for a keyword and cite a phrase.
For standards you have to read the whole paper and understand it.

> Qmail is out of compliance with RFC282.

Says who? You? *lol*

        \Maex



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