[quote user="khk"]temp is empty and scratch contains only old files...[/quote]

From the Help section on configuring the queue:

[quote]Configuring Mercury's mail queues

Mercury stores mail messages it is processing in directories called Queues. All Mercury systems must have at least one queue, called the Primary Queue
, which is where jobs reside as they transit the system. The primary queue should always be located on a drive local to the machine where Mercury is running if at all possible. If you place the primary queue on a remote system, and the connection to the remote system becomes unavailable, mail may be lost or damaged.
[/quote]

Hi all,

I've got a problem with Mercury 4.72 on WinXP-Prof:

- Mercury receives mail via POP from external server,

- delivers mail to local users/mail accounts

End users work with Thunderbird (IMAP), and for test purposes I also tried to get mails via Nokia-Mail-Application (IMAP). Everything worked well for a couple of weeks without any problems. 

Since about 1 day (maybe after automatic maintenance tasks and automatic restart) Mercury receives mails via POP (as the lines in the POP window confirm) but does not deliver mails to local users. Forced shutdown of Mercury leads to a windows error message (mercury core module does not react). Restarts don't do anything good. 

I tried "forced poll" in core module window (confirmation line appears in windows) but without any real effect.

The queue folder is empty.

In the mercury/Mail/%user% folder are recently changed pnm-files.

Clients (without local message storage) can search and display old messages. 

Any ideas?

Regards

KHK

Additional information:

since the problem occurs Mercury wrote about 30 GB of data in C:\Programme\MERCURY\SESSIONS\MERCURYI (FYI: Mercury/Mail/... contains about 3,3 GB of data. There is a total of two users).

[quote user="khk"]

Additional information:

since the problem occurs Mercury wrote about 30 GB of data in C:\Programme\MERCURY\SESSIONS\MERCURYI (FYI: Mercury/Mail/... contains about 3,3 GB of data. There is a total of two users).

[/quote]

Turn off session logging and delete the logs, you are probably out of disk space.

Thanks so far. Disk space is no problem at all on this computer. Nevertheless I turned off session logging and moved the files to some other part of the HD. But the problem remains.

Additional info: Well, yes, I found the main problem: In the core module config there had been defined a QUEUE folder on a network drive (completely stupid idea, yes...) and this drive had been disconnected. Now I switched to a local (existing) queue folder and everything is running smoothly now.

Now the problem is a bit different: Where are the mails received by the POP3-Client module during the day without existing queue-folder? Are they recoverable?

Now the problem is a bit different: Where are the mails received by the

POP3-Client module during the day without existing queue-folder? Are

they recoverable?

Maybe, depends on how the system responded to the lack of a queue.  Check the SCRATCH and TEMP directories for files.  That's where the mail is stored when received via MercuryD until delivered.

temp is empty and scratch contains only old files...

temp is empty and scratch contains only old files...

 Then the mail that was downloaded is gone.