<p>Ok, figured out my problem.</p><p>My handler was returning 1, instead of returning 0, which was why Mercury returned 235. My handler should be returning 0, so that Mercury will return 334.</p><p>Issue resolved. </p>

<p>Hi everyone,</p><p>I have a problem with the Mercury SMTP server.</p><p>Here's a log of a session:</p><p>04:08:44.867: Connection from 124.77.145.122, Wed Dec 18 04:08:44 2013<lf> 04:08:44.867: << 220 announcer ESMTP server ready.<cr><lf> 04:08:45.240: >> EHLO q-86cf7b5066fb4<cr><lf> 04:08:45.240: << 250-announcer Hello q-86cf7b5066fb4; ESMTPs are:<cr><lf>250-TIME<cr><lf> 04:08:45.240: << 250-SIZE 0<cr><lf> 04:08:45.240: << 250-AUTH CRAM-MD5 LOGIN<cr><lf> 04:08:45.240: << 250-AUTH=LOGIN<cr><lf> 04:08:45.240: << 250 HELP<cr><lf> 04:08:48.360: >> AUTH LOGIN<cr><lf> 04:08:48.360: << 334 VXNlcm5hbWU6<cr><lf> 04:08:49.655: >> d2VibWFzdGVy<cr><lf> 04:08:49.655: << 334 UGFzc3dvcmQ6<cr><lf> </p><p>As you can see, after the client sends AUTH LOGIN, Mercury SMTP sends 334.</p><p>On the other hand, when I tried to simulate this by performing telnet MercurySMTPServerHostName 25, I get a 235 instead, as the log session below shows:</p><p>09:19:43.053: << 220 announcer ESMTP server ready.<cr><lf> 09:19:45.440: >> EHLO ME<cr><lf> 09:19:45.440: << 250-announcer Hello ME; ESMTPs are:<cr><lf>250-TIME<cr><lf> 09:19:45.440: << 250-SIZE 0<cr><lf> 09:19:45.440: << 250-AUTH CRAM-MD5 LOGIN<cr><lf> 09:19:45.440: << 250-AUTH=LOGIN<cr><lf> 09:19:45.440: << 250 HELP<cr><lf> 09:20:03.803: >> auth login<cr><lf> 09:20:03.819: << 235 Authentication successful.<cr><lf> 09:20:17.732: >> quit<cr><lf>  </p><p>Why am I not getting a 334 response? </p>