Pegasus Mail & Mercury

There are at least 3 ways to do this. The simplest solution is probably to create a mailbox called support, and use file based forwarding to deliver copies to joe and fred. Another way is to create an alias for support@acme.com and point it to a general rule set that delivers copies of the mail to joe and fred. The ...

Sorry if this wasn't clear, but all the same I have to insist that IMAP only needs port 143 to work. To use SSL protection for IMAP port 993 must be open as well (and SSL must be enabled in Mercury), but that's not a requirement for IMAP as such. If the device is set to connect only if SSL is available and port 993 is closed the _inbox_.pnm ...

IMAP will only need port 143 to be open to work, but it could be that some antimalware program is monitoring that port and causes lockups. If a sub-folder, for instance the one for sent messages, contains extremely many messages that could perhaps lead to problems, but I don't see any connection to the _inbox_.pnm file unless it ...

_inbox_.pnm is, as you probably know, a text file containing a list of messages in the inbox, that is created and maintained by Mercury. It should be updated automatically in the background when the contents of the inbox changes, so there is no direct reference to it in any logs. What you should look for in the MercuryI logs is any error or ...

Verify that the device is set to show a sufficient number of messages, and don't keep more messages in the mailbox than can be downloaded by the device. /Rolf 

For folders you can use the mbxmaint or mbxmaint_ui utilities that are included with Mercury to find and fix errors (the first one is a command-line tool, the second one has a normal user interface). For the mailbox structure the best is to have Mercury recreate it (if not multi-layered). If just renaming the HIERARCH.PM file didn't do it, ...

Unless it's a complicated folder structure with multiple layers it's probably best to rename the corrupted HIERARCH.PM file to force Mercury to automatically create a new one on the next login. /Rolf 

To activate session logging for MercuryC open the configuration dialog for that module and fill in the full path to the directory where you want log files to be created (for instance C:\MERCURY\Sessions\MercuryC). Then check ''Enable'' and click OK to save changes. Remember to deactivate when you don't need it any more. To get more details in the ...

With some programming experience it should definitely be possible to create a MercuryB module to handle autoreplies and forwarding. There is actually a more recent version of the external web tool package, though. First download the installer: http://downloads.serieguide.se/webtools.zip Install the program in the main Mercury directory (that ...

I missed the part about the IP interface restrictions, sorry about that. It's rarely a good idea for a server to only respond to traffic from the server itself. But did you actually get any response on port 25 on server1.thosforums.com when connecting with Telnet? It just times out when I try it. /Rolf