<p>Please note Thomas' recommendation to change the password to something that hasn't been published on the Internet! Otherwise the server will soon be relaying lots of spam and become blacklisted.</p><p>/Rolf </p>

<p>Good Morning at everyone,</p><p> I've a trouble with mercury mail transport auth login. I use a smtp client mounted on a plc to send an email to the mercury server inside the business network. I have a secondary server in the net where the MercuryC module send the received email with STARTTLS method. </p><p>I can send email ouside the business network, via plc->MercuryS->MercuryC->Server with tls->Google Mail if I don't set the AUTH LOGIN procedure (authentication with password without ssl). If I send via plc an AUTH LOGIN request in smtp, the server send back an error of authentication after I send user and password in base64 encription.</p><p>I can sniff the comunication between plc and the mercury server and between mercury server and the secondary server with an application called wireshark, so I can follow the entire message exchange procedure between client and servers. The password and the user that I translate in base64 is exactly (upper/lower case corresponds) what I set in <span style="font-style: italic;">manage local users </span>in Mercury. </p><p> <img src="file:///C:/Users/fabiob/Pictures/Plc_SMTP_communication.gif" alt=""></p><p>The same procedure I use for another smtp server called winwebmail and it is accepted without any problem. The problem of winwebmail is that it doesn't support STARTTLS relaying. </p><p>So, have you an idea of what is the problem?</p><p>Thank you in advance. </p>

<P>I don't see the picture you included.</P> <P>Have you tried putting on session logging on the Mercury server where you are having problems - presumably the first, receiving SMTP?</P> <P>Post the text of the session log here, minus any confidential stuff.</P>

<blockquote>I can send email outside the business network, via plc->MercuryS->MercuryC->Server with tls->Google Mail if I don't set the AUTH LOGIN procedure (authentication with password without ssl). If I send via plc an AUTH LOGIN request in smtp, the server send back an error of authentication after I send user and password in base64 encription.</blockquote>Setup MercuryC to do session logging and provide us with the session log showing both the good and the bad connection for analysis.  FWIW, this might be one of the many servers that advertise AUTH CRAM-MD5 and then have not configured the system to use it.  You might want to turn this off in MercuryC before testing.

<p>Here the bad session logging:</p><p>09:52:59.013: Connection from 192.168.0.13, Wed Mar 09 09:52:59 2011<lf> 09:52:59.013: << 220 192.168.0.29 ESMTP server ready.<cr><lf> 09:53:00.153: >> EHLO [192.168.0.13]<cr><lf> 09:53:00.169: << 250-192.168.0.29 Hello [192.168.0.13]; ESMTPs are:<cr><lf>250-TIME<cr><lf> 09:53:00.169: << 250-SIZE 0<cr><lf> 09:53:00.169: << 250-8BITMIME<cr><lf> 09:53:00.169: << 250 HELP<cr><lf> 09:53:00.309: >> AUTH LOGIN<cr><lf> 09:53:00.309: << 334 VXNlcm5hbWU6<cr><lf> 09:53:00.465: >> ZmFiaW8=<cr><lf> 09:53:00.465: << 334 UGFzc3dvcmQ6<cr><lf> 09:53:00.606: >> ZmFiaW8=<cr><lf> 09:53:00.606: << 501 Authentication failed - bad user or password.<cr><lf> 09:53:00.715: >> QUIT<cr><lf> 09:53:00.715: << 221 192.168.0.29 Service closing channel.<cr><lf> 09:53:00.715: --- Connection closed normally at Wed Mar 09 09:53:00 2011. --- 09:53:00.715:  </p><p>  The good session logging without password and user:</p><p>09:19:21.313: Connection from 192.168.0.13, Wed Mar 09 09:19:21 2011<lf> 09:19:21.313: << 220 192.168.0.29 ESMTP server ready.<cr><lf> 09:19:21.454: >> EHLO [192.168.0.13]<cr><lf> 09:19:21.454: << 250-192.168.0.29 Hello [192.168.0.13]; ESMTPs are:<cr><lf>250-TIME<cr><lf> 09:19:21.454: << 250-SIZE 0<cr><lf> 09:19:21.454: << 250-8BITMIME<cr><lf> 09:19:21.454: << 250 HELP<cr><lf> 09:19:21.656: >> MAIL FROM:<fabio.bonelli@ascontecnologic.com><cr><lf> 09:19:21.656: << 250 Sender OK - send RCPTs.<cr><lf> 09:19:21.797: >> RCPT TO:<fabio.bonelli@gmail.com><cr><lf> 09:19:21.812: << 250 Recipient OK - send RCPT or DATA.<cr><lf> 09:19:21.000: >> DATA<cr><lf> 09:19:21.015: << 354 OK, send data, end with CRLF.CRLF<cr><lf> 09:19:22.156: >> Date: 16 Jun 2009 14:31<cr><lf> 09:19:22.202: >> From: fabio.bonelli@ascontecnologic.com<cr><lf> 09:19:22.249: >> To: fabio.bonelli@gmail.com<cr><lf> 09:19:22.312: >> Subject: From local mail server<cr><lf> 09:19:22.405: >> <cr><lf> 09:19:22.405: >> Test concluso con successo.<cr><lf> 09:19:22.499: >> <cr><lf> 09:19:22.514: >> .<cr><lf> 09:19:22.514: << 250 Data received OK.<cr><lf> 09:19:22.655: >> QUIT<cr><lf> 09:19:22.655: << 221 192.168.0.29 Service closing channel.<cr><lf> 09:19:22.670: --- Connection closed normally at Wed Mar 09 09:19:22 2011. --- 09:19:22.670:</p><p> The good smtp messages with password with WinWebMail Server:</p><p>     836 169.193601  192.168.0.29          192.168.0.13          SMTP     S: 220 ESMTP on WinWebMail [3.8.0.2] ready.  http://www.winwebmail.net     839 169.340645  192.168.0.13          192.168.0.29          SMTP     C: EHLO [192.168.0.13]     840 169.340647  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: EHLO [192.168.0.13]     842 169.340999  192.168.0.29          192.168.0.13          SMTP     S: 250-SIZE     845 169.351730  192.168.0.29          192.168.0.13          SMTP     S: 250 AUTH LOGIN     848 169.491951  192.168.0.13          192.168.0.29          SMTP     C: AUTH LOGIN     849 169.491952  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: AUTH LOGIN     851 169.492999  192.168.0.29          192.168.0.13          SMTP     S: 334 VXNlcm5hbWU6     854 169.641498  192.168.0.13          192.168.0.29          SMTP     C: ZmFiaW8=     855 169.641500  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: ZmFiaW8=     857 169.642013  192.168.0.29          192.168.0.13          SMTP     S: 334 UGFzc3dvcmQ6     860 169.791424  192.168.0.13          192.168.0.29          SMTP     C: ZmFiaW8=     861 169.791425  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: ZmFiaW8=     863 169.792042  192.168.0.29          192.168.0.13          SMTP     S: 235 Authentication successful.     866 169.992340  192.168.0.13          192.168.0.29          SMTP     C: MAIL FROM:<fabio.bonelli@ascontecnologic.com>     867 169.992709  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: MAIL FROM:<fabio.bonelli@ascontecnologic.com>     869 169.995201  192.168.0.29          192.168.0.13          SMTP     S: 250 OK     873 170.143969  192.168.0.13          192.168.0.29          SMTP     C: RCPT TO:<fabio.bonelli@gmail.com>     874 170.143971  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: RCPT TO:<fabio.bonelli@gmail.com>     876 170.146927  192.168.0.29          192.168.0.13          SMTP     S: 250 OK, recipient accepted     879 170.342851  192.168.0.13          192.168.0.29          SMTP     C: DATA     880 170.342853  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: DATA fragment, 6 bytes     882 170.343529  192.168.0.29          192.168.0.13          SMTP     S: 354 Send checkpointed message, ending in CRLF.CRLF     885 170.493241  192.168.0.13          192.168.0.29          SMTP     C: DATA fragment, 25 bytes     886 170.493243  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: DATA fragment, 25 bytes     889 170.544135  192.168.0.13          192.168.0.29          SMTP     C: DATA fragment, 41 bytes     890 170.544137  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: DATA fragment, 41 bytes     892 170.593376  192.168.0.13          192.168.0.29          SMTP     C: DATA fragment, 29 bytes     893 170.593766  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: DATA fragment, 29 bytes     895 170.643485  192.168.0.13          192.168.0.29          SMTP     C: DATA fragment, 33 bytes     896 170.643874  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: DATA fragment, 33 bytes     898 170.743780  192.168.0.13          192.168.0.29          SMTP     C: DATA fragment, 31 bytes     899 170.744147  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: DATA fragment, 31 bytes     901 170.845271  192.168.0.13          192.168.0.29          IMF      from: fabio.bonelli@ascontecnologic.com, from: fabio.bonelli@ascontecnologic.com, subject: From local mail server, subject: From local mail server\r\n,     902 170.845655  192.168.0.13          192.168.0.29          SMTP     [TCP Out-Of-Order] C: DATA fragment, 5 bytes     904 170.853859  192.168.0.29          192.168.0.13          SMTP     S: 250 OK     915 170.994652  192.168.0.13          192.168.0.29          SMTP     C: QUIT     916 170.995125  192.168.0.29          192.168.0.13          SMTP     S: 221 Closing connection </p><p> </p>

So you do have 'fabio fabio' in auth.pwd ?

I haven't that file. So could it be the problem?[:|] Explain better, please.

<p>> 09:52:59.013: Connection from 192.168.0.13, Wed Mar 09 09:52:59 2011<lf> > 09:52:59.013: << 220 192.168.0.29 ESMTP server ready.<cr><lf> > 09:53:00.153: >> EHLO [192.168.0.13]<cr><lf> > 09:53:00.169: << 250-192.168.0.29 Hello [192.168.0.13]; ESMTPs are:<cr><lf>250-TIME<cr><lf> > 09:53:00.169: << 250-SIZE 0<cr><lf> > 09:53:00.169: << 250-8BITMIME<cr><lf> > 09:53:00.169: << 250 HELP<cr><lf> > 09:53:00.309: >> AUTH LOGIN<cr><lf> > 09:53:00.309: << 334 VXNlcm5hbWU6<cr><lf> <b>Username:</b> > 09:53:00.465: >> ZmFiaW8=<cr><lf>  <b>fabio</b> > 09:53:00.465: << 334 UGFzc3dvcmQ6<cr><lf> <b>Password:</b> > 09:53:00.606: >> ZmFiaW8=<cr><lf> <b>fabio</b> Now you need to change this username and password.  These encoded strings can be decoded with any Base64 decoder. > 09:53:00.606: << 501 Authentication failed - bad user or password.<cr><lf> Check Configuration | MercuryS | Connection Control and verify that you have a password file with the user name fabio and password fabio </p><p>> 09:53:00.715: >> QUIT<cr><lf> > 09:53:00.715: << 221 192.168.0.29 Service closing channel.<cr><lf> > 09:53:00.715: --- Connection closed normally at Wed Mar 09 09:53:00 2011. --- > 09:53:00.715:  </p>

<p>Ok, thank you for the suggestion.</p><p>I've created the file <i>pw </i>in the mercury directory with one line:</p><p>fabio fabio</p><p>That is my user and password. Then I've checked <i>Only Authenticated SMTP connection may realy email</i>, where you say. In the input box there I write <i>pw</i>. </p><p><b>Now all is working fine</b>. Thank you very much. </p>