This is a discussion on Re: DSN (2) within the mailing.postfix.users forums, part of the Mail Servers and Related category; -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wietse Venema wrote: > Victor Duchovni: > >>On Tue, May 24, 2005 ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 Wietse Venema wrote: > Victor Duchovni: > >>On Tue, May 24, 2005 at 04:04:58PM -0400, David Cary Hart wrote: >> >> >>>In my quest for MTA erudition, I have gone through the referenced RFCs >>>and I concede that I still don't know what I don't know. Hopefully, >>>someone will eventually create a comprehensible document or "howto." >> >>What problem are you trying to solve? Why does DSN need a howto? It will >>just work(TM). The configuration parameters will have sensible defaults >>that most sites won't need to change and will be documented. > > > DSN support does not fundamentally change the information in Postfix > bounce messages, because Postfix already implemented the easy 90 > percent of the DSN protocols. > > DSN support adds one option to the Postfix sendmail command: > > -N dsn (default: 'delay, failure') > Delivery status notification control. Specify either a comma- > separated list with one or more of failure (send notification > when delivery fails), delay (send notification when delivery is > delayed), or success (send notification when the message is > delivered); or specify never (don't send any notifications at > all). > > This feature is available in Postfix 2.3 and later. > > These options are propagated via SMTP to servers that understand > DSN. You can disable DSN with smtpd_discard_ehlo_keywords=dsn, or > with smtpd_discard_ehlo_keyword_address_maps if the feature needs > to be selective. > > So notify=success is new, as is notify=never. However, notify=never > works only if the receiving server understands DSN too. Can someone give me the proper syntax to test this? (I am running the latest snapshot) as it doesn't appear to work for me. Or am I reading the changes wrong and it's not yet fully implemented? Thanks, Chris - -- Chris Horry KG4TSM "You're original, with your own path zerbey@wibble.co.uk You're original, got your own way" PGP: DSA/2B4C654E -- Leftfield -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCk5pEnAAeGCtMZU4RAtUNAJ4hQecx5l2BsyyOxW0W3z rXZqF2IgCbBVeo 5EvyBoNT83JZC9sBQXOcwq8= =FA9P -----END PGP SIGNATURE----- |