I run Mercury on a dedicated Win7 PC, not as a service, logged in as a domain user (comparable to a standard local user with limited access to files on servers).  I manage it as the same user so thought the answer was "no" to your admin question but upon further investigation I see that I have granted full permissions to C:\Mercury by Authenticated Users.  So, admin equivalent permissions to Mercury without being a local admin.

This PC is not publicly accessible so granting full permissions to C:\Mercury by Authenticated Users was a lazy way of allowing access to whoever I might login as.

Hello,

After some fine-tunings, I got my attachment-based rule to work (from my previous posts). Now the issue is that when Mercury is run as a service it doesn't run the POP3 module to download the messages, and I have to close the instance that is running as a service and start it manually, at which point it does work properly. If my server restarts and I don't notice, the messages don't get downloaded until I do.

Is this a known limitation/bug? This makes no sense to me, as if I want to run Mercury as a service, it should be fully functional. Could there be a setting I'm missing?

Running latest version on a Windows 2008 R2 server.

The only thing that comes to mind is that the default path may be different when running Mercury as a service, so make sure that working directory in MercuryD configuration is specified with full path.

When you run Mercury manually to configure it do you 'Run as administrator'?

I once ran into an issue where Windows was redirecting the .ini file when I did not 'Run as administrator' when manually configuring.

[quote user="Rolf Lindby"]

The only thing that comes to mind is that the default path may be different when running Mercury as a service, so make sure that working directory in MercuryD configuration is specified with full path.

[/quote] 

Thanks, Rolf.

I'll look into it.

EDIT: I checked and yes, I have full paths. I'll look into the other suggestion given above. 

[quote user="apshore"]

When you run Mercury manually to configure it do you 'Run as administrator'?

I once ran into an issue where Windows was redirecting the .ini file when I did not 'Run as administrator' when manually configuring.

[/quote]

I don't think I ran it as admin when I set it up. I tried running both as admin as non-admin, and the settings are there in both cases, so I'm baffled.

Thanks for your reply.