Oh and I forgot to mention - no there's no real time av on either server

Sorry, found the issue.  When I had spoken with the admins at backscatterer, they said we were being blocked for backscatter, according to their info.  When I checked the configuration on our server and THEIR DATABASE, it looks more like the VRFY command was enabled (which it shouldn't).  I've got the system configured to not backscatter or send VRFY commands.  Thanks for your help and especially your patience.

I have quite a few IP access restrictions in MERCURY.ACL.  At times I'd like to temporarily remove some or all of the "denied" restrictions.  If I were to do a switch of MERCURY.ACL files, how can I get Mercury to re-read/apply the file without restarting it?  Thanks.

 - Vince

There isn't one.

Idiots should not run mail servers.

Read the help.

When you understand the concepts, you will know what to put in all the little boxes.

Thank you Thomas. I tried it with Pegasus as the IMAP client, and it worked immediately. Now I'll have to start tweaking with SSL etc, but the basics work.

 PS: Even SLL and configuring my cellphone was easy.

An entirely new mailstore is indeed in work for Mercury, but it's still some time until it's finished (it requires rewriting a very big portion of the code).

Would it be possible to use Thunderbird to first create the wanted folder structure and then transfer messages folder by folder, or is the structure too complex for that?

/Rolf 

This patch corrects a problem in the MercuryX Scheduling Module released with Mercury v4.72 which would prevent other modules from coming online at startup if the scheduling module was unconfigured. If you do not load the MercuryX module, you do not need to install this patch.

Go here to download:

http://community.pmail.com/files/folders/patches/entry24194.aspx 

It looks as if there was a problem with a .lnk file.  I had set up a link to Mercury's loader.exe in the system Startup folder and it was this .lnk file that was being flagged by HiJackThis.  I deleted the .lnk file and made a new one and all was well.  HiJackThis no longer complains.  What went wrong with the old file, I don't know.

Gordon

It's a very strange setup, but then again maybe that's what you want, I have no way of knowing. Anyway, disable the MercuryX module (it's broken in 4.72 and can disrupt other modules), If you actually want to send something from your very restricted localhost environment you should in Connection control check "Connections from this address range may relay mail through this server".

Does your ISP allow you to connect to an external SMTP server (mail.google.com) on port 25? If not you should probably use the SMTP server they provide for relaying. To get more information on what is happening you can specify a log file for MercuryC, and temporarily switch on session logging in MercuryC as well.

If you plan to run a mail server it actually a good idea to study the manual. 

/Rolf  

Sounds like the MercuryX bug as per this thread http://community.pmail.com/forums/thread/22605.aspx

Disable the MercuryX module.

Thanks, I've contacted tech support at Roadrunner.com and await their answers.

I don't think you may switch, because the APIs used for sending broadcasts by Mercury are provided by the Netware Client and the use of APIs is hardcoded in Mercury. There is no output by the coremodule like "send <user> <subject>".

But may be I missunderstand your environment. I understand you're having a Novell Netware Server with Novell Accountmanagement (which ever) and Mercury configured for use of this accountmanagement. In this case Mercury assumes a Novell Netware Client for full functionality. SEND respective the Novell-APIs know about Netware Users and are capable identifiying a workstation, where the Netware user is logged in.

NET SEND only knows about local users on Windows or users in a Windows DOMAIN/Active Directory. In this case the pre-condition using NET SEND is the same username on Windowsworkstation/-domain than on Netware. But even than there is no support in Mercury for Windows Accountmanagement and in consequence no use of APIs for NET SEND.

Sorry

   Olaf

Great, thanks Rolf.

Sorry everyone.  Get this, the message issuing my license got sent to my spam box!  Argh!

I'm good now.

Thanks,

C.J.

Square brackets are reserved characters in regular expressions, so you need to do something like this to make it work:

If expression headers matches "*X-AC-Weight: [[]####] (Whitelisted) -9999*" Goto "Exit Rules"

See Mercury help for more details about regular expressions.

/Rolf 

Just set up any email client on the host system to connect with IMAP to 127.0.0.1 and see what happens.

From a networking perspective it will make no difference what folder a message being requested by IMAP is in. Can you open the new messages (.CNM files) in the mailbox with for instance Notepad or are the files corrupt?

/Rolf 

Mercury works with any reasonably standards compliant email client, including Outlook and Thunderbird. For most uses the default settings in Mercury are OK. You will need to enter the information that you are prompted for during installation, of course. Pay special attention to getting the local domains settings right.

/Rolf 

You have to ask Google. In Pegasus you may *bounce* the mails with your googleaccount, but don't know, if Google allows relaying.

 so long   Olaf

I solved the problems I was having with Mercury I got Mercury through xampp. I just opened xampp control panel and unchecked the box for service on the Mercury mail area and it cured all my problems so far for getting in the admin area. I just thought everyone would like to know. Thanks for the help.