The Mercury service can be installed with the instm32s.exe program, which can be found in the Mercury directory. Once installed with appropriate settings there are several ways to control it in Windows 2008 Server. You can use the Microsoft Management Console (MMC) snap-in for services, you can use traditional command line commands (net start <nameofservice>, net stop <nameofservice>) or the resource kit sc.exe command line utility, and presumably the new PowerShell scripts as well. Google around a bit if you need more info. The newer versions of has controls for it as well.
If you have installed ClamWall you need to make sure you have the lastest ClamAV version (see this post for more details: http://community.pmail.com/forums/thread/22914.aspx).
Furthermore you should make sure you have no real-time antivirus software or similar that could be interfering with Mercury's access to the queue directory.
Any interventions at the file level within Mercury, except policies invoked, is considered dangerous. That said, we manipulate several config-files automatically without problems, but never queue directories - and it has worked without problems for a decade and a half now.
I have since found out that I had a failing switch module (hard fail yesterday - switch engine actually disabled module).
I would have to say that Thomas's post earlier was spot-on, packets were not able to reach their intended SMTP server uninterrupted. I believe that it occurred in messages sent to yahoo.com because that domain / MX had some of the longer connect times due to numerous accounts receiving the same email that was generated on our end.
This was not an easy thing to troubleshoot as we had replaced same module (twice) in the last 45 days or so. One replacement was bad out of the box, by the way.
DynDns receives my mail and forwards it to the mailserver that they have listed in their MX records. I had this set up to go to my registrar, which I also use for my email.
I added my mailserver, mail.gamesoda.com to the top of the list for these mx records. I also changed the smtp port setting to 25. I am now able to receive mail.
I'm still using verizon for the smart host, so i can send mail too.
There isn't enough information to say what could be wrong. From what you write it seems that the message is received by MercuryS but not sent on to the destination. Start by verifying that the local domains section of core configuration is correct (read the Mercury help for that section). Using the word "localhost" here is only likely to confuse you, so avoid that. Then send another test message and check Mercury core log and the log of the delivering module (MercuryE or MercuryC) to get more information, switching on session logging temporarily if necessary.
If it after that still isn't obvious what the problem is please post the contents of the mercury.ini file and relevant parts of the logs here, and we might be able to help you figure it out.
Here's a session log showing a valid SMTP sending process. I've highlighted the connecting string with a valid domain name and the SMTP address strings. When your application can do this it's putting out a valid message.
Connect to 'scruznet.com', timeout 300. 15:04:13 >> 220 scruz.net ESMTP Sendmail 8.8.5/1.34 ready at Sat, 20 Jun 1998 15:04:14 -0700 (PDT)\0D\0A 15:04:13 << HELO thomas.lmms.lmco.com\0D\0A 15:04:13 >> 250 scruz.net Hello stephens.sj.scruznet.com [165.227.102.91], pleased to meet you\0D\0A 15:04:13 << MAIL FROM:<stephens@scruznet.com>\0D\0A 15:04:14 >> 250 <stephens@scruznet.com>... Sender ok\0D\0A 15:04:14 << RCPT TO:<stephens@scruznet.com>\0D\0A 15:04:14 >> 250 <stephens@scruznet.com>... Recipient ok\0D\0A 15:04:14 << DATA\0D\0A 15:04:14 >> 354 Enter mail, end with "." on a line by itself\0D\0A 15:04:14 << From: "Thomas Stephenson" <stephens@scruznet.com>\0D\0A 15:04:14 << To: stephens@scruznet.com\0D\0A 15:04:14 << Date: Sat, 20 Jun 1998 15:04:12 -0700\0D\0A 15:04:14 << MIME-Version: 1.0\0D\0A 15:04:14 << Content-type: text/plain; charset=US-ASCII\0D\0A 15:04:14 << Content-transfer-encoding: 7BIT\0D\0A 15:04:14 << Subject: test\0D\0A 15:04:14 << Priority: normal\0D\0A 15:04:14 << X-mailer: Pegasus Mail for Win32 (v3.01b)\0D\0A 15:04:14 << \0D\0A 15:04:14 << test message body\0D\0A 15:04:14 << \0D\0A 15:04:14 << .\0D\0A 15:04:15 >> 250 PAA08117 Message accepted for delivery\0D\0A 15:04:15 << QUIT\0D\0A 15:04:15 >> 221 scruz.net closing connection\0D\0A
That is completely true and can be implemented easily to POP3 and IMAP4 the issue appears when the client try to use smtp ssl/tls and invoke the STARTTLS command. then the STunnel can not be used but only the mercury ssl/tls native mode with all the the actual constraints.
And you might not want to just start the GUI while the service is running. Use the Interactive Service Detection window and click on "View the message" to open the GUI. Or stop the service prior to opening the GUI manually (desktop icon).
Surely the most efficient answer is to forward the mail to a public folder. Only one copy of the message and everyone can see if it has been replied-to or not? Or they can grab it from there and move it into their own folder to "take ownership".
I think Thomas has pretty much answered everything! The main thing is to make sure that your Internet provider allows incoming access to port 25 on 86.95.162.33. If so computers around the world will be able to send you messages using the domain MX (pointing to mail.3d-printers.eu).