Normally the program called by the policy will be visible. There are workarounds to make it run hidden as outlined here:
 

 /Rolf
 

Yeah, I was ready for that part (tedious, but not really difficult).

 I can not believe how easy this was.  David Harris ROCKS!

And thanks for the help, I do appreciate it.

MR 

Thank you. I didn't know that.

Mail sent to simply user instead of user@domain.com will have an X-Envelope-To: address of a simple user name rather then a full SMTP address.  This happens in a number of ways but most common is through the use of MercuryD and delivering using a user name in the MercuryD setup.  I do not know how you are setup but you must not be delivering via an alias, filter, MercuryD, etc using a simple user name or the forwarding will fail.

Looks like it, the Received headers repeat every (approx) 30 seconds, which presumably is your Core polling interval.

With the filesystem unable to remove the file it would get hit at every poll. 

Sounds like you're running a very resource tight system.
Mercury runs fine on such, provided you do not overuse RAM or have very little disk space left.

Periodically we purge the hidden windows update directories, and all the different temp directories that Windows uses. Via the scheduler we defrag every volume every night, and this is done after any backup is done, which also is done nightly. We do however only backup configurations and data, space would be impossible else.

The only case when Mercury could overuse the disk is by using up session log space, under heavy load. Be very careful about enabling session logging. Session logging is nearly the same as many others call debug logs, and they consume power as well as disk.

Tools we frequently use are:
SpinRite from Gibson Research CnW Recovery www.cnwrecovery.com
Filemon and TaskInfo

If ChkDsk solved your problem that was fine, but if you suspect any disk errors, you should first check the disk with diskmanager, then check the event log. If we still suspect disc-related problems, we run SpinRite (if it's not a RAid 1,5,6 unit), then lastly run chkdsk. However if you have mechanical errors on a disk, ChkDsk seriously damages the MFT and you will have real trouble getting your data back. You will notice problems with the mechanics if simple copy or ntbackup freezes. Then unplug the disk, insert into another computer and use CnW to read sector by sector to an image, and restore from that image whatever you can.

Best of luck

Thanks Rolf Lindby.

We get very little spam with blank subjects.. but we get quite a few from suppliers and clients that don't include the subject line.
I think it's good to make them include a subject... Makes it easier to find / store the email.

PLEASE ADD IMAP FILTERING SUPPORT

SpamHalter needs good database contents to work properly, and it needs to be trained with real messages from your environment. I would suggest that you start over and restore the default settings (which in most cases will work fine). Download the sample database from SpamHalter homepage (http://www.ararat.cz/download/words4.zip) and import it using SpamHalter Tools. Then you need to add spam messages and good messages from your own mailboxes. Take all you can get (yes, really all) and follow the instructions in the manual:

You must have prepared two directories with a lot of emails saved as text files. One directory for spam messages, the other for nospam messages. Each text file is one RAW message for database. To create these text files you can use the save message feature from Pegasus Mail. Then you must run SpamHalterTools.exe. In the window you can specify your directories with messages, and then add the contents of these directories to the database by hitting the corresponding button.

When that's done keep sending corrections to the Spam and Nospam mailboxes. Check the log to verify that the updates really work.

/Rolf 

Peter, David,

thanks to your quick responses and davids magick (coding) it's solved: the provided pre-release candidate (only changing MERCURYP a bit) now works nearly flawless. The POP3-Server is a lot faster than it was in 4.52...

Thanks a lot to everyone - keep on that great work! (I think the "big" competitors never can keep up with that flexibility and reaction-time...)

Kindest Regards!

P.S.: Nils: Thanks to David's bugfix there's no more need to work around anymore - thank you anyways...

Installation is the same, should be no problem!

/Rolf 

If you run Mercury and Outlook on the same computer localhost (or 127.0.0.1) can be entered as incoming and outgoing server in Outlook. The Internet name for the system can not be localhost. If you have a domain of your own it could be for instance mail.mydomain.com, or if not, it should be the hostname of your computer. You can leave Identify myself as in MercuryE configuration empty (it should not be "admin").

If you have a domain and Mercury is assigned to handle mail for that domain you can create your own mailboxes in Mercury. Then your email address will be in the form mymailbox@mydomain.com. If not, use an email mailbox set up by your Internet provider, and download to Mercury with the MercuryD POP3 client.

Filling in Local domains in Core configuration is critical to getting the system working correctly. Please read that section of Mercury help carefully.

If you are connecting to the Internet from a home subscriber connection your Internet provider often blocks certain mail services. You may need to use the MercuryC relay client rather than MercuryE to deliver mail if port 25 is blocked. There is more information about this in Mercury help.

/Rolf 

Did anyone find a solution to this problem?

 I recently installed all new computers in a small office (5 machines). All new (pre-loaded) software on each. I moved the Mercury

Mail over to the new server computer and it seems to be working fine but I have several machines that will not display the 

subscribed folders consistently. I have seen this in the past and have not found a good solution. What is going on or where do I look?

 We are using Outlook 2007 but I have also seen this issue on Outlook Express and Thunderbird. I am running Mercury Mail v4.62.

Any help would be appreciated.

Curt

That's a pretty good thought dilbert. You were right - the IIS SMTP was running. I turned it off since I haven't been using it anyway. Hopefully that fixes things. THANKS!

Thanks a lot
 

Thanks to everyone for their help.  Setting my old Win2K machine in my basement as my own ISP has been a fun and challenging experience.  I'm learning a lot.

For the record: If you are on a dynamic IP it is best to use MercuryC and use someone else's SMTP server since most dynamic IP's are blocked to prevent potential spam.  

Thanks Rolf,

Have picked that up too. This is a very helpful tool and your support has been fantastic, I thank you for all your contributions and hopefully you'll not have to hear from me again anytime soon!

 Regards

Craig

Well, all seems to be quieting down on their Mercury. I think they will be dealing with spam rejections from other servers for a day or two, but they can handle that. I do appreciate all your help. If it chokes again, I will be back!

Mercury currently has no filter rules to move a message into a named user folder.  It can only be moved to the mailbox (new mail folder).  This function is on many wishlists but is not expected in the next version being prepared for release soon.

An alternative is to create a specific user mailbox just to handle these messages.

Your question is too general to work with.  Get a copy of Mercury/32 v4.52 from http://www.pmail.com/downloads and install is as an update over v4.01 that comes with XAMPP and then read over the manual for setup process.  It's pretty straight forward but it's not trival and it depends a lot on the specifics of your installation.  When you get done doing this then come back with specific questions about what you are trying to do and can't get to work.  You can also go to http://kbase.pmail.gen.nz/mercury32.cfm and get a lot of info on the setup as well.  You can probably search on XAMPP in this forum as well to get a lot of help since there XAMPP setup questions come in over and over.  ;-)

If you are working in a Novell environment and the pmxf.ini file hasn't been automatically created, try creating it manually (see Thomas' post of 2008-06-17 for details).

/Rolf