Community Discussions and Support
Don't always want "Duplicate Message Suppressed"

My wife and I are both members in a club that sends notices via google

groups.  Therefore two identical e-mails arrive via MercuryD, one

addressed to her, one addressed to me.  One of these e-mails will be

suppressed, and it is luck-of-the-draw whether I get the remaining one

or she.  Is there any way to disable this feature?

Only through the use of a special header in the mail message that provides the original RCPT TO: address.  You cannot use the X-Envelope-To: header for this since it's written at the time the mail is being written to a CNM file by core.  If there is no special header then you may have to use a filter to forward the mail from the Google group to the other user.

Checking for special headers in messages

By default, MercuryD goes through the standard headers in incoming mail looking for local addresses: the fields it examines are: "To", "Cc", "BCC" and "Received". MercuryD also records the Message-ID of every message it processes and usually will not attempt to deliver the same message twice.

Unfortunately, not all ISPs use POP3 mailbox schemes that will work with this approach: some use a non-standard header to record the address of the person for whom the message was actually intended - for example, "X-Deliver-To" is one that is seen from time to time. If your ISP uses a non-standard header to record the delivery envelope address, you can tell MercuryD about it using the Headers control: type in the name of the header Mercury should examine for local addresses (so, from our example above, you would type in X-Deliver-To). The field is not case-sensitive (so, X-Deliver-To and X-DELIVER-TO are treated as identical) and you can add the colon separator at the end of the name or not as you wish. If your ISP uses more than one special header to identify the local addressee, you can enter multiple header names in this field, separated by semi-colon characters (";"). You must not type any spaces in this field.

If you check the control labelled Check only in these headers then MercuryD will no longer examine the standard To, Cc, Bcc and Received headers for local addresses and will not discard duplicate messages. Use this control only if you are sure that your ISP always adds the header to your mail.

Your ISP will usually be able to tell you if they use a special header to identify the envelope address in your messages.

<blockquote>My wife and I are both members in a club that sends notices via google groups.  Therefore two identical e-mails arrive via MercuryD, one addressed to her, one addressed to me.  One of these e-mails will be suppressed, and it is luck-of-the-draw whether I get the remaining one or she.  Is there any way to disable this feature? </blockquote><p>Only through the use of a special header in the mail message that provides the original RCPT TO: address.  You cannot use the X-Envelope-To: header for this since it's written at the time the mail is being written to a CNM file by core.  If there is no special header then you may have to use a filter to forward the mail from the Google group to the other user. </p><p><i><b>Checking for special headers in messages</b></i> By default, MercuryD goes through the standard headers in incoming mail looking for local addresses: the fields it examines are: "To", "Cc", "BCC" and "Received". <b><i>MercuryD also records the Message-ID of every message it processes and usually will not attempt to deliver the same message twice.</i></b> Unfortunately, not all ISPs use POP3 mailbox schemes that will work with this approach: some use a non-standard header to record the address of the person for whom the message was actually intended - for example, "X-Deliver-To" is one that is seen from time to time. If your ISP uses a non-standard header to record the delivery envelope address, you can tell MercuryD about it using the Headers control: type in the name of the header Mercury should examine for local addresses (so, from our example above, you would type in X-Deliver-To). The field is not case-sensitive (so, X-Deliver-To and X-DELIVER-TO are treated as identical) and you can add the colon separator at the end of the name or not as you wish. If your ISP uses more than one special header to identify the local addressee, you can enter multiple header names in this field, separated by semi-colon characters (";"). You must not type any spaces in this field. If you check the control labelled Check only in these headers then MercuryD will no longer examine the standard To, Cc, Bcc and Received headers for local addresses <i><b>and will not discard duplicate messages</b></i>. Use this control only if you are sure that your ISP always adds the header to your mail. Your ISP will usually be able to tell you if they use a special header to identify the envelope address in your messages. </p>

My wife and I are both members in a club that sends notices via google groups.  Therefore two identical e-mails arrive via MercuryD, one addressed to her, one addressed to me.  One of these e-mails will be suppressed, and it is luck-of-the-draw whether I get the remaining one or she.  Is there any way to disable this feature? 

Thanks, Eric T.

<P>My wife and I are both members in a club that sends notices via google groups.  Therefore two identical e-mails arrive via MercuryD, one addressed to her, one addressed to me.  One of these e-mails will be suppressed, and it is luck-of-the-draw whether I get the remaining one or she.  Is there any way to disable this feature?  </P> <P>Thanks, Eric T.</P>
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