|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: 2.3.x dsn support and delay_warning_time
From: Wietse Venema (wietse
porcupine.org)
Date: Tue Oct 17 2006 - 05:41:02 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rene van Hoek:
> Wietse Venema wrote:
> > Rene van Hoek:
> >> Hello,
> >>
> >> Postfix 2.3.x support fully dsn. With dsn, an remote mua or mta can
> >> specify of which events to get informed (delayed, failed, success). See:
> >> http://www.postfix.org/DSN_README.html
> >>
> >> My question is, how does this relate too the delay_warning_time setting?
> >
> > That is not specified in the RFC documents.
> >
> > Wietse
> >
> Hello,
>
> Let me clarify.
>
> As described in http://www.postfix.org/DSN_README.html:
>
[deleted]
>
> So I am wondering how the above relates too the 'delay_warning_time' setting.
Citing RFC 3461
+ A NOTIFY parameter value containing the keyword "DELAY" indicates
the sender's willingness to receive "delayed" DSNs. Delayed DSNs
may be issued if delivery of a message has been delayed for an
unusual amount of time (as determined by the MTA at which the
message is delayed), but the final delivery status (whether
successful or failure) cannot be determined. The absence of the
DELAY keyword in a NOTIFY parameter requests that a "delayed" DSN
NOT be issued under any conditions.
All possible delay_warning_time settings are compliant with RFC
3461, including the setting where the MTA never sends DELAY
notifications.
In other words, RFC 3461 is totally unrelated to delay_warning_time settings.
Wietse
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]