[quote user="Greenman"]Regarding the spam issue - that is exactly why I do not want all the mail to be downloaded. These people will ultimately need to manage the Mercury installation. It will be far easier for them to review the spam folder on the web site and forward false positives than it would be to manage all the aspects necessary to effectively filter out spam, and then still have to review the spam account for false positives.[/quote]

IMHO, leaving it on the server is only an option if detection of false positives is not a concern.  Bringing it down, filtering it to a SPAM user and adding the SPAM user mailbox as an added mailbox to someones folder list avoids the 'out of sight, out of mind' syndrome.  If you do bring it down, add filters to auto remove all the vulgar ones, nobody needs to see that crap!  I would be happy to share my filters with you if you decide to go that route.

Hi

Within Pegasus Mail there is an option when setting up POP3 access to delete the mail from the server once it has been retrieved. Is it possible to do this with the POP3 client in Mercury?

I ask because I am setting up a mail server for a very small charity who want a copy of their mail on their local network. I can configure their MX records to direct mail to their network, but they will get all the spam too. I know I can install Spamhalter to sort this out but it requires a lot of intervention and these people are not at all technical.

I was wondering, therefore, if the POP3 client - MercuryD - could be configured to get the mail from their existing web-based email server which already strips out the spam, and then delete the mail from the web-based server so it does not fill up and reach capacity.

I can't see any way to configure this. Is it possible?

Thanks!

MercuryD can not be configured to leave mail on the server. 

Regarding spam, if the spam remains in the inbox of the web mail host then let MercuryD bring it down and filter it using Mercury filters.  If the web mail host diverts spam out of the inbox consider changing that to keep it in the inbox and bringing it down.  If you don't bring it down there is no easy way to check for false positives which may or may not be a concern.  If it is, you can configure Mercury to filter all spam to a "SPAM" user and have someone review it for false positives before deleting.

FWIW, I use MercuryD to POP hosted mailboxes.  I found the spam filter on my host to be too unreliable for business use so set it for loose detection and use POPFile in conjunction with Mercury as my local "trainable" spam filter (this was set up before Spamhalter was included in Mercury).  I then use Mercury filters to filter all spam to a Spam user.  I have the Spam user as an added mailbox in my Pegasus which makes it convenient to routinely review it for false positives.  I also have a bunch of filters both at the Mercury level and the Pegasus level that auto delete known spam.

Thanks a lot for the confirmation Brian.

Regarding the spam issue - that is exactly why I do not want all the mail to be downloaded. These people will ultimately need to manage the Mercury installation. It will be far easier for them to review the spam folder on the web site and forward false positives than it would be to manage all the aspects necessary to effectively filter out spam, and then still have to review the spam account for false positives.

Cheers!