Sorry about this - the POP3 modules were not downloading anything. No *.MD files were in the folder.

What was happening was that the MessageLabs banner was not visible in one view - all mail defaults to plain text view, and although the banner is visible in the majority of these, it is not visible in others. Switching views revealed the banner. And the spam mails are addresses to two people who have filled out online surveys and and have not un-ticked the 3rd party mail request.... grrrr

Sorry for the false alarm.

Hi again

We have two POP3 accounts defined in the Mercury POP3 module. Both are presently disabled. This morning I discovered that even though they are both disabled, Mercury was still downloading from one of them.

I wanted to keep the account information within Mercury, but did not want to use them while we are testing the SMTP server. Can anyone suggest a way to tell Mercury not to download from either of the POP3 acounts please?

[quote user="Greenman"]

Hi again

We have two POP3 accounts defined in the Mercury POP3 module. Both are presently disabled. This morning I discovered that even though they are both disabled, Mercury was still downloading from one of them.

I wanted to keep the account information within Mercury, but did not want to use them while we are testing the SMTP server. Can anyone suggest a way to tell Mercury not to download from either of the POP3 acounts please?

[/quote]

Check again.  MercuryD will not download when the POP3 setups are disabled.  Make sure you pause MercuryD though when making changes since changes will not be affected when the process is active.  Also make sure you are not running two instanses of mercury/32.

Thank you, Thomas. Since disabling both accounts I have manually stopped and restarted Mercury several times, and have re-checked the POP3 configuration each time too. The server has also been restarted twice since this change was implemented, and I am the only person to log onto it. It is definitely downloading from one POP3 box. I know this because at present the only mail being collected is via the SMTP module which collects mail from MessageLabs servers, all of which have a banner appended. The POP3 mail is all addressed to one domain, and is spam.

I'll remove the POP3 module from Mercury, and restart Mercury.

[quote user="Greenman"]

Thank you, Thomas. Since disabling both accounts I have manually stopped and restarted Mercury several times, and have re-checked the POP3 configuration each time too. The server has also been restarted twice since this change was implemented, and I am the only person to log onto it. It is definitely downloading from one POP3 box. I know this because at present the only mail being collected is via the SMTP module which collects mail from MessageLabs servers, all of which have a banner appended. The POP3 mail is all addressed to one domain, and is spam.

I'll remove the POP3 module from Mercury, and restart Mercury.

[/quote]

This almost sounds like you are running multiple copies of Mercury/32.  Are you absolutely sure that there is only one running? Try using Task Manager to verify.

Just checked Task Manager, and there is just one copy of Mercury running.

[quote user="Greenman"]Just checked Task Manager, and there is just one copy of Mercury running.[/quote]

There is no way in the world that MercuryD will continue downloading when disabled unless it was active when you were doing the disabling so it did not take affect.  Pause MercuryD and then go in and disable all of the POP3 accounts.  Verify they are disabled and then unpause.

[quote user="Greenman"]

We have two POP3 accounts defined in the Mercury POP3 module. Both are presently disabled. This morning I discovered that even though they are both disabled, Mercury was still downloading from one of them.

Thomas and David - thanks for your replies.

As I said, I have stopped and restarted Mercury several times, and have also restarted the server and checked the POP3 settings.

Here is a screenshot.

Again, the only mail we should be receiving is via MessageLabs, using the SMTP server. The only IP addresses allowed are those given us by MessageLabs when we set the service up. As you may be aware all mail filtered by MessageLabs has a banner appended identifying it as being processed by MessageLabs servers.

The mail in question has no banner, and is addressed to the second domain seen in the screenshot. When disabling the POP3 accounts, the first one was disabled and then about 2 weeks later, the second was disabled. All the mail is spam.

Is there any setting that could possibly overide this?

Edit:

Mercury is the only mail server running.

[quote user="Greenman"]

Thomas and David - thanks for your replies.

As I said, I have stopped and restarted Mercury several times, and have also restarted the server and checked the POP3 settings.

Here is a screenshot.

Again, the only mail we should be receiving is via MessageLabs, using the SMTP server. The only IP addresses allowed are those given us by MessageLabs when we set the service up. As you may be aware all mail filtered by MessageLabs has a banner appended identifying it as being processed by MessageLabs servers.

The mail in question has no banner, and is addressed to the second domain seen in the screenshot. When disabling the POP3 accounts, the first one was disabled and then about 2 weeks later, the second was disabled. All the mail is spam.

Is there any setting that could possibly override this?

Edit:

Mercury is the only mail server running.

[/quote]

No override setting at all.  I guess it's possible if you are using a proxy between MercuryD and the POP3 server that the proxy does not get the word that the POP3 account has been disabled.  I have no clue if this is even possible but it's the only thing I can think of that would cause the POP3 download.  I would recommend turning on session logging in MercuryD and then disable the POP3 accounts.  When you disable the account verify this by opening and closing MercuryD configuration to ensure they are disabled.  You might also try pausing MercuryD before doing the disabling so you are sure that MercuryD is not active when you are doing the configuration change.  Now if the mail is downloaded by MercuryD there should be a *.MD log file of the download.

Thanks, Thomas.

No proxy is used.

I've turned on session logging, so I will post back in a couple of days with the results.