The reason is sounds technical is probably that it is rather technical... ;)

It's perhaps best to take it step by step.

Transferring email on the Internet requires port 25. So the first thing to do is to make sure that the device you use to connect to the Internet (DSL modem, router or whatever) has port 25 open, and that any incoming traffic on port 25 is redirected from there to port 25 on the server running Mercury. Make sure there is no firewall program on the Mercury server that blocks port 25.

To send an email you set the SMTP server in your email program to the IP address of the Mercury server. If you run the email client on the same computer as Mercury you should set it to localhost or 127.0.0.1 (which is the same thing). Your email is then received by the SMTP server module in Mercury, and sent to non-local recipients via the SMTP client module (either MercuryE or MercuryC).

To receive an email from someone via the Internet you need to make the public IP address for the mail server handling your domain known to the world. To do this you add a MX record to the DNS information for your domain, containing the hostname of the server. This could be mail.myownserver.info. You will then need an additional A record that gives the IP address for that hostname (which you have, IP is 76.125.92.139).

The MX records for myownserver.info now point to mail6.zoneedit.com and mail7.zoneedit.com, which presumably is not what you want, so you need to change that.

I'm not able to connect to port 25 on 76.125.92.139 at present, so that's another thing you need to check on.

/Rolf
 

Now I want to restore the *.TMP files into the SCRATCH folder because

there are also some legitimate mails between the garbage mails. But

Mercury does not care about the *.TMP files and they are still in the

SCRATCH folder. Restarting Mercury did not help. I tried it also only

with just a few mails - no change. Any suggestions?

I assume that you are receiving the mail via MercuryD and these temp files in the SCRATCH directory were created by the program when the mail was downloaded via MercuryD.  This is not always true since there can be other TMP files in the SCRATCH directory.  I also assume that these are RFC 2822 message files.  If so then you can convert them to 101 files and put them into the queue by adding the following lines to the top of the good messages and save them to the queue.

The "FOR" designation in trace fields records the recipients for which an SMTP mailer accepted responsibility.  It's rarely used, often not provided, is optional according to spec, and is in any case only permitted to hold one forward-path (multiple forward-paths long deprecated for security reasons).  The FOR clause doesn't record the mailbox to which the mail was delivered - that will be handled by a Mail Delivery Agent and isn't the responsibility of the MTA since it has no function to SMTP mail delivery (Mercury uses a different X-line for this).

Cheers,

Sabahattin

[quote user="Thierry"]

Hello,I've installed and configured Mercury.But I cannot send Emails from local addresses such as ict@sfar.local to titi@yahoo.com for estence. What could be the problem with MercuryC?

Evry thing seems to be Ok but I'm getting the following error: 30 Dec 08 09:17, Servicing job MO000006... 550-Verification failed for <ict></ict>

Can anybody help me pls?

Thanks.@sfar.local>

The domain sfar.local is invalid and the receiving system is rejecting for that reason. Change the domain of the sender to a real domain and this will work.

[/quote]

[quote user="herud"]

Hallo,

I have installed Mercury/32 Version 4.52 with the modules SMTP Server, SMTP Relay Client and POP3 Client under Windows Vista Premium Home, SP 1. Generally it works fine.

But every time I go on the option CONFIGURATION -> MANAGE LOCAL USERS mercury crashes.

I have tried to start mercury with the Windows-Options "Run programm with administration rights" or in the compatibility mode for "XP" but the result is always the same crash. I have run mercury under the administrator login, no changes.

I suspect there is a problem with either your setting on the mailbox directory in Configuration | Mercury core "Local mailbox directory path" or the rights to that directory.  This should be something like c:\mercury\mail\~n   and Mercury/32 needs all rights to that directory path.

In the event log under WINDOWS-PROTOCOLS -> APPLICATIONS there ist the following entry (in german):

"Fehlerhafte Anwendung mercury.exe, Version 4.5.2.0, Zeitstempel 0x00000000, fehlerhaftes Modul mercury.exe, Version 4.5.2.0, Zeitstempel 0x00000000, Ausnahmecode 0xc0000005, Fehleroffset 0x00057bb2, Prozess-ID 0x17d4, Anwendungsstartzeit 01c96a559ee4a9c0"

Translation:

"incorrect application mercury.exe, version 4.5.2.0, time stamp 0x00000000, incorrect module mercury.exe, verion 4.5.2.0, timp stamp 0x00000000, exception code 0xc0000005, error offset 0x00057bb2, process-id 0x17d4, application start time 01c96a559ee4a9c0"

Has anybody an idea for eliminating this error or for a work-around ?

Great thanks in advance and a Happy New Year

Jochen from Würzburg in Germany

Thomas,

What I failed to do was exit Pegasus and restart it on my computer after making the change in NConfig. Duh!

Your suggestion fixed my problem.

Thank you so very much.

Happy New Year to you and yours,

eRob

ok, as per your instructions...I switched to MercuryC and set it up using the same information I would use if I was setting up Outlook express to send and recieve mail from my host.

For comcast, I had to go to their site and check the help files on how to set up outlook express and they gave mail.comcast.net on port 587.  That didn't work, so I tried smtp.comcast.net on port 587 and ... IT WORKS!!!

 Thank you so very much and I hope my response as to the exact fix will help others.

Good point, google for "base64 decode" to find a tool for it (there are plenty of them on the web).

/Rolf
 

Thanks but you are right that this is not in the SMTP command.

It's working now

[quote]

~$ telnet mail.tals.com.au 25
Trying 59.167.194.170...
Connected to mail.tals.com.au.
Escape character is '^]'.
220 tals.com.au ESMTP server ready.
ehlo dln
250-tals.com.au Hello dln; ESMTPs are:
250-TIME
250-SIZE 0
250-AUTH CRAM-MD5 LOGIN
250-AUTH=LOGIN
250-STARTTLS
250 HELP
quit
221 tals.com.au Service closing channel.
Connection closed by foreign host.
[/quote]

and your DNS looks OK.

[quote]

~$ dig tals.com.au -t mx

; <<>> DiG 9.5.0-P2 <<>> tals.com.au -t mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52753
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;tals.com.au.                   IN      MX

;; ANSWER SECTION:
tals.com.au.            3600    IN      MX      10 mail.tals.com.au.

;; AUTHORITY SECTION:
tals.com.au.            3380    IN      NS      ns80.mdwebhosting.com.au.
tals.com.au.            3380    IN      NS      game-server.tals.com.au.

;; ADDITIONAL SECTION:
mail.tals.com.au.       3600    IN      A       59.167.194.170

;; Query time: 113 msec
[/quote]

What do the MercS logs say?

I have now got to the bottom of this.  You confirming that it was not a problem at my end has forced me to look further.

In fact the messages I thought were all the same were in fact sent at slightly different times.  They were generated in a frenzy last night at three of my clients as error messages when certain machines failed to connect to my FTP server.  They were sent via Demon who was the ISP for three of my clients.

For some reason, these messages were not delivered immediately but rather, very slowly throught the day.  A few straglers are still coming in now.

I have now set up the client machines to post direct to my server and not via their ISP.

Thanks again.

My Distributing POP3 Client has been set to download mail for three accounts on my ISP's server.  Two are working correctly, but one results in the message "File creation error. - Network Error; delivering anyway." when polling takes place.  There is mail for that account, but it is being left on my ISP's server.

 Any ideas what may be causing this and what the solution might be?

Prior to this, all accounts have functioned correctly for many months.

 Thank you

GordonM

 Further Comment

Further to the above, I have now set up a normal POP3 account on Outlook Express for the problem account.  This manages to pull down all of the mail except, possibly, one message.  I receive an error message, saying:

 Message number 1 could not be retrieved. Account: 'pop.broadband.rogers.com', Server: 'pop.broadband.rogers.com', Protocol: POP3, Server Response: '-ERR problem retrieving message.', Port: 110, Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800420CD

Maybe one of the messages on the server has been corrupted.

Problem Solved

It seems that there was a problem with one message on the server.  I downloaded all of the messages for the problem account, without leaving messages on the server.  I then received the error message noted above.  I then went into the account using my ISP's webmail app and one message was left behind.  I delted this.  I then sent a test message to the account and Mercury was able to download it.  I have no idea what was wrong with the message that I had to delete, as I had no means of analyzing it through webmail.

Thanks for the help guys

 Much Appreciated

Well - I had problems with other mail servers on this machine, so tested them (and Mercury) on a virtual pc - all worked immediately. 

Obviously something is going on on that machine.  I shall investigate and post my findings! 

Thanks for your help - sorry if I was vague in places but I was stumped!

thank you very much for all the help & guidance.

regards,

bun

Hello Peter

you can use the MercuryH PH-Server-Module . With this module you can "share" a normal Pegasus-Mail-Adressbook for Users which has a PH-client.

Info from the Mercury-Help-File:

>MercuryH PH Directory Server
>
>MercuryH is a directory services module - it accepts requests for addressbook lookups from other systems and returns lists of possible matches. The protocol used by MercuryH is called the PH >protocol, also sometimes known as the QI/CSO protocol: it is widely-used on the Internet by mail clients such as Pegasus Mail and Qualcomm's Eudora. At the time this help file was written, an >Internet standard was in the late stages of being formalised for the PH protocol - MercuryH implements that standard.
>
>In order to fulfil queries, MercuryH uses a Pegasus Mail addressbook file, mapping the fields in the addressbook file onto the standard fields defined by the PH protocol. Any Pegasus Mail >addressbook can be used by MercuryH, and you can use the import/export tools provided with Pegasus Mail to create and maintain addressbooks for MercuryH.
>

Hope this helps

Hans 

[quote user="mikerocosm"]

Long time user, first time poster . . .

I've just converted my home Mercury server (gathers several POP3 accounts for myself and my wife, distributes them back to us through Pegasus) to deliver mail using IMAP instead of POP3. I've got it all working just fine, locally and from various remote installations, but IMAP clients will not connect to the Mercury server as long as the Pegasus client is running on the server machine (which is also my trusty does-everything home computer). Simplest solution is to just close Pegasus on the server after I've run my traps each morning, I suppose, but I never had to do that when using POP3, and Lord knows, I don't want to have to change my behavior now.

So, is there a way to configure Pegasus locally on the Mercury server so that it doesn't interfere with IMAP access from remote Pegasus clients?

Nope, the lock file is in place to ensure that a user and Mercury/32 are not both accessing the same folders at the same time.  That would be a sure way to lose data and maybe the entire folder.  This is not a problem with POP3 since it is only downloading the mail as separate files from the new mail directory.  Even when these files are downloaded and deleted via POP3 the only thing you have to do in WinPMail to clear it up is to close and reopen the new mail folder.

Inquiring minds want to know . . .

Best regards,

Mike

Open relays are quickly discovered and misused, so it's important to get the relaying settings right in Mercury. Once that is done you have done what you can, tracking down spammers and making them rethink their lives is not a realistic undertaking.

There is a risk your IP address has been blacklisted if you have been relaying a lot of junk, so you may want to check that (for instance here: http://www.mxtoolbox.com/blacklists.aspx)

Haven't been using SSL with Outlook so I can't help there. Maybe someone else knows?

/Rolf 

Hi Thomas

Got some files back but not all? many are ones I deleted some time back.  Pegasus is now working, I must move on, so much time
wasted.

Many thanks for your help and patience.

Happy Christmas to you and yours Thomas