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.

You could try running a "virtual SMTP server" like Loa PowerTools () on your own machine. It looks to applications on the local machine as though it's an SMTP server running on 'localhost' (or 127.0.0.1) but is connected (via Port 443, the secure http port) to a real SMTP server running elsewhere. You can find a discussion of it in connection with Port 25 blocks and ISPs at bit.ly/G46Pm and on a blog at bit.ly/bBjiNw.

 Whoever will need this in the future:

 I suddenly (everything was working fine for a few years) had the same problem running Mercury as service (by the help of NSSM utility), while running it as application with GUI did not reproduce the problem.

Analyzing the activity of the server with the help of Process Monitor utility, I found that it was not able to read the certificate file.

As soon as I assigned read permissions for the SYSTEM account (which is used while running as service) the problem was solved.

ps: thanks for the irreplaceable mail software :)  

Glad you have solved your first query.  However, as you stated, your spf record is not quite right - see

> Does MERCURY 4.62 support IMAP secure authentication?

If you are talking about the MS Outlook secure authentication, no it does not.  Mercury/32 does support SSL/TLS secure connections though.

[quote user="Nikolas"]Is it true that POP3 and IMAP user names and passwords cannot be sent encrypted?[/quote]

Not really, the connection you use to the server can be an SSL/TLS encrypted tunnel so that all traffic, including the user/pass authentication, won't be accessible.  Most modern clients support SSL connections.

[quote user="BleemZ"]
[MercuryS]
Debug : 1
Logfile : C:\server\xampp\MercuryMail\LOGS\MERCURYS\~y-~m-~d.log
Timeout : 30
Relay : 1
Strict_Relay : 0[/quote]

It's not yet fixed if this server is open to the internet - these relay settings allow anyone to relay through your server and will get you on blacklists before the day is out.

Relay : 0,  Strict_Relay : 1  is secure.  (Equivalent to checking the top 2 boxes in MercuryS config | Connection control - Relaying)

I have removed the Interface.  I don't have a local domain as such as I am using this to pull down several POP3 accounts for myself and my wife.  After reading the section in Help it did not make any sense to configure those settings.

Hi! And many thanks! Once again!
So, MercuryC.NLM work as should (~ designed) and problem lies in sender (mail-system)!
Great support! Also, our best to mr. Harris!
More thanks, Alar from Tartu Uni, Estonia.
PS! I got another such a sender and there was "Reply-To: <>". And, yes, it failed autoforwarding.

I found the problem. it was in the mercury.ini, the fixed ip address was not the one i assigned to my mail server

> I looked at the MercuryI log file. It does not have any entry for my attempt to authenticate. It's as if my email client isn't talking to
> the server! How can that be?


If the client is showing a connection attempt and you are can connect to port 143 via telnet then something is setting on port 143.  If there is nothing showing in the Mercury log nor on the console screen then this looks like something else is trapping the calls to port 143.  Are you sure you are not running multiple copies of Mercury?   Is there anti-virus software running?  Anti-virus software could be setting between Mercury and the client trapping calls to port 143.

Is there a link between the record in the Mercury S log and the correspondent record in the Mercury E log?

Only the MAIL FROM and RCPT TO addresses.  There is no unique process number controlling the entire thread except for the Message-ID of the original message and that's not logged.

Edit:  There of course is the capability of the sending client to ask for a delivery receipt and a MercuryE transaction record showing the delivery process.  The read receipts are much more tricky since many system (and users) turn off read receipts.

> I made changes to the SMTP server port (=465) and the SMTP address (=smtp.1and1.com), i now receive the following error message;

This is a good ESMTP host.  I was able to connect to port 25 normally via telnet.

Start | Run telnet smtp.1and1.com 25 returns

220 smtp.perfora.net (mrus2) Welcome to Nemesis ESMTP server
ehlo thomas
250-smtp.perfora.net
250-STARTTLS
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-PIPELINING
250-SIZE 120000000
250 HELP

I says it supports STARTTLS and ESMTP aurthorization

> Connection error during handshake with smtp.1and1.com failed
> Error FF servicing queue job.

I suspect you are still trying to connect to the wrong port.

>  
> The mercury ini file is pasted below;
>  
> #  MERCURY.INI generated by Mercury Setup

> [MercuryC]
> Host : smtp.1and1.com
> Failfile : C:\MERCURY\Mercury\FAILURE.MER
> Poll : 30
> Scratch : C:\MERCURY\scratch
> ReturnLines : 15
> Timeout : 30
> ESMTP : 1
> Server_Port : 465

Use port 25.  This one is saying it uses STARTTLS which uses the standard port 25 or maybe the submission port 587 since it responds to port 587 as well.  In any case try port 25 first.

> SMTP_Username: olawale@artwales.biz
> SMTP_Password:
> POP3_Auth : 0

You have not set authorization the the server is requesting it. You might need to to relay off this server.

> POP3_Host : smtp.1and1.com
> POP3_Port : 465

Use port 25 instead of port 465 unless you know what type of secure connection is required by the host.

> POP3_ConnFlags : 4
> Logfile : C:\MERCURY\Logs\MercuryC\~y-~m-~d.log
> Log_Verbose : 0
> Session_logging : C:\MERCURY\Sessions\MercuryC
> Session_logmode : 0

> [MercuryS]
> Debug : 1
> Logfile : C:\MERCURY\Logs\MercuryS\~y-~m-~d.log
> Timeout : 30
> Relay : 0
> Strict_Relay : 1
> Server_Port : 465

Not sure what you are doing here.  MercuryS must have port 25 open to receive mail from the outside world unless you are receiving from a special gateway or forwarding system on this alternate port.  

In any case, I cannot telnet into either of these ports to the artwales.biz IP address.


> Alt_Server_Port : 587
> Allow_Illegals : 0
> SMTP_Authentication : 0
> Session_logging : C:\MERCURY\Sessions\MercuryS
> Session_logmode : 0
> Compliance_Settings : 0
> Maximum_Failed_Rcpts : 4
> Max_Relay_Attempts : 4
> SSL_Mode : 0
> ST_Blacklisting : 288
> No_VRFY : 0
> SMTP_ConnFlags : 0
> [MercuryP]
> logfile : C:\MERCURY\Logs\MercuryP\~y-~m-~d.log   # Traffic logging file
> Session_logging : C:\MERCURY\Sessions\MercuryP\   # Directory for session log files
> Session_logmode : 0
> Scratch : C:\MERCURY\Scratch\MercuryP
> Timeout : 60
> UIDL_nul_list : 1
> New_UIDs : 1
> No_NUL_passwords : 1

> [Domains]
> artwales: artwales
> artwales: artwales.biz
> artwales: [74.208.138.235]

I figured it out. It was the DNS zone that I had to enter a mail exchange mx regi. thanks for the respond Rolf.

/Andrée

Thanks!!! You are my hero!

The hosts file isn't expected to contain MX information so MercuryE will always query available name servers. However, in this case you could probably use the (not very well documented) domain re-write function in Mercury.

Find the empty Rewrite section towards the end of mercury.ini and add this line:

[Rewrite]
serverB: [192.168.2.34]

This should redirect all mail

for someuser@serverB to someuser@[192.168.2.34]. You will need to restart Mercury for this to take effect.

/Rolf

Well, you could have two accounts but everything that goes to A gets copied to B. That way you have two entirely independent sets of messages.

You could set one (or both) of the clients to leave mail on the server, although you'd need an agreed deletion policy somewhere along the line.

Your best bet might be to simply use IMAP rather than POP3. That way the messages aren't moved off the server onto the client. Unless one user deletes a message from the server, the other user will still see it.

I've lately run several tests aginst MercuryI, and what I can see your report generally match my findings.

Approx. the following is what I've last week reported to David for examination:

• It appears that in some cases newly created threads have to finish before allowing existing ones to continue. (this means the opposite of what you say above)
• CPU rushes, and disk activity is extremely intense. Especially cache-files are not bulk-read.
• MercuryI reads the headers of all UNSEEN messages, returns the headers and body, then adds a X header containing FLAGS. I'm under the impression that this is the reason why some some clients report message headers have been altered, who then stop fetching new messages.
• \RECENT flag always reports 0.

David has responded and is examining these issues. I'll keep you posted when I have something to report.

> 0,256,"6FTWYDEH:7AA9:FOL00012","4D591135:My mailbox","Gelöschte Nachrichten",0,20
>
> According to the above article, the second value should be between 0 and 4 (two relevant bits). And there shouldn't be anything behind
> the name of the folder, so where does the ",0,20" come from? Is this a syntax error I should fix, or have there been additions to the
> HIERARCH.PM format? Maybe those values denote certain special folders in PMAIL or for the IMAP server. (The above is a "Trash"
> folder.)

This is an indication that the folder has been deleted.  Delete the line when Pegasus Mail is not running.