[quote user="pleyraki"]I am using pop client to receive the mails. Thanks.[/quote]
That is probably why you are having the problem. When the exact same message is received MercuryD via for multiple users only the first one one will be processed. You need to look at the headers of these messages to see if there is a X-Envelope-To:, or similar (but not X-Delivered-To added by Mercury/32) and use that for delivery.
From the MercuryD help:
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.
<p>[quote user="pleyraki"]I am using pop client to receive the mails. Thanks.[/quote]</p><p>&nbsp;</p><p>That is probably why you are having the problem.&nbsp; When the exact same message is received MercuryD via for multiple users only the first one&nbsp; one will be processed.&nbsp; You need to look at the headers of these messages to see if there is a X-Envelope-To:, or similar (but not X-Delivered-To added by Mercury/32) and use that for delivery.</p><p>From the MercuryD help:</p><p>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.
&nbsp;</p>