If you run Mercury and Outlook on the same computer localhost (or 127.0.0.1) can be entered as incoming and outgoing server in Outlook. The Internet name for the system can not be localhost. If you have a domain of your own it could be for instance mail.mydomain.com, or if not, it should be the hostname of your computer. You can leave Identify myself as in MercuryE configuration empty (it should not be "admin").

If you have a domain and Mercury is assigned to handle mail for that domain you can create your own mailboxes in Mercury. Then your email address will be in the form mymailbox@mydomain.com. If not, use an email mailbox set up by your Internet provider, and download to Mercury with the MercuryD POP3 client.

Filling in Local domains in Core configuration is critical to getting the system working correctly. Please read that section of Mercury help carefully.

If you are connecting to the Internet from a home subscriber connection your Internet provider often blocks certain mail services. You may need to use the MercuryC relay client rather than MercuryE to deliver mail if port 25 is blocked. There is more information about this in Mercury help.

/Rolf 

Did anyone find a solution to this problem?

 I recently installed all new computers in a small office (5 machines). All new (pre-loaded) software on each. I moved the Mercury

Mail over to the new server computer and it seems to be working fine but I have several machines that will not display the 

subscribed folders consistently. I have seen this in the past and have not found a good solution. What is going on or where do I look?

 We are using Outlook 2007 but I have also seen this issue on Outlook Express and Thunderbird. I am running Mercury Mail v4.62.

Any help would be appreciated.

Curt

That's a pretty good thought dilbert. You were right - the IIS SMTP was running. I turned it off since I haven't been using it anyway. Hopefully that fixes things. THANKS!

Thanks a lot
 

Thanks to everyone for their help.  Setting my old Win2K machine in my basement as my own ISP has been a fun and challenging experience.  I'm learning a lot.

For the record: If you are on a dynamic IP it is best to use MercuryC and use someone else's SMTP server since most dynamic IP's are blocked to prevent potential spam.  

Thanks Rolf,

Have picked that up too. This is a very helpful tool and your support has been fantastic, I thank you for all your contributions and hopefully you'll not have to hear from me again anytime soon!

 Regards

Craig

Well, all seems to be quieting down on their Mercury. I think they will be dealing with spam rejections from other servers for a day or two, but they can handle that. I do appreciate all your help. If it chokes again, I will be back!

Mercury currently has no filter rules to move a message into a named user folder.  It can only be moved to the mailbox (new mail folder).  This function is on many wishlists but is not expected in the next version being prepared for release soon.

An alternative is to create a specific user mailbox just to handle these messages.

Your question is too general to work with.  Get a copy of Mercury/32 v4.52 from http://www.pmail.com/downloads and install is as an update over v4.01 that comes with XAMPP and then read over the manual for setup process.  It's pretty straight forward but it's not trival and it depends a lot on the specifics of your installation.  When you get done doing this then come back with specific questions about what you are trying to do and can't get to work.  You can also go to http://kbase.pmail.gen.nz/mercury32.cfm and get a lot of info on the setup as well.  You can probably search on XAMPP in this forum as well to get a lot of help since there XAMPP setup questions come in over and over.  ;-)

If you are working in a Novell environment and the pmxf.ini file hasn't been automatically created, try creating it manually (see Thomas' post of 2008-06-17 for details).

/Rolf

You don't say which version you are now running, but make sure you are using v4.52 or apply patches to v4.01 to avoid a security issue.  Details are here or on .

Do you mean that you want all mail to be copied to another account, which can then be polled? If so, use the Configuration>Filtering Rules>Edit Global Rules and setup a rule to copy all incoming mail using the 'Always triggers' rule. Set it up to copy all incoming mail to an account of your choice.

First thing i though of was port 25 blocking.  ;-) Make sure that McAfee is not scanning the mail folders and Mercury/32 directories since it will cause problems.  You will lose whole folders if McAfee finds a virus in a folder.  McAfee is not as bad as some A-V software but it still can cause mail delivery problems.   You can run the Clamwall daemon on Mercury/32 and have clamd process your email type viruses.

The .QDF files turn up in the SMTPMAIL directory on my Netware 4 server which has been there since 1996 when I first installed mercury.nlm .  I just continued to use it when I changed to Mercury32.  The files on my Netware server are not virus scanned.  I have scanners working on my Windows 2000 server and my workstations.  I guess the scanner on the Windows server could be operating when Mercury32 accesses the Netware directory.  I think I have just reconfigured the scanner to skip the queue directory.  We shall see.

 Thanks

Rights management (and failing to plan for such) catches many, myself included. [:P]

[quote user="Reece"]The connection to the Mercury server from the main (relay) server is also SSL, so that all outgoing mail is over an SSL connection in the first instance. If the receiving server doesn't accept SSL then I want to send it via the relay server, not Mercury.[/quote]

The only way to guarantee a SSL/TLS connection from your server is to send everything through a suitable relay server.  Although, as Thomas says, what you gain by this strategy is unclear.

No way to automate the entire process.

Now I copy all mailbox for user in thunderbird and upload the folders manually in a temp IMAP account. After I move these folder in teh proper user dir. 

Well I finally got it to work! [:D]

The mention of environment variables got me thinking, so I changed the service definition so that Mercury would run under the account I used to install (and generate the SSL certs) and it worked like a charm.  Apparently Mercury relates the SSL cert with the username that created it....and that's probably why I was getting the -3 cryptlib error when I tried to run Mercury under a different account. 

Glad you got your solution, and thanks for posting it to complete the thread for anyone else in a similar situation. [Y]

Hi Thomas,

Thanks for all your help. I have found the problem. The IP address of the mail server had been changed, so I was happily looking at a mailserver that was no longer being used. When I trace on the actual url for the mail server I found that it ended up at a different IP address. Changed my IP, Username and password on the Mercury /32 server and mail came flooding in.

 Thanks again for all you help it is appreciated.