If there has been connection problems there can be old files left in the queue and scratch directories. Usually it won't make any difference for Mercury, but it can still be a good idea to clean it up.

If this is a home network it shouldn't be too difficult to find a suitable time when there are no jobs in queue to shut down Mercury for a minute and remove junk files.

The scratch directory is used by Mercury for temporary work files and is by default in your main Mercury directory. If you are running a recent version there will be sub-directories for each module - if so keep the sub-directories but remove any files in them.

/Rolf

I have installed Mercury/32 on a dedicated machine on my LAN to act as a mail proxy.
MercuryD collects the mails from distant POP3 server every 5 mn, then I can read them with Imap from the desktop or a portable on the LAN (client=SeaMonkey or OutlookExpress).
For sending mails, the client smtp's directly with distant SMTP server, neither MercuryE nor MercuryC is involved.

The problem: if I compose a large mail (say, 22 MB) and want to save it in the Drafts folder, it may last forever, even never complete.

Most of the time I quit the transfer after 15mn, loose my work, redo it and then the mail is saved in 5 seconds (LAN=Eth 100Mb).

I have read the many entries reporting a 'slow' problem, so I :

• stopped the Avast! antivirus on all machines
• disabled session logging on all modules
• stopped ClamAV
• have no filtering rules

Result: problem stays. All PCs are WinXP Home.
To be complete: it may also take forever to load a big mail from the server, same symtoms-

Ideas, anyone?

This Mercury tool is great, even I could make it run, the online help is awesome and it is what I need.
Just this pesky slowness problem...

JF 

In case you wonder why I'm doing this proxy'ing:

- wife wants to see the same Inbox when sitting in front of desktop OR portable, therefore -> Imap

- FReemail does not offer Imap access for free, just pop3

- wife won't change email address...

Changing wife is not an option. And I want to keep Mercury too. 

IMAP access to Mercury over a 100 Mbit LAN is typically very fast. So you will need to test things systematically until you can find out what it is that slows things down for you.

Transferring messages with big attachments to the server puts the heaviest load on the client as it will have to encode attachments to a transferable format, so I would start at that end. Verify that disks are OK with chkdsk, defragment, make sure you have enough free space on the system volume, check RAM usage and processor load. Make sure no other process is interfering (yes, I noticed that you already tested with stopping your anti-virus program, but there could be other processes that intercept disk access). Try with another well reputed mail client (Thunderbird or Pegasus for instance).

If problems persist you can then move on to checking the network. Restart switches and any other intermediate devices, move cables to other slots, try with other patch cables.

Finally move to the Mercury server and check disks and system resources the same way as on the client machine. Filtering rules should have no effect on IMAP transfers, though, but you should avoid session logging. Make sure you have the most recent version of Mercury. Manually clear queue and scratch directories and restart Mercury.

If you then still have the same problem make a completely new installation of Mercury in another directory and test again in case some program file has been corrupted.

/Rolf

In the account setup of my mail client(s) I had entered as IMAP mail server the computer name in Windows.
- this is the name you enter under 'Computerbeschreibung' in the Properties of your workstation (Arbeitsplatz/Eigenschaften).

Well, don't do that: instead of the Windows hostname, give the IP address of the machine on which Mercury/32 is running

You may loose a bit of flexibility if your mail server changes IP address, but at least now mails are downloaded or saved to the Drafts folder in a blink.

Most DHCP servers like the one that runs on my cheap Dlink router, keep a record of the IP address they attribute to a given MAC address, so it is not really a loss.

JF,
relieved . Wife can stay.

[quote user="Rolf Lindby"]

Manually clear queue and scratch directories and

restart Mercury.

1. I wanted to do that but did not dare: is it actually possible to delete files in the mail queue with Windows Explorer (wouldn't this corrupt the queue)?
2. Where do I find a scratch dir  and what is it for? Can't find this in the help.
   

JF