Yes, the switch in the Core configuration is on, so I don't know what the problem is.  I have more urgent things to deal with at the moment, but I will come back to it later.

Thank you

Gordon

I wish to change the machine that runs Mercury so, as instructed elsewhere, I am attempting to simply copy the whole Mercury folder over to the C: drive of the new machine.  This is Mercury 4.72 (not being run as a service) and both the source and target machines are running Win XP SP3.

The copying process gets underway but eventually stops with a message saying:

Cannot copy Certificate: Access denied.

Make sure the disk is not full or write-protected

and that the fle is not currently in use.

There is plenty of room on the destination machine/partition and I can't see any sign of the file being write protected.  Mercury on the source machine is not running, so I don't see why the file should be in use.

Any help would be appreciated.

Gordon

What certificate is that more specifically? Could some other process on the source server be accessing it?

/Rolf 

Rolf - I don't know.  I presumed that it is a file called Certificate, which came with the 4.72 distribution.  It is showing a modified date of 2 Aug 2008.  It is in the top level MERCURY folder.  Having noticed that blat.exe was installed on the day after in the MERCURY folder, maybe it is something to do with that.  blat, which I do use, shouldn't really be in this folder, so I may have some tidying up to do.  I can't remember what I did with this 2 1/2 years ago!

If you don't think it is anything to do with Mercury, I will tidy things up before I attempt to copy again.

Thank you

Gordon

It's not a file created by the Mercury installer, anyway. So try copying other files and see if everything works without it.

/Rolf 

Thank you, Rolf.

I am still considering how best to achieve what I want to do.  If I simply copy the MERCURY folder over to the new machine, I will probably want to stop the old machine running Mercury as soon as I start up Mercury on the new one, so that I don't have some new mail on the old machine after the copy has taken place.  The copy process will take quite a while, as the size of the MAIL folder is almost 7GB.  Also, I am concerned that something on the new machine will not work straightaway and I will have to do some troubleshooting.  I am using various supporting scripts and also blat and stunnel, so there is defintely scope for things to go wrong.  I think that what I would prefer to do is to get the new machine working together with all of the scripts and supporting apps and then switch it over to be the "production" machine once all is working correctly.  If I do this, is it possible either to replace the new machine MAIL folder with that on the old machine or can I copy the files from the old MAIL folder into the new MAIL folder?  Will this work?

Thank you

Gordon

You can start by just copying the program without the mail folder, create some test users, and do your testing. When you are ready to go just shut down Mercury and replace the mail folder with the one from the other server.

/Rolf

Excellent!  That's exactly what I wish to do.

Thank you

Gordon

The transfer to the new PC seemed to go fine and I am just sorting out some of the clutter that had accumlated in the old Mercury folder, so it's not in the new one.  In fact, I am now running both the new system and the old system side-by-side, to check that they work the same way (this is largely my SPAM control measures, not Mercury itself).  To run this side-by-side arrangement, I set up a new account with my ISP and then copied all messages to that new account.  The new PC Mercury then downlaods mail from this new account.  The only way that I found to copy all messages to the new account is to add a fowarding rule at the beginning of the filtering rules.  This means that the content contol is still done on the old system (I have disabled this on the new system, so that content control isn't done twice).  Is there a better way to do this?  I would have ideally liked to have sent a copy of each message to the new account before Mercury starts to process any of the content, but I couldn't see how this could be done.  As I understand it, it's not possible for Mercury D to leave mail on the (ISP) server, so that doesn't seem to be an option for both new and old servers downloadng the same messages from the ISP.

Thank you

Gordon

[Edited] 

OK, I found it!  I see that I needed to turn on "Allow file-based forwarding specification using FORWARD files" before the forwarding option shows up in the individual accounts in "Manage local users ...".  I haven't found anything to globally forward all messages for all users, but the small number of user accounts that I have doesn't make this a problem.

Gordon

Automatic forwarding isn't working as I expected.  Does the copy of the message being forwarded get processed by global filtering rules?  If so, this doesn't do what I need.  I just want a "clean copy" of the message to be forwarded to another address.

I am a little confused by the format of the FORWARD file.  In the help file for the forwarding set-up, the format is shown as:

Forward-To : <address>
Deliver-Also : Y|N

Note that there is a space before the colon on each line.  I suspect that this space shouldn't be there (it is not shown in the wording underneath the forwarding set-up window ... or maybe it doesn't matter).

Also, should the angle brackets be present in the forwarding definition?  I suspect that they should not be, i.e. a correct definition would be:

Forward-To: somebody@somewhere.com
Deliver-Also: Y

Is my understanding correct?

Thank you

Gordon

[quote user="GordonM"]Also, should the angle brackets be present in the forwarding definition?  I suspect that they should not be, i.e. a correct definition would be:

Forward-To: somebody@somewhere.com
Deliver-Also: Y

Is my understanding correct?[/quote]

That is exactly how I write my Forwarding files and they work perfectly - I use multiple Forward-To: lines as well.

Thank you for the confirmation, Paul.  I still haven't got autoforwarding to work.  I have the correct entries in the FORWARD file, but nothing happens ... no forwarding takes place.  For the time being I have given up and gone back to putting a forward rule in the filtering rules.  That works fine.  This is all just for testing, so it doesn't matter too much which way I do it.  I'll probably go back and try to make autoforwarding work some time, just to make sure that I understand how I should be setting it up.

Gordon

File-based forwarding should be quite easy to set up. Just remember that you need to switch it on in Core configuration / Advanced / Allow file-based forwarding specification using FORWARD files.

/Rolf