Hi,
I setup a Postfix based plateform whith DSN enabled to support "success" NOTIFY
as described below :
1) Mails are forwarded to Cyrus through LMTP ("delivered" action is fixed
since thread "LMTP delivery and DSN action value for "success"")
2) mailboxes on Cyrus are internal addresses, virtual alias makes mapping
between external address and internal address
3) antispam and antivirus processing is done by pipe based content filter
I have a first issue when mapping address with virtual alias, address is
notified "expanded" even if 1 to 1 mapping.
I found the following thread : " Re: DSN chain broken by virtual alias map"
>> I know the current behaviour is acceptable by rfc3461, and I know that
>> specifying multiple addresses in virtual map is possible and would call for
>> current handling. Still, it would be nice to pass NOTIFY=SUCCESS to
>> the next MTA if virtual alias maps is used purely for 1-to-1 recipient
>> address transformations.
> You will find the same behavior with local(8) aliasing, and
> dot-forward files, again in conformance with the RFC it will
> propagate all DSN options except for the NOTIFY SUCCESS option.
> If someone wants one-to-one expansions to be treated special then
> they will have to write code for virtual alias, local alias, and
> dot-forward files. It is either all three or nothing. I will not
> accept inconsistenct behavior.
I am voluntary to write such code for local alias and dot-forward files too if
always OK
I have a second issue with pipe process that don't manage DSN options. I
started a patch to manage such options.
I propose to open 2 threads in postfix-devel mailing list for these two patches
if everybody is OK
Thanks,
Sébastien
Ce message et les pièces jointes sont confidentiels et réservés à l'usage
exclusif de ses destinataires. Il peut également être protégé par le secret
professionnel. Si vous recevez ce message par erreur, merci d'en avertir
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant
être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra
être recherchée quant au contenu de ce message. Bien que les meilleurs efforts
soient faits pour maintenir cette transmission exempte de tout virus,
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne
saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for
the addressee; it may also be privileged. If you receive this e-mail in error,
please notify the sender immediately and destroy it. As its integrity cannot be
secured on the Internet, the Atos Origin group liability cannot be triggered
for the message content. Although the sender endeavours to maintain a computer
virus-free network, the sender does not warrant that this transmission is
virus-free and will not be liable for any damages resulting from any virus
transmitted.
