[quote user="Methuselah"] Local Users: Username=TechnoMail, Personal Name = Robin Martin
Core/Local Domain: LocalHost = YMCSERV, Internet name = technolib.coza
Aliases: Aliasemail@example.com, 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
A local mailbox, a local user in netware, (or later a local user in Windows AD)
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.
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.
When two Mercury/32 processes are running simultaneously (by mistake) both are polling the same queue, leading to several identical mail being delivered.
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.
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.