Replies: 1 comment 1 reply
-
It is undesirable to change this to the (each) address of the final destination. This is because the recipient may mistakenly believe that the message in question is sent only to them, and may not realize that it has been read by the other people on the mailing list. For the same reason, rewriting The feature you desire would be useful in a one-way announcement list, but is difficult to achieve in Sympa. Some other email newsletter distribution systems may allow personalization of |
Beta Was this translation helpful? Give feedback.
-
Hi all,
i am responsible for a larger Sympa installation and it works really fine. Thanks for your excellent work!
There is just this one thing, i just seem to not unterstand.
Stituation as i understand it form a header use perspective. Involved headers:
Envelop-To: subscriber
To: list address
X-Original-To: list address
What happens: The Envelop-To is used to determine which account gets the message and then this header gets delete upon delivery (yes, the subscriber address can be found in some Received header, but that is a rather convoluted header; a least in enterprise setups, as we have installed). Thus the normal mailclient user (probably not looking into mail headers at all) can not directly see which of his aliases is subscribed in the list. When they try to unsubscribe for instance, it can fail because they do not use the correct alias for the list. As such we listserver-admin do get tickets, in which they ask for the reason why they can not unsubscribe from a specific list they are subscribed to.
So here is my question:
I would be inclined to change the To header to subscription address, as sympa generates individual mail for each subscriber. But i don't know the reasoning behind the use of the headers right now.
Best regards,
Patrick Veith
Beta Was this translation helpful? Give feedback.
All reactions