-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tim Legant wrote:
>>
>> I fixed this by changing one line at tmda-rfilter.
>> I changed following line in Function release_pending:
>> recipient = msg.get('x-tmda-recipient')
>> to
>> recipient = msg.get('delivered-to')
>>
>> This way, the released message is not delivered to the original
>> envelope receiver (*which in fact, might be several mailboxes, if
>> local aliases are used!*) but only to my own local mailbox. Are
>> there any risks?
>
> Probably not if your change is local and only affects you. We
> wouldn't change this for the official version of TMDA since, if you
> have an address configured as an alias for several mailboxes,
> presumably each of those mailboxes should receive a copy. As you've
> noted, re-injecting the message to the X-TMDA-Recipient will cause
> that to happen, whereas re-injecting it to Delivered-To will not.
>
> Given your particular situation and your knowledge of your MTA's
> configuration, it seems a safe change to make.
Hmm.. The problem is that the *official* version re-injects the
message to the X-TMDA-Recipient, which might case duplicate versions
to other local recipients.
btw.. I had to make a similar change to file 'Pending.py'.
- --
Send replies to:
[EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/t/ZJuA3ghgc3fUsRAlt6AKC1VH3GmqApMkiI7yYlrV5wmj5n4wCfSE+l
NSgqG73n3dk5aqfxbJq7vcU=
=Ovt6
-----END PGP SIGNATURE-----
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers
