Hi,

  I kept fiddling and it seems that, despite there were no real configuration issues, MercuryC wouldn't work while the end-to-end client worked like a charm from the first unconfigured start. Odd but... it's fine to me for now :)

Thanks for pointing me out that there are actually TWO distinct smtp client daemons in Mercury.

 - Andrea

Greetings,

   I've configured Mercury on a small webserver of mine. I did open the requisite ports 25, 110 and 143. Then I set up a php webmail service (MailBee) making it rely on M32 for mail reception and delivery. When I send a message, the Mercury log reports: 

 [code]T 20080901 171001 48bc2120 EHLO lalista.org
T 20080901 171001 48bc2120 MAIL FROM:<andrea@lalista.org>
T 20080901 171001 48bc2120 RCPT TO:<resle77@hotmail.com>
T 20080901 171001 48bc2120 DATA - 14 lines, 448 bytes.
T 20080901 171001 48bc2120 QUIT
T 20080901 171001 48bc2120 Connection closed with 127.0.0.1, 0 sec. elapsed.[/code]

However, the mail is never received. What else should I check? In case you're not noticing... I am a total newbie to mail services, smtp, pop etc.

Thanks in advance,

   andrea

There could be several things that need to be checked. The quoted MercuryS log shows that MailBee is sending a lot of HTML trash in the SMTP MAIL FROM and RCPT TO, so you will first have to make sure that MailBee behaves correctly. The next step would be to check the log from the delivery module that you use (MercuryE or MercuryC) to find out what's happening there.

/Rolf 

Also, you need to URGENTLY check the settings in MercuryS, and make sure at least the top two relaying controls are checked.

If your server is accepting the example above, it will be accepting everything from any spammer that finds your open port 25.