fixed :-) Thanks again Thomas [Y]

Has anyone written a rule similar to this?  What works for you, other than blocking Google mail outright?

I use POPFileD and POPFile and it catches all of the 419'ers regardless of sender. It's hands off since it's analyzing the message body for the spam.

That looks to be the problem thanks for the quick help.

well what am i supposed to use???

One way is to create a GMail account for just the purpose of sending mail via MercuryC. 

right, so you're saying i need this to help prevent my outgoing emails

being identified as spam. i was confused before because i thought you

meant i need it for sending local mail (by which, to be clear, i mean

mail destined for example to user1@localhost, which mercury should

stick into a test mailbox on the same system).

since mercury is relaying the message through my gmail account, is what

you suggested really necessary?

 I think so.  Have you looked at the headers on the messages you are sending.  The Mercury/32 server is going to identify itself in these headers for each message sent through this host. 

since merc is just essentially (afaik)

logging into the gmail account and giving gmail a message to send, why

should the real original destination matter? i mean i use thunderbird

to send mail from my computer all the time, that's essentially doing

exactly the same thing merc is doing here, and there's no problem with

mail being identified as spam there...

Not really, mail sent via T-bird is being send directly to the ISPs SMTP host for processing.  Mail sent by your application (or T-bird) via MercuryS is being processed via MercuryS and queued, Mercury core and queued and MercuryC.   Each process is adding a Recieved line to the message.

Here's the headers put on by Peter's Mercury/32 server for the message I got from the comunity server.  The web process is sending the mail via MercuryS.  If you are using "localhost" as both the name of the system and the domain then it will show at least 3 times in the message.  If you are forwarding mail from ma local user there can be many more instances.

 Received: from Spooler by mail.praktit.se (Mercury/32 v4.62) ID MO0003BA;
 10 Jul 2008 01:16:31 +0200
Received: from spooler by mail.praktit.se (Mercury/32 v4.62);
 10 Jul 2008 01:16:26 +0200
Received: from web2 (192.168.1.20) by mail.praktit.se (Mercury/32 v4.62) with
 ESMTP ID MG0003B4; 10 Jul 2008 01:16:22 +0200

 This message was first received by MercuryS and queued as MG0003B4, then processed by core and queued as MO00003BA and finally taken from the queue by MercuryE for delivery to my server.

Or a better use of alias so the X-Envelope-To: address of the delivered message is a full SMTP email address.  ;-) 

Alias: abuse@homesweethome.de
Real address: admin@homesweethome.de

 Where can I get WinPMail PB1?

 "A public beta of Pegasus Mail v4.5 is now available for anyone who

wishes to do so to try out. The beta is very complete and stable, but

is provided without formal technical support - you should almost

certainly apply due diligence testing to it before using it in a

production environment.

You can download the public beta from , or a full German version of the beta from http://download-us.pmail.com/w32-451-de-pb1.exe (and yes, we realize they appear to have different version numbers).

Peter

Stromblad will post an announcement telling you about new beta-related

forums that will be made available in the community in the near future

- using these forums, you can discuss the beta and provide feedback if

you wish.

Please read the "What's new" notes in the beta installer or help file for information on the v4.5 release.

Cheers to all!

-- David --"

Thank you! *Success*! 

I will Download Mercury 4.62 and will try to configure the same.

A POP3 check in itself won't require much computing power, actually. But it's good to hear it works now!

/Rolf 

You could also set a forward file in the 2 users dir to forward to an external address (e.g. gmail).

This would avoid having to manually maintain a lot of aliases .

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