[quote user="Greenman"]Resetting/editing pconfig files is a pita because I have to copy them to a 32bit machine, make the changes then copy them back to the 64bit server.[/quote]

There's an easier way - install DOSbox on the 64-bit machine and then you can run pconfig.

See this thread http://community.pmail.com/forums/thread/20369.aspx

Hi

I should know how to do this but can't get it to work...

We use Pegasus Mail with Mercury on a Windows network. Pegasus Mail's program files are accessed from each client PC via a shortcut that links to the program on a server. Pegasus Mail is, therrefore, not installed locally.

One of our staff, Fred, has recently left and I need to copy mail sent to his internal address to another user. So, if I send a message to Fred and type fred in the To: field it will be delivered to Fred's mail account. I want to ensure that a copy of that message is also sent to John's account who has taken over Fred's job.

I have set up two global rules in Mercury: Copy messages sent to fred@domain.com to john@domain.com. This works fine. I have set up a second rule where messages addressed to fred are copied to john - the domain name is not present. The problem I am having is that messages where just the internal name is used in the address (To: fred) the messages are not being copied to John's account.

Can anyone help me with this, please?

Thanks!

There is an easier way than using filters.  It is called a Forward file.  Placing a Forward file in Fred's mailbox directory will insure that Mercury forwards all message to the addresses listed in the Forward file.  See details in the Mercury manual (pg 21). 

Here's the caveat.  Mercury must be configured so that local messages get passed through it otherwise local mail bypasses Mercury.  Your filter on the local username of Fred are failing which suggests that your local mail may not be passed through Mercury.  This setting is in the gateway configuration of pconfig.  It's the last option, "Force all mail through".

Thanks a lot.

Resetting/editing pconfig files is a pita because I have to copy them to a 32bit machine, make the changes then copy them back to the 64bit server. So this option to control how Mercury deals with locally addressed messages is not available through the Mercury GUI?

I'll look into using the Forward file. Thanks for the page number - that's great :)

Cheers!

[Edit]

Just read the manual - that's easy. Thanks again :)

> Resetting/editing pconfig files is a pita because I have to copy them to a 32bit machine,
> make the changes then copy them back to the 64bit server. So this option to control how
> Mercury deals with locally addressed messages is not available through the Mercury GUI?

Unfortunately not.  This is actually a Pegasus Mail thing.  It is capable of distributing to local users on its own, which is what you are seeing.  Pconfig handles the configuration of a gateway for Peg.

How much of a problem would it be for you to open Freds' mailbox routinely or just leave it open?  My thinking is that you could work around the pconfig issue by creating a new mail forward filter in Freds' Pegasus then either leave an instance of Peg running with his mailbox open or create a shortcut or a scheduled job that runs Peg to open his mailbox and trigger the filter rule.