That sounds like the mailbox at some point  was accessed from a different device, maybe a smartphone, that marked a number of messages as "read", preventing the normal POP3 client from getting them. If MercuryP was set to create a log file (needn't be a session log in this case) it might be possible to locate a different IP address there.

Greetings,

So I have been successfully using Mercury for years to poll a domain catch all account and then sort and deliver mail to several users.

Just recently one user is not getting all mail that Mercury has dropped in the users c:\mercury\mail\cakyle folder. When we log into mercury for that user some mail comes across and other messages are left behind. Seems random?

She has been using Mozilla Seamonkey as a client. I tried adding that account to my Thunderbird client with the same results. Messages that are in the box are not all delivered.  We are moving the messages to the client so the folder should empty after a pickup.

Any ideas why we can't get these messages delivered to the client from the server?

Running version 4.74 on windows home server. I have tried a few different things with no luck.

Thanks in advance for any assistance.

Matt

Is that using POP3 or IMAP access? Anyway, the best way to track such a problem is probably to temporarily switch on session logging for the appropriate module and see the full conversation between the client and the server.

Upgrading to the current version (4.80) is by the way always recommended.

Using POP3 access.  I think I solved the problem but I am not sure why it started misbehaving?

In the POP3 server global settings I unticked the "mark successfully retrieved mail as "read""

and "offer only unread mail to connected clients".  Client then downloaded all messages from the folder.

Mercury has worked so well I rarely look for updated versions, I will move to 4.80 soon.

Thanks fort he response.