Community Discussions and Support

The perfect forum for general discussions or technical questions about Mercury Mail Server.

PiS posted May 11 '07 at 11:51 am

[quote user="Methuselah"]
Local Users:
 Username=TechnoMail, Personal Name = Robin Martin

Core/Local Domain:
  LocalHost = YMCSERV, Internet name = technolib.coza

  Alias=robin@technolib.coza, Real address=TechnoMail

THIS WORKS - via Mercury spooler only . . .  at last !![/quote]

My goodness, you're really good at trial and error. Now here is an explanation:
Real Address within the Alias configuration, is either

  1. A local mailbox, a local user in netware, (or later a local user in Windows AD)
  2. An off-host recipient - we call it a relay address then, since the email is relayed out of this system.

Configuration interfaces is hard to do that are so intuitive that someone with limited knowledge can set this up. As programmers it is also very hard to imagine, how someone not involved in the lingo reads the interfaces.
Nonetheless, you DID IT! Congratulations.

dkocmoud posted May 22 '07 at 11:37 pm

Just to clarify:

  • MercuryS: SMTP Server module that receives incoming SMTP email from SMTP clients and from other SMTP servers.
  • MercuryC or MercuryE: SMTP Client module that sends outgoing SMTP email to other SMTP servers; MercuryC is a relay client that simply relays all outgoing mail to a specified SMTP server whereas MercuryE is an End-to-end delivery client that can do domain name resolution in order to contact the recipient's SMTP mail server and deliver the SMTP email message directly.
  • MercuryP: POP3 Server module provides new emails to POP3 clients
  • MercuryD: POP3 Client module downloads new emails from other POP3 hosts on behalf of your users

I recommend that you keep the "do not permit SMTP relaying of non-local mail" option enabled at all times.  Otherwise, your Mercury server will become known as an "open relay", which is a bad thing and which will get your Mercury server's IP address added to various blacklists.  Instead, I recommend adding your local subnet(s) to MercuryS's connection control's Allow column and optionally enabling the "strict relaying" option.  If you have any remote users that use public IP addresses outside of your control, then see about using SMTP authentication in Outlook when relaying email through Mercury.



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!

-- David Harris --
mangrove posted Mar 13 '07 at 1:11 am

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.
Hide topic messages
Enable infinite scrolling
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft