Hallo Thomas
[quote user="Thomas R. Stephenson"]Mercury maiser creates a new message, it does not just bounce a message. It removes all addresses in the message body to ensure that the list mail only goes to the list members. The To: field is being corrected to the actual setting of the list. These addresses are made comments in the the message. This is all by design.[/quote]
Hmm ... reads like having a designdiscussion. I'm on many mailinglists and some of them administered by me (i.e. the german Mailinglist for Pegasus mail), most of them on majordomo and mailman ... and even had that lists on Mercury/NLM before. None of them behaves like that ... it is very (!!!) unusual.
I've built some mailutilities with perl, PHP (long before they had modules or libraries for that). I used it with Mercury/NLM simply placing ready to send mails as files in the queuedirectory. All you need to do is to add a envelope with mailadresses for sender and recepient(s). In case of maiser you may wish to add headers like sender, errors-to, reply-to, may be some list-headers, change return-path and add some received-lines. Thats all. The other headers don't need to be touched.The recepients are in envelope - nowwhere else, that's all you need to enshure only listmenbers get the mail. So - why does mercury touch and manipulate the other headers? There is no reason at all!
[quote]If you really need to maintain the addresses in the original body of the message then use a real Mercury account and a FORWARD file in that account to bounce the mail.[/quote]
For shure I'm not the only maintainer who needs this information and most times he may not have access to my Mercury/32. And I don't want to have thousands of mails forwarded to have probably that one I have to maintain. It's not my private playground at home - it's the mailserver of a faculty. I was willing to buy a big license of Mercury/32 ... but the more bugs or unusual behavior I find while testing the more I get in doubt.
Sorry, but there is a simple rule in mailhandling: never touch headers that you don't realy need to touch!
bye Olaf
<p>Hallo Thomas
</p><p>[quote user="Thomas R. Stephenson"]Mercury maiser creates a new message, it does not just bounce a message.&nbsp; It removes all addresses in the message body to ensure that the list mail only goes to the list members.&nbsp; The To: field is being corrected to the actual setting of the list.&nbsp; These addresses are made comments in the the message.&nbsp; This is all by design.[/quote]</p><p>Hmm ... reads like having a designdiscussion. I'm on many mailinglists and some of them administered by me (i.e. the german Mailinglist for Pegasus mail), most of them on majordomo and mailman ... and even had that lists on Mercury/NLM before. None of them behaves like that ... it is very (!!!) unusual.</p><p>I've built some mailutilities with perl, PHP (long before they had modules or libraries for that). I used it with Mercury/NLM simply placing ready to send mails as files in the queuedirectory. All you need to do is to add a envelope with mailadresses for sender and recepient(s). In case of maiser you may wish to add headers like sender, errors-to, reply-to, may be some list-headers, change return-path and add some received-lines. Thats all. The other headers don't need to be touched.The recepients are in envelope - nowwhere else, that's all you need to enshure only listmenbers get the mail. So - why does mercury touch and manipulate the other headers? There is no reason at all!
</p><p>[quote]If you really need to maintain the addresses in the original body of the message&nbsp; then use a real Mercury account and a FORWARD file in that account to bounce the mail.[/quote]</p><p>For shure I'm not the only maintainer who needs this information and most times he may not have access to my Mercury/32. And I don't want to have thousands of mails forwarded to have probably that one I have to maintain. It's not my private playground at home - it's the mailserver of a faculty. I was willing to buy a big license of Mercury/32 ... but the more bugs or unusual behavior I find while testing the more I get in doubt.</p><p>Sorry, but there is a simple rule in mailhandling: never touch headers that you don't realy need to touch!
bye&nbsp;&nbsp; Olaf</p><p>&nbsp;</p>