[quote user="Mishu"]Why couldn't Mercury start as a service? I can start it as an application.[/quote]

You have installed the license correctly, I presume?

Have a look at this thread and see if it can help:

http://community.pmail.com/forums/thread/22780.aspx

/Rolf

It's basically the same procedure again. Start by checking the folder with mbxmaint. If it reports an error try repairing it. If this should fail, use the other tool I linked to extract the messages, and try creating the folder again from scratch.

/Rolf 

MercuryE will continue to try to send a message until the maximum number of retries specified in Core configuration / Mail queue has been reached. 10060 appears to be a Windows socket error indicating a timeout. Try increasing the MercuryE timeout value considerably (to for instance 300 secs), and make sure your Internet provider hasn't started blocking outgoing SMTP traffic.

/Rolf

If the number of .QCF / .QDF files isn't so big you can just open them in Notepad (or any word processor program) to find the recipient address. If there are many files you could probably use the built-in search in Windows to search for the address in the files.

Email addresses are not case sensitive, so web.ES is an acceptable form (assuming that the domain is called web.es, of course). webES, on the other hand, is erroneous.

If these are proper messages and not spam (that frequently contain strange addresses) it could be that when replying to messages some mail clients misinterpret the sender information in the original message and create a malformed To header.

/Rolf 

Thank you for your reply.

In march I could use the gmail smtp server having a gmail account.

But I got the information that gmail has changed it's policy in may and that this isn't possible anymore.

 As far as I understand it, this means that a person using his e-mail client and on travel connects to some hotspot doesn't have the possibility anymore to reply his mails or sent new ones.

What does the interface show?

Any clues in the log files?

Start by checking Mercury logs to see where the problem occurs. Try to follow the message from when it's received by MercuryS to when it's accepted by the relay server, and note any errors that appear. Post log excerpts here if you want us to help you figure it out.

/Rolf 

Okay, thanks Thomas.

I run no antivirus software, so that is not the issue here.

All seems to be working okay now.

I am set to receive the notifications, so will be able to monitor.

Thanks

Ellie 

Some machines talking to MercuryS can't establish proper SSL session. Reason logged is: 'Invalid compression algorithm information'

16:49:45.234: Connection from 145.64.132.99, Wed Sep 15 16:49:45 2010<lf>
16:49:45.250: << 220 XXXXXXXXXXXXXXXX ESMTP server ready.<cr><lf>
16:49:45.296: >> EHLO epo.nl<cr><lf>
16:49:45.312: << 250-XXXXXXXXXXXXXX Hello epo.nl; ESMTPs are:<cr><lf>250-TIME<cr><lf>
16:49:45.328: << 250-SIZE 0<cr><lf>
16:49:45.343: << 250-AUTH CRAM-MD5<cr><lf>
16:49:45.359: << 250-STARTTLS<cr><lf>
16:49:45.375: << 250 HELP<cr><lf>
16:49:45.468: >> STARTTLS<cr><lf>
16:49:45.484: << 220 OK, begin SSL/TLS negotiation now.<cr><lf>
16:49:45.546: 22: Error -32 activating SSL session (locus 0, type 0, code 0, 'Invalid compression algorithm information')
16:49:45.562: --- Connection closed normally at Wed Sep 15 16:49:45 2010. ---
16:49:45.578:

Another mailer can't establish SSL  session, that's 194.11.253.100/SPFDEFRA01.capgemini.com

I suspect that my auto-signed certificate is the reason.

Question: how can I write a FILTERING RULE that prevent offering STARTTLS to some mailers ?

(some H rule based on the EHLO line prolly?).

Thanks,

JF

Hi all 

I find the problem, there was something wrong within the scratch directory (I had over 500 files .tmp)

Once I deleted the contents of the directory the global rules began to operate even without the need to reset mercury

thanks for you support

Please send me a private message here on the forum with a working email address - the messages we send to you about this are refused.

/Rolf

Mercury wouldn't be able to do what you ask, without having really advanced deterministic behavior about what a client could be doing as next command.

 If a mail server was to store an e-mail with attachment of 5MB without consuming the server RAM, it would need an overall cache engine to query first and disk data secondly. In the background Windows does this on local files, but serverwide, meaning over network lans, and other OSs, client side caching is dangerous. This is the reason why many have large issues with file based databases, and the bad solution called opportunistic locking. 

Thanks for the quick reply.

The current config is netware 5.1 running mercury on windows platform, with pegasus client.

I had a feeling I would have to do a fresh install.  I am aware of all the manual stuff that I have to do for the full windows, I was not aware that there is AD integration which might help alot.

since I have to do a fresh install do you know how to move the mercury license

thanks for all the great info

thanks I'll give it a try

> It was sent from a php script though my website. But its not setup to keep sending out emails, but its sending though my gmail. Which
> mercury is using for outgoing. Here's whats it doing...

This bounce message doe not say why Mercury was getting the bounce message.  One of the major problem here is you are sending mail out to the internet using the domain localhost and that is not allowed.  This is especially true for the postmaster address which is taken from the domain name you entered in Configuration | Mercury core | Internet name for this system. 

Other than that we need to see exactly what you are sending out though the script.  Turn on session logging in MercuryS to see what is coming in and in MercuryC to see what is going out via the GMail relay host.

>  
> Delivery to the following recipient failed permanently:    
> Admin@localhost
> Technical details of permanent failure: The recipient
> server did not accept our requests to connect. Learn more at
> http://mail.google.com/support/bin/answer.py?answer=7720 [localhost
> (1): Connection timed out]
>
> ----- Original message -----
> Received: by 10.114.92.3 with SMTP id p3mr5560597wab.77.1283188451407;       
> Mon, 30 Aug 2010 10:14:11 -0700 (PDT)
> Return-Path: <hatchiechris@gmail.com>
> Received: from localhost (c-71-227-159-43.hsd1.wa.comcast.net [71.227.159.43])  
> by mx.google.com with ESMTPS id x9sm14552538waj.15.2010.08.30.10.14.09
> (version=TLSv1/SSLv3 cipher=RC4-MD5);        Mon, 30 Aug 2010 10:14:10 -0700 (PDT)
> Received: from Spooler by localhost (Mercury/32 v4.72) ID MO00008F;  30 Aug 2010 10:14:03 -0700
> Received: from spooler by localhost (Mercury/32 v4.72); 30 Aug 2010 10:13:52 0700
> To: Electronic Postmaster <Admin@localhost>
> From: Electronic Postmaster <hatchiechris@gmail.com>
> Date: Mon, 30 Aug 2010 10:13:41 -0700
> Subj
> User <Tatalena@opprimovox.net> not known at this site.

BTW, the message was painful to read, I had to unwrap the garbage so it was legible.  

Is this another XAMPP setup??

That's certainly unambiguous. Thank you for your help.

Regards,

Bruce

The RFC max length for a single line is 1000 characters including CR-LF, and recommended line length is max 80 characters. Check formatting of the message to see if this is the reason for your problems.

/Rolf

Thank you.

Ah, well, it was worth a try.

The reason I am trying to do this is because we use MessageLabs for two of our three domains, and as I mentioned here  we are having problems with undesirable mail (spam-bots) using the lowest MX record to deliver mail directly to our IP address.

I know I can remove the last MX record, but I wanted to avoid doing this if possible.