2011/1/25 Eric Charles <[email protected]>:
> Hi,
>
> Trying to learn more, I read http://www.ietf.org/rfc/rfc1892.txt and have a
> few questions:
>
> - Could you sketch a simple use case of ESMTP-DSN (sorry to ask, I don't
> know anything about it).

It usually enable better bounces and better message tracking.

For example my company wrote an email marketing service. This service
works with any SMTP server correclty supporting the DSN extension.
This requirement is that our web application wants to receive not only
failures notifications but also success notifications. ESMTP-DSN allow
this kind of result. Otherwise by default you only receive a bounce
when there is a delivery issue and not when delivery succeded. Also
the "notification" you get contains informations you requested
(original headers/message, the ENVID you used to send the message).

DSN extension also allow for better tracking of aliasing: if every MTA
in the chain supports DSN then in your bounce you will see the
original recipient you used. This is a very good stuff when some
aliasing happened in the middle and let you find the original
recipient even without using VERP or similar techiques based on
rewriting the return path.

> - Is DSN for MTA-to-MTA only or also for Client-to-MTA ?

Could even be used by Clients but I'm not aware of clients using it.
This would let users ask for success delivery notification reports.

> - Do you know if thunderbird 3 support DSN?
> (http://forums.mozillazine.org/viewtopic.php?f=29&t=780365 I may ask th ml,
> but maybe you've got experience with it)

I don't think it supports DSN, but I never investigated.

So, for the final user this is not anything "major", but I think that
the most difficult task to correctly implement DSN is to allow the
container to better track each mail and I better tracking would help
administratorts to find what happened to a message.

Stefano

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to