Welcome to the Community Support forum for the Mercury Mail Transport System.

What this forum IS: 

a place where you can ask questions and give answers, where Mercury

users can share their expertise and experience with each other for

the benefit of all.

What this forum IS NOT:

an official technical support forum. Whilst I and my test teams will

participate here as much as time permits, the fact that you post a

question does not create any formal obligation on us to answer it. We

will do our best to assist you as time and circumstance permits.

Rules for using this forum: This forum is provided as a community service: as such, certain rules apply.

• No

  flames, outbursts, bad manners, slurs, abuse or rudeness. Discourteous

  behaviour will not be tolerated. Forum moderators will delete posts

  that breach this rule without notice or apology. Don't get me wrong:

  you're welcome to complain here - but if you do so, do it courteously

  and respectfully and we'll all get along fine.
  

• No spam or advertising. Don't post irrelevant messages or advertise products unless they are directly relevant to Mercury.
• No large attachments, please.
• No wishlists please - not because we don't want them, but because there is another forum specifically intended for them.
  
• No WareZ, no links to illegal download sites, no porn, no material that breaches copyright.
  

To participate in this forum, you must be a registered user of the site.

These rules notwithstanding, this forum is provided so that we can all help each other. Enjoy!

I know of three occasions where this happens:

1. When two Mercury/32 processes are running simultaneously (by mistake) both are polling the same queue, leading to several identical mail being delivered.
2. When using MercuryD (POP3 client) a mail might be too big, or a TCP/IP error might occur during the transaction. Then MercuryD won't delete the mail from the POP3 host, and it gets redownloaded at the next try. Try setting the timeout to a larger number, and increase the time between POP3 connections as needed.
   
3. Some double-mail IMAP errors with Thunderbird can be solved by setting mail.server.serverX.max_cached_connections to 1 (where X is the number of the associated account, typically 2) in the Thunderbird configuration editor.