[quote user="chriscw"]We do run Spamhalter on the server but not clamwall I could never work out how to get it to work.  I guess that now we have a few Outlook users Ii maybe should have another go.[/quote]

For me Clamwall is a 'must have' first line protection for incoming mail.  I use some of the Sanesecurity signatures as well to catch spam as well as viruses.

Post on these forums if you are still having problems setting it up - the windows binaries from ClamAV are now very stable.

Some of my colleagues wish to use Microsoft Outlook, I know they are insane masochists but there you are.  What are the options for linking Outlook to Mecury?  I know we can do it using IMAP and I assume we can do it using POP3 with the caveat that Outlook will then store all messages locally because as far as I know it is not designed to work from a mail server.  

 Is there a way to make Outlook store its mail on the server is connecting via POP 3 or is there any other way of getting Outlook to work with Mercury? 

I have Outlook 2007 installed and have tested with IMAP which works fine in my limited testing.  As for POP3, Outlook has config options that allow for leaving messages on the server but I have never tested a POP3 account.

IMAP would be my recommendation.

If you mean "store mail on the server" like a network install of Pmail does - you could probably store the pst file (separate one per client) on a network share (on the server) but it would likely be horribly slow and unreliable.

 edit: it IS designed to work from a server, as long as that server is Exchange...

The Outlook datas are stored in the user's profile (in Microsoft\Outlook under AppDatas), you can enable the roaming profiles on the domain and then find your Outlook datas on any station you log on, this works fine with the pop3 protocol, the problem is that you can't access your mail datas when you're not logged on the domain (from outside for example), if it happens to the user a better choice is to use the imap protocol which works from within your local network and from outside (Mercury has to be reachable from outside).

Regards

Because most of our Outlook users also connect on their Android tablets and mobiles I guess we will have to stick with IMAP on Outlook too.

I di find though that mecury.exe was only running on CPU 1 on our server which meant the CPU was often saturated and flat lining.  I set the CPU affinity for Mercury to use CPU 2, 3 and 4 instead which seems to have greatly improved matters.  If I restart the Mercury program I have to set the CPU affinity again which is a bind but at least it now works much better.

[quote user="chriscw"]

Because most of our Outlook users also connect on their Android tablets and mobiles I guess we will have to stick with IMAP on Outlook too.

I di find though that mecury.exe was only running on CPU 1 on our server which meant the CPU was often saturated and flat lining.  I set the CPU affinity for Mercury to use CPU 2, 3 and 4 instead which seems to have greatly improved matters.  If I restart the Mercury program I have to set the CPU affinity again which is a bind but at least it now works much better.[/quote]

Do you run Clamwall, Spamhalter or any policies?  Maybe one of those is causing the flat lining.

We do run Spamhalter on the server but not clamwall I could never work out how to get it to work.  I guess that now we have a few Outlook users Ii maybe should have another go.