<p>The username and password from the session are just Base64 encoded, not encrypted, so anyone using a Base64 decoder can read it...</p><p>Good to hear it worked with msendto.exe! </p><p>/Rolf </p>

<p>I would like to be able to send e-mail from a script that has been called by Mercury's Global Filtering to a user account on my LAN.  Can I do this without having to go outside of my LAN (e.g. for DNS lookup)?  Currently I have been using blat as a command-line mail sending application from within my script.  A typical blat line is (I have manufactured this example to protect the innocent (me)):</p><p>C:Mercury/blat $Msg_File -to <a mce_href="mailto:Gordon@localhost." href="mailto:Gordon@localhost.">Gordon@localhost.</a> -from <a mce_href="mailto:Gordon@localhost" href="mailto:Gordon@localhost">Gordon@localhost</a>. -subject "Script Notification" -server localhost -port 25 -u <a mce_href="mailto:Gordon@localhost" href="mailto:Gordon@localhost">Gordon@localhost</a> -pw password -debug -log C:/MERCURY/blat.log -timestamp</p><p>The blat log shows the following exchange with MercuryS:</p><p>2009.09.02 18:04:16 (Wed)------------Start of Session----------------- Blat v2.6.2 w/GSS encryption (build : Feb 25 2007 12:06:19) 2009.09.02 18:04:16 (Wed): <<<getline<<< 220 Computer ESMTP server ready. 2009.09.02 18:04:16 (Wed): >>>putline>>> EHLO delta2 2009.09.02 18:04:16 (Wed): <<<getline<<< 250-Delta Hello Computer; ESMTPs are: 2009.09.02 18:04:16 (Wed): <<<getline<<< 250-TIME 2009.09.02 18:04:16 (Wed): <<<getline<<< 250-SIZE 0 2009.09.02 18:04:16 (Wed): <<<getline<<< 250 HELP 2009.09.02 18:04:16 (Wed): Sending C:/MERCURY/TestMessage.txt to <a mce_href="mailto:Gordon@localhost" href="mailto:Gordon@localhost">Gordon@localhost</a> 2009.09.02 18:04:16 (Wed): Subject: SMTP_Test 2009.09.02 18:04:16 (Wed): Login name is <a mce_href="mailto:GordonNew@127.0.0.1" href="mailto:GordonNew@127.0.0.1">Gordon@localhost</a> 2009.09.02 18:04:16 (Wed): >>>putline>>> AUTH LOGIN 2009.09.02 18:04:16 (Wed): <<<getline<<< 334 VXNlcm5hbWU6 2009.09.02 18:04:16 (Wed): >>>putline>>> R29yZG9uTmV3QDEyNy4wLjAuMQ== 2009.09.02 18:04:16 (Wed): <<<getline<<< 334 UGFzc3dvcmQ6 2009.09.02 18:04:16 (Wed): >>>putline>>> [edited: password removed] 2009.09.02 18:04:16 (Wed): <<<getline<<< 501 Authentication failed - bad user or password. 2009.09.02 18:04:16 (Wed): The SMTP server did not accept Auth LOGIN PASSWD value. 2009.09.02 18:04:16 (Wed): >>>putline>>> QUIT 2009.09.02 18:04:16 (Wed): <<<getline<<< 221 Delta Service closing channel. 2009.09.02 18:04:16 (Wed)-------------End of Session------------------</p><p>I am absolutely sure that I am using the correct password for the account Gordon.</p><p>Maybe this is a blat issue, though I have used it successfully with external servers.</p><p>Is MercuryS happy with an address like <a mce_href="mailto:GordonNew@127.0.0.1" href="mailto:GordonNew@127.0.0.1">Gordon@localhost</a> or does it insist upon using DNS.  I have also tried to use 127.0.0.1 instead of localhost, but the result is the same.</p><p>So my question is, why is MercuryS rejecting the login.</p><p>Note that Connection Control lists 127.0.0.1 as a valid connection source.</p><p>Thank you</p><p>Gordon </p>

<p>As the AUTH fails, make sure you are sending exactly the same username as in your auth file. In this exemple you are sending <span class="Apple-style-span" style="font-family: -webkit-monospace; white-space: pre-wrap; ">GordonNew@127.0.0.1.</span></p><p>Note that the password now is publicly known - you will need to replace it.</p><p>Furthermore there is a command line mail client included with Mercury called msendto.exe </p><p>/Rolf </p>

<P>Rolf - How did you find <SPAN style="FONT-FAMILY: -webkit-monospace; WHITE-SPACE: pre-wrap" class=Apple-style-span><A href="mailto:GordonNew@127.0.0.1" mce_href="mailto:GordonNew@127.0.0.1">GordonNew@127.0.0.1</A>?  I don't see it in what I posted.  Also, I am not clear how I have exposed the real password.  Have you decoded some of the server transaction in some way?</SPAN></P> <P><SPAN style="FONT-FAMILY: -webkit-monospace; WHITE-SPACE: pre-wrap" class=Apple-style-span>Thank you for the tip about msendto.exe.  I wasn't aware of this.</SPAN></P> <P><SPAN style="FONT-FAMILY: -webkit-monospace; WHITE-SPACE: pre-wrap" class=Apple-style-span>Thank you</SPAN></P> <P><SPAN style="FONT-FAMILY: -webkit-monospace; WHITE-SPACE: pre-wrap" class=Apple-style-span>Gordon</SPAN></P> <P><SPAN style="FONT-FAMILY: -webkit-monospace; WHITE-SPACE: pre-wrap" class=Apple-style-span><U>Edited </U>.... Oh, I now see the <SPAN style="FONT-FAMILY: -webkit-monospace; WHITE-SPACE: pre-wrap" class=Apple-style-span><A href="mailto:GordonNew@127.0.0.1" mce_href="mailto:GordonNew@127.0.0.1">GordonNew@127.0.0.1</A> in the html, but I don't see the password (no real ones, anyway).  Have I missed something?</SPAN></SPAN></P> <P><SPAN style="FONT-FAMILY: -webkit-monospace; WHITE-SPACE: pre-wrap" class=Apple-style-span><SPAN style="FONT-FAMILY: -webkit-monospace; WHITE-SPACE: pre-wrap" class=Apple-style-span>Gordon</SPAN></SPAN></P>

<P>Rolf - I just tested msendto.exe and it seems that it is what I need to use.  I had a small problem sorting out the To/From addressing.  <A href="mailto:username@localhost">username@localhost</A> caused a complaint that this isn't a fully qualified address and <A href="mailto:username@127.0.0.1">username@127.0.0.1</A> apparently has "bad sender address syntax".  In both of these cases, the address was assumed to be non-local (presume because of the "@").  However, just using "username" was successful and was accepted as local.</P> <P>Gordon</P> <P mce_keep="true"> </P>