Hi - I'm sorry to see that you are still having trouble with this. For a home LAN, with a limited number of stable users, this should be fairly straightforward. Home LAN use of Mercury is also my situation.
From what you have said, I presume that you are using the MercuryS SMTP server, to collect your mail from your various contacts. So, they would be sending mail to you as (say) mainuser@yourdomain.com. Others in your home will have been allocated other usernames with the same yourdomain.com domain name. I presume that you have registered your domain name and it's associated with an IP address through DNS. If you are using an ISP which allocates dynamic IP addresses, there are other issues that I won't get into, unless this is needed.
As an example, in my case, I have several users, which Mercury knows about through Configuration/Manage local users ... For the Mercury SMTP server to know how to deal with incoming mail for these users, I define this in Configuration/Aliases .... Therefore, as an example, there is an alias set up that directs mail addressed to Microsoft-Commercial@mydomain.com to the user "Gordon" (me). There is no need to add the local domain name to the local user.
Your domain name needs to be set in Configuration/Core Module as the "Interent name for this system".
I have assumed that your are using the Mercury SMTP server. If you are not and your mail comes to accounts at your ISP, the set up is even easier. In that case you will need to use the MercuryD Distributing POP3 client, to "POP" your mail from your ISP's POP3 server to Mercury. The set-up in Configuraton/MercuryD is very simple. In my case, I have three principal accounts with my ISP and these are associated with three local usernames through the MercuryD set-up screen. If you are using MercuryD and also send your mail, using your ISP's SMTP server (via MercuryC relay client), I don't think that you even need a valid domain name to put in the Merciury core module. So far as I know, it can be anything, in this case.
You can use both MercuryD and MercuryS if you have some mail addressed to your own domain and some to a domain defined by your ISP.
I may be telling you some obvious things that you already know. However, I don't know, given the discussion in this thread so far.
GordonM
<P>Hi - I'm sorry to see that you are still having trouble with this.&nbsp; For a home LAN, with a limited number of stable users, this should be fairly straightforward.&nbsp; Home LAN use of Mercury is also my situation.</P>
<P>From what you have said, I presume that you are using the MercuryS SMTP server, to collect your mail from your various contacts.&nbsp; So, they would be sending mail to you as (say) &nbsp;<A href="mailto:mainuser@yourdomain.com">mainuser@yourdomain.com</A>.&nbsp; Others in your home will have been allocated other usernames with the same yourdomain.com domain name.&nbsp; I presume that you have registered your domain name and it's associated with an IP address through DNS.&nbsp; If you are using an ISP which allocates dynamic IP addresses, there are other issues that I won't get into, unless this is needed.</P>
<P>As an example, in my case, I have several users, which Mercury knows about through Configuration/Manage local users ...&nbsp; For the Mercury SMTP server to know how to deal with incoming mail for these users, I define this in Configuration/Aliases ....&nbsp; Therefore, as an example,&nbsp;there is an alias set up that directs mail addressed to <A href="mailto:Microsoft-Commercial@mydomain.com">Microsoft-Commercial@mydomain.com</A> to the user "Gordon" (me).&nbsp; There is no need to add the local domain name to the local user.</P>
<P>Your domain name needs to be set in Configuration/Core Module as the "Interent name for this system".</P>
<P>I have assumed that your are using the Mercury SMTP server.&nbsp; If you are not and your mail comes to accounts at your ISP, the set up is even easier.&nbsp; In that case you will need to use the MercuryD Distributing POP3 client, to "POP" your mail from your&nbsp;ISP's POP3 server to Mercury.&nbsp;&nbsp;The set-up in Configuraton/MercuryD is very simple.&nbsp; In my case, I have three principal accounts with my&nbsp;ISP&nbsp;and these are associated with three local usernames through the MercuryD set-up screen.&nbsp; If you are using MercuryD and also send your mail, using your ISP's SMTP server (via MercuryC relay client), I don't think that you even need a valid domain name to put in the Merciury core module.&nbsp; So far as I know, it can be anything, in this case.</P>
<P>You can use both MercuryD and MercuryS if you have some mail addressed to your own domain and some to a domain defined by your ISP.</P>
<P>I may be telling you some obvious things that you already know.&nbsp; However, I don't know, given the discussion in this thread so far.</P>
<P>GordonM</P>