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.

 

[quote user="Thomas R. Stephenson"]

Use an AND filter with the address/domain of the requester and the Spamhalter header with an action delete (or move to a spam user).  Looks something like this in the riles.mer

If expression headers matches "X-SPAMWALL: SPAM detected!"  LogicalAnd ""

If header "CT" contains "domain.com" Move "@c:\\pmail\\mail\\spamaccount"

but the backup server handles mail for some other domains ... would that not forward ALL incoming mail to the remote server?

 

Hi, two weeks ago I've subscribed to a service that sends an e-mail at

2 a.m.   The default exit / restart also happens to be at 2 a.m.  It

turns out that when exit / restart happens it doesn't wait for

everything to be idle, but instead just does its thing, and anything in

progress will be lost.  I know that since I have POPFile and all the

service e-mails got as far as POPFile, but not into Mercury.  I've now

moved the reload time to 2:15 and they're now progressing all the way

to the client.  But what might be lost at 2:15?

Nothing will be lost, they'll be resent.  The SMTP protocol is designed to handle breaks in communication between the sender and the receiver.   If a SMTP connection is lost in the middle of a transaction, the sender is required by the RFC to requeue the mail to be sent later.  Now if the service does not resend a message  that fails to complete then you have to talk to them about their bug in their service.

I only have logging on as I was trying to find out why certain emails were not being received.

Now that's sorted logging will be turned off.

From David Harris:

It's stored as part of the encoded string in MercuryD.dat. There's
basically no way of getting at it outside the program's UI at this point.

 

aaaaaaaaaahhhhhhhhhhhhhhhh! damn! I've seen that so many times, but have never had to use it.

Many thanks.

[quote user="tomt"]My greeting.mer contains:

220-mail.domain.co.uk Mercury/32 v4.52 ESMTP server ready.
220-Use of this server for unauthorised relaying of mail is forbidden.
220 Unsolicited Commercial E-mail ("spam") is NOT WELCOME HERE.

Is this format wrong ??[/quote]

It isn't the format specified in greeting.txt because you have added response codes and the initial line. Here's a relevant section:

"We recommend the following text as a starting point:

--------- cut here --------------
Use of this server for unauthorised relaying of mail is forbidden.
Unsolicited Commercial E-mail ("spam") is NOT WELCOME HERE.
--------- cut here --------------

MercuryS automatically adds the SMTP response codes and continuation
characters correctly."

Try telnetting into your server to see what response you get.

That said, the client may not be able to handle multi-line responses anyway, even if they are formatted correctly.

 

Now you see the problems you have when you are trying to use a single-user protocol (POP3) to handle multiple users.  If you have an enlightened ISP, when they put the mail into the POP3 mailbox they will also add a special header passing the original SMTP RCPT TO: address the the message.  If so, MercuryD can (and should) be told what the header is and to use this header for delivery instead of the addresses in the RFC 2822 message body.  From the MercuryD help:

 

Checking for special headers in messages

By default, MercuryD goes through the standard headers in incoming mail looking for local addresses: the fields it examines are: "To", "Cc", "BCC" and "Received". MercuryD also records the Message-ID of every message it processes and usually will not attempt to deliver the same message twice.

Unfortunately, not all ISPs use POP3 mailbox schemes that will work with this approach: some use a non-standard header to record the address of the person for whom the message was actually intended - for example, "X-Deliver-To" is one that is seen from time to time. If your ISP uses a non-standard header to record the delivery envelope address, you can tell MercuryD about it using the Headers control: type in the name of the header Mercury should examine for local addresses (so, from our example above, you would type in X-Deliver-To). The field is not case-sensitive (so, X-Deliver-To and X-DELIVER-TO are treated as identical) and you can add the colon separator at the end of the name or not as you wish. If your ISP uses more than one special header to identify the local addressee, you can enter multiple header names in this field, separated by semi-colon characters (";"). You must not type any spaces in this field.

If you check the control labeled "Check only in these headers" then MercuryD will no longer examine the standard To, Cc, Bcc and Received headers for local addresses and will not discard duplicate messages. Use this control only if you are sure that your ISP always adds the header to your mail.

Your ISP will usually be able to tell you if they use a special header to identify the envelope address in your messages.

 

 

I've done some tests with Server 2008 and the upcoming Mercury 4.61 and didn't notice any issues with Loader/Mercury/S/P/E/Imap. Though from experience web site configuration takes some getting used to.

Ok, I got it. I had a misconfiguration of the local domains in the core modul. Now everything works fine. Thank you!