If you have a mercury.lic file in the Mercury directory it should just be moved to the new location.

/Rolf

[quote user="gears"]i d abit of codeing, if its not to hard i could write one up, know where i might get a thing todo this with?[/quote]

If you are going to write a daemon to sort out every problem with mail clients that connect to your mail server, I think you've started an impossible task.  Far better to correct this mis-configured client to do what is wanted.

[quote user="cypherinfo"]

Hello, this is my first post here :-)

I run a website localhost with XAMPP 1.7.1 and Joomla. Mercurymail 4.6. I do not wanna use my ISP for SMTP I'll use MercuryMail.[/quote]

That means you are using MercuryE and not MercuryC for outgoing mail

[quote]I need to use the SMTP host (I need to enter it in a config file; what I have to write there?) of my mail server in another application.

Where I may find it in the settings? After having read the post in the forum I guess it may be my IP. Am I right?[/quote]

Is the application expecting a name or an IP address?  If it is running on the same machine, use localhost or 127.0.0.1, otherwise use the appropriate name or address.

[quote]What if I want to set a custom SMTP host name?[/quote]

I think that's a machine/network configuration issue.  Not Mercury

For Pegasus/Mercury setup this should be a good starting point:

Usernames in Mercury/32 is always just a simple name like jdoe. If the server handles multiple domains and you need to specifically connect it with one of them you will need to create aliases as well.

/Rolf 

I am interested in retrieving older manuals from Pegasus mail,

particularly from the 90s. Via Google, I was only able retrieve newer

manuals. Can somebody help me?

Not sure if these should be made available since in the '90's David was selling these as a part of the support contract.  You might want to contact him directly for these manuals though. .

Problem solved ....

somehow a wrong pconfig.

kai atle

Thanks, Rolf, that fixed it.

 Added the glue headers and blank line, renamed to .101   

Shortly after dropping into the QUEUE folder, Mercury picked it up and created the .QDF/.QCF pair, then it went.

Chris

So you want to use separate sender information in the email client for each user in your local network, but any message sent to an external recipient should have that information replaced with a common sender address? Sender information appear in the SMTP envelope of the message as well as in various message headers (From, Sender, Reply-To etc). To change it in outgoing messages you would need a special daemon, there are no standard tools for it. There is a Daemon Developer Kit available in the Downloads section, but some programming skills will be required.

/Rolf

When running as a service you will most likely need to enter the full path to the killfile (in Configuration / MercuryS SMTP Server / General) before clicking Edit.

You can probably find a lot of information about the anti-spam tools in the PDF manuals that are included with Mercury, Graywall and SpamHalter.

/Rolf

I have made this work in the past, but can't recall the specifics, sorry.

I also recall failing to make it work, more recently.

I usually just rename the *.qdf to *.101 and add the "glue headers" at the top

[quote]$ from@address

T recip@address

<blank line>

<existing message body>[/quote]

Then drop it back in the queue and it gets reprocessed as a new message.

edit: this also can be done to *.cnm files from a mailbox (for spam fp's etc)

[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