Double checked hotmail and found the email was sent to spasm, So it is fixed.

AOL on the other hand, not spasm but get lost for a while.  Sent 10:30 am, finally show up in the inbox at 5 pm. Novertheless, it arrived.

Thank for all the help.  We are slowly picking up how the program work.

At this point, our problem, of course, is still addressing the incoming email.  It seems our ISP only recognized the standard emailaddress@co-name.com format.  At least the work around works.

First, may I ask am I using the right program?

We have a DSL conection and one   email account (something like Co-email@coname.com)

We would like to like to link to pegasus mail system so 4 to 5 local users can access to the external email account at the same time email locally.

I assume Mercury can link the external to pegasus so each user can receive email addressed to them thru Co-email@coname.com but not sure how to set up Mercury.

The manual said I should install Mercury D and Mercury E but I am loss during configuration.

How outsider can address each user through our external email account?

Assuming that coname.com is a domain that you own and that your Internet provider has set up a domain mailbox for you (to which all messages for coname.com are delivered, regardless of the recipient name before the @), you can use MercuryD to collect the messages and distribute them to your local users. Someone sending messages will simply address them to user1@coname.com, user2@coname.com etc.

If your Internet provider allows you to send email directly to the Internet you can use MercuryE (the direct-delivery SMTP module). If the provider blocks port 25 you should instead use MercuryC to relay messages through a SMTP server that your Internet provider runs.

/Rolf 

Thank for your reply.

Although we have register the domain name, our ISP only allow us to set up limited number of mailbox.  Incoming email can be delievered only when addressed to the specific address. 

At this point, I have set up one user that match the email address and all other local users will receive mail forwarded by using filtering rule by addressing in the subject line.

Hope there is a better way.

If the mailbox that your Internet provider has set up isn't a domain mailbox, where all mail addressed to any user in the domain is placed, then the alternative would be to use Mercury to handle incoming SMTP connections for the domain as well. To do that you need a fixed IP address, and you should ask your Internet provider to change the MX pointer for the domain.

/Rolf 

There may be some other possibilities here.  Many ISPs will handle the "+" convention in usernames.  So, it might be possible to ask users to use addresses like username+user1@domain.com username+user2@domain.com.  Mercury can then recognize these in To: Cc: etc headers in global filtering and route messages accordingly.

I may have initially misunderstood your question.  My impression was that you wanted each user to receive every message, i.e. all users receive the same messages.  If this is the case, the global filter approach that you have tried will work, or you could set up a distribution list in Mercury.

Regarding needing a fixed IP address, I don't think that this essential for SMTP to work correctly.  My ISP doesn't offer fixed IP addresses unless one pays for a more expensive business account.  Even without this, IP addresses don't change very often .... in fact I have found it quite difficult to make this happen.  I would need to disconnect my DSL modem for several hours for the ISP to "forget" the old IP address.  My IP address has only changed a handful of times in several years (maybe I am lucky with my ISP).  However, to avoid problems when there is a change, I use an application called DirectUpdate.  This tracks the IP address and causes changes to happen to DNS records. There are several applications that can do this.

Gordon

using + does help.  Still come back as undeliveried.

Testing the program further and encounter another problem.

We have another email address using the same domain name but set up in outlook.

So when we start testing the pmail and mercury, we are using outlook to send and receive email from our second email account.  There is no problem.  The email when out of Mercury and reach outlook thru internet.

When I try to send to other emails such as hotmail or aol.  Mercury stmp show the jobs are done, but nothing come in at hotmail or ao.  The strange thing is that when we send a incoming mail from hotmail, then using reply the send out a replying email, it reach the hotmail account.  The address is exactly the same, the raw view only show a difference with

X-RS-Header: In-reply-to: <col110-w37FFAE70F19A9E6263AE70C3520@phx.gbl>

X-RS-Header: References: <col110-w37FFAE70F19A9E6263AE70C3520@phx.gbl>

What can be set wrong?

Forget to mention, we are now using Mercury C - relay outgoing instead of Mercury E - direct sending.

Each Mercury module has its own log file, so even if the MercuryS log shows that a message has been received correctly you will need to check the MercuryC log to see that the Internet provider's server did accept it.

If the message was accepted by the relay server you will have to contact your Internet provider to find out why it didn't reach the final destination.

/Rolf 

Maybe there are too many issues being dealt with at once here.  As a first thing, if you send mail to your primary account from,say, Hotmail (I presume that you have an account that you can send from), do you receive it through your Mercury server in your local PMail account.  If that works, if you want to test the "+" form of addressing, try sending the same thing again, but add +test to the username.  If you are using MercuryD to pick up mail from your ISP, whether this works will depend on your ISP's mail handling.  Gmail supports this, but my ISP (Rogers, Canada) does not.  If you use Mercury S, this will support the + convention, though you need to check the appropriate box in Mercury Configuration/Mercury Core Module ..../Advanced.  I have just tried this and confirmed that it works.

Gordon