Community Discussions and Support
MAISER manipulating headers

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.  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]</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  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   Olaf</p><p> </p>

Hallo Mercuries,

have some mailinglists on Mercury/32 and saw something astonishing I never saw in any mail from any mailserver (even not from Mercury/NLM):

Original mailheaders (from CC):

...
Received: from [xxx.xxx.xxx.xxx] (xxx.xxx.xxx.xxx) by domain.de (Mercury/32 v4.73) with ESMTP
       ID MG004F08 (Using SSL/TLS, 3DES, CBC mode, keysize 192 bits) ; 24 Nov 2011 14:09:21 +0100

From: initial.lastname@domain.de>
To: Test-List@domain.de
Date: Thu, 24 Nov 2011 14:09:21 +0100
CC: givenname.lastname@domain.de
X-mailer: Pegasus Mail for Windows (4.61, DE v4.61 R1)
...

 Mailheaders of mail  to listmember:

...
Received: from spooler by domain.de (Mercury/32 v4.73); 24 Nov 2011 14:09:36 +0100
From: initial.lastname@domain.de>
To: "Test-Liste WISO" <TEST-Liste@wiso.tu-dortmund.de>
Date: Thu, 24 Nov 2011 14:09:21 +0100
Errors-to: <Owner-Test-Liste@domain.de>
Reply-to: TEST-List@domain.de
Sender: Maiser@domain.de
Received: from [xxx.xxx.xxx.xxx] (xxx.xxx.xxx.xxx) by domain.de (Mercury/32 v4.73) with ESMTP
      ID MG004F08 (Using SSL/TLS, 3DES, CBC mode, keysize 192 bits) ; 24 Nov 2011 14:09:21 +0100
Comments: Originally To: Test-List@domain.de
Comments: Originally CC: givenname.lastname@wiso.tu-dortmund.de
X-mailer: Pegasus Mail for Windows (4.61, DE v4.61 R1) (via Mercury/32 v4.73)
Message-ID: <96404062.3022.1322144147@wiso.tu-dortmund.de>
...
 You see what astonishs me? Where's my mistake? What option should I choose to end that manipulation?

Or are these bugs?
  • My mailreader is Pegasus and X-Mailer exists ... Mercury is no mailreader (at that moment only for testpurposes and may be in future if there is a webmailer) and if X-Mailer exists, it should not be manipulated. If there is no X-Mailer, Mercury creates it and puts in himself. X-Mailer as I understand that talks about the mailreader of the one in FROM. This information is importand for error- or bug-handling!
  • If MAISER gets a mail for a list, the listadress in TO must be correct. Don't touch the TO-field ... there may be other receipients in and as one of the listmembers I want to see that!.
  • Don't touch CC or BCC ... for the same reason! Delete comment ... most mailreaders don't show them on default or only in headerview.
  • All manipulated lines (excep receiverd, return-path) should be below first "received", where they normally reside. I don't want miss that line(s) somewhere in nowhere when searching for an error.

Any suggestion?

    Olaf

&lt;p&gt;Hallo Mercuries,&lt;/p&gt;&lt;p&gt;have some mailinglists on Mercury/32 and saw something astonishing I never saw in any mail from any mailserver (even not from Mercury/NLM):&lt;/p&gt;&lt;p&gt;Original mailheaders (from CC):&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;... Received: from [xxx.xxx.xxx.xxx] (xxx.xxx.xxx.xxx) by domain.de (Mercury/32 v4.73) with ESMTP &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ID MG004F08 (Using SSL/TLS, 3DES, CBC mode, keysize 192 bits) ; 24 Nov 2011 14:09:21 +0100 From: initial.lastname@domain.de&amp;gt; To: Test-List@domain.de Date: Thu, 24 Nov 2011 14:09:21 +0100 CC: givenname.lastname@domain.de X-mailer: Pegasus Mail for Windows (4.61, DE v4.61 R1) ... &lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;&amp;nbsp;Mailheaders of mail&amp;nbsp; to listmember:&lt;/p&gt;&lt;blockquote&gt;... Received: from spooler by domain.de (Mercury/32 v4.73); 24 Nov 2011 14:09:36 +0100 From: initial.lastname@domain.de&amp;gt; To: &quot;Test-Liste WISO&quot; &amp;lt;TEST-Liste@wiso.tu-dortmund.de&amp;gt; Date: Thu, 24 Nov 2011 14:09:21 +0100 Errors-to: &amp;lt;Owner-Test-Liste@domain.de&amp;gt; Reply-to: TEST-List@domain.de Sender: Maiser@domain.de Received: from [xxx.xxx.xxx.xxx] (xxx.xxx.xxx.xxx) by domain.de (Mercury/32 v4.73) with ESMTP &amp;nbsp; &amp;nbsp; &amp;nbsp; ID MG004F08 (Using SSL/TLS, 3DES, CBC mode, keysize 192 bits) ; 24 Nov 2011 14:09:21 +0100 Comments: Originally To: Test-List@domain.de Comments: Originally CC: givenname.lastname@wiso.tu-dortmund.de X-mailer: Pegasus Mail for Windows (4.61, DE v4.61 R1) (via Mercury/32 v4.73) Message-ID: &amp;lt;96404062.3022.1322144147@wiso.tu-dortmund.de&amp;gt; ...&lt;/blockquote&gt;&amp;nbsp;You see what astonishs me? Where&#039;s my mistake? What option should I choose to end that manipulation? Or are these bugs? &lt;ul&gt;&lt;li&gt;My mailreader is Pegasus and X-Mailer exists ... Mercury is no mailreader (at that moment only for testpurposes and may be in future if there is a webmailer) and if X-Mailer exists, it should not be manipulated. If there is no X-Mailer, Mercury creates it and puts in himself. X-Mailer as I understand that talks about the mailreader of the one in FROM. This information is importand for error- or bug-handling! &lt;/li&gt;&lt;li&gt;If MAISER gets a mail for a list, the listadress in TO must be correct. Don&#039;t touch the TO-field ... there may be other receipients in and as one of the listmembers I want to see that!.&lt;/li&gt;&lt;li&gt;Don&#039;t touch CC or BCC ... for the same reason! Delete comment ... most mailreaders don&#039;t show them on default or only in headerview. &lt;/li&gt;&lt;li&gt;All manipulated lines (excep receiverd, return-path) should be below first &quot;received&quot;, where they normally reside. I don&#039;t want miss that line(s) somewhere in nowhere when searching for an error.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Any suggestion?&lt;/p&gt;&lt;p&gt;&amp;nbsp; &amp;nbsp; Olaf &lt;/p&gt;

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.

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. 

 FORWARD can contain the following lines.

Forward-To: <address>
Deliver-Also: <Y> or <N>

The <address> is a single address to which the message should be forwarded.  While each Forward-To: line can only contain a single address, a user's FORWARD file can contain multiple Forward-To: lines, which will result in the message being forwarded separately to the address specified in each line.

You must turn on this capability in Configuration | Mercury core | Advanced "Allow file-based forwarding specification using FORWARD files".

&lt;p&gt;Mercury maiser creates a new message, it does not just bounce a message.&amp;nbsp; It removes all addresses in the message body to ensure that the list mail only goes to the list members.&amp;nbsp; The To: field is being corrected to the actual setting of the list.&amp;nbsp; These addresses are made comments in the the message.&amp;nbsp; This is all by design. &lt;/p&gt;&lt;p&gt;If you really need to maintain the addresses in the original body of the message&amp;nbsp; then use a real Mercury account and a FORWARD file in that account to bounce the mail.&amp;nbsp; &lt;/p&gt;&lt;p&gt;&amp;nbsp;FORWARD can contain the following lines. Forward-To: &amp;lt;address&amp;gt; Deliver-Also: &amp;lt;Y&amp;gt; or &amp;lt;N&amp;gt; The &amp;lt;address&amp;gt; is a single address to which the message should be forwarded.&amp;nbsp; While each Forward-To: line can only contain a single address, a user&#039;s FORWARD file can contain multiple Forward-To: lines, which will result in the message being forwarded separately to the address specified in each line. You must turn on this capability in Configuration | Mercury core | Advanced &quot;Allow file-based forwarding specification using FORWARD files&quot;. &lt;/p&gt;
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft