Pegasus Mail & Mercury

Hi everyone,

since i'm a newbe to configuring mail servers this question is probebly asked a thousend times but i can't get it right. I'm running Mercury32 v4.62 on a WinXP Pro SP3 machine on a local LAN behind a firewall. The PC local IP is 192.168.1.100 and is also running a Apache web server. My ISP is hosting my domain name and collects my mail so i'm using Mercury to retrieve the mail from my ISP and redistribute it to my local users. So far this works well for retrieving and sending mail (either with MercuryC or MercuryE). The problem is that when i send a mail to an unknown local user or to my original mail address, that is not to my domain, Mercury will not collect this mail, will not send a mail to the sender and the postmaster for notification of an unknown user.

Can somebody help me in the right direction.

I'm stuck, thanks for all help.

Mark

Not sure I understand exactly how you mean, but there is a good chance the problem has something to do with what is listed in Mercury Core Module configuration /Local domains. Have a look at the help text for that segment and see if that could fix it.

/Rolf
 

Rolf,

thanx for the reply. As mentioned i'm a newbe but i think the answer is somewhere in the Core Module as you've written but i still can't figure it out. I'll try to explain my problem a bit better:

MY ISP hosts my domain called markladage.nl

Mercury is configured as follows (parts of the Mercury.ini):

[General]
myname:          markladage.nl    # Canonical name for this server

[Domains]
markladage: markladage
markladage: markladage.nl

Problem: a mail send to test@markladage.nl (test is a non existing local user) is not collected by Mercury and Mercury won't reply to the sender and/or the postmaster that this user don't exist 

I guess the problem is that the local server is named markladage.nl and the domain hosted by my ISP is named markladage.nl ???

Mark

Do you have a default user specified in your mercD POP3 definition?

If not, then any mail not addressed to a valid local user is silently dropped (including BCC's or anything without your user in the To: or CC: header)

If you try sending to your non-existing user locally (i.e. direct to mercuryS) you should get the "User not known" SMTP response, or a failure notice, depending on the mercS setting)

A single domain cannot be maintained by two separate mail servers.  If all of the users in markladage.nl are not on your Mercury/32 system then you need to change the domains section from markladage.nl to local.markladage.nl and alias all of the local users from localuser@markladage.nl to localuser@local.markladage.nl.  Now when mail is sent to test@markladage.nl and that users does not exist locally it is sent via MercuryC (or E) to the domain at the ISP.  Mail sent to localuser@markladage.nl is passed to the alias localuser@local.markladage.nl and then core sees this as a local user.

Thomas,

thanks for the help. As far is i can tell MercuryE sends the messages in good order but now there is a problem with retrieving the messages. In the MercuryD POP3 Client module i get the message:

n message succesfully retrieved

n non-local message ignored.

So it looks if Mercury does not recognize any local user anymore after aliasing them, here's an example of an user i have aliased:

mark@local.markladage.nl == mark@markladage.nl (copied from alias.src)

I can't retrieve any message anymore from any local computer on my LAN.

Mark

mark@local.markladage.nl == mark@markladage.nl

Looks like the alias ia backwards.  It should be

original address  == local alias address 

or 

mark@markladage.nl == mark@local.markladage.nl

After changing this local mail can be recieved but non-local mail is still ignored and can't be retrieved.

dilberts_left_nut:

Do you have a default user specified in your mercD POP3 definition?

If not, then any mail not addressed to a valid local user is silently dropped (including BCC's or anything without your user in the To: or CC: header)

If you are sending a message by SMTP directly to the Mercury server for a non-existent local recipient there should be an error message. If, however, the message is received by your ISP's mailserver there is no way to determine at the time of reception if the recipient address exists or not. When the message is downloaded by MercuryD it will be moved to the default mailbox (if you have defined on). It will then be up to you to handle those messages (move to correct recipient or send error notifications).

In case you want messages for the default mailbox always to return an error notification it can be done as well. One way would be to use a daemon. A global filtering rule (with Always trigger/Send a reply using a template) would be a simpler solution, but there is probably no header in the message indicating that it will be delivered to the default mailbox at the time the filtering occurs. An alias pointing to a general rule could probably do it, though. You would then enter the alias as default mailbox in MercuryD. The rule would send a reply and could then move the message to a real mailbox if you like to have it saved.

/Rolf
 

Ok,

 thanks to everyone who helped me.

i think i got the point.

Mark