#43 "The SMTP server did not accept Auth PLAIN value."
Hi, I have an interesting problem. I have two computers, both running exactly the same scripts, with exactly the same versions of Blat (the script and blat are being run off a shared network drive).
Computer A - (WinXP/SP2) sends mail fine
Computer B - (also WinXP/no SP) chokes. Here's the output log:
V:\tools>blat262\full\blat.exe test.bat -server mail.domain_removed.com -f mailer@domain_removed.com -pw pw_removed -to "robert@domain_removed.com" -subject "TESTING"
Blat v2.6.2 w/GSS encryption (build : Feb 25 2007 12:06:19)
Sending test.bat to robert@domain_removed.com
Subject: TESTING
Login name is mailer@domain_removed.com
The SMTP server did not accept Auth PLAIN value.
Are your login userid and password correct?
The SMTP server did not accept Auth LOGIN PASSWD value.
Sniffing the SMTP I/O shows both A and B doing the same thing. The only difference is that B just stops after the initial 250-* data comes back from the server. Here's the trace - I've marked where B stops and throws it's errors.
220 swarthymail-a2.g.dreamhost.com ESMTP
EHLO bigeddy
250-swarthymail-a2.g.dreamhost.com
250-PIPELINING
250-SIZE 40960000
250-ETRN
250-STARTTLS
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
250 8BITMIME
==== Computer B stops here. Computer A continues on ... ===
MAIL FROM:<mailer@domain_removed.com>
250 Ok
RCPT TO:<robert@domain_removed.com>
250 Ok
DATA
354 End data with <CR><LF>.<CR><LF>
Date: Fri, 29 Jun 2007 06:19:46 -0700
From: mailer@domain_removed.com
To: robert@domain_removed.com
X-Mailer: Blat v2.6.2 w/GSS encryption, a Win32 SMTP/NNTP mailer http://www.blat.net
Message-ID: <01c7ba50$Blat.v2.6.2$29bf5fca$158a9a1ef78@domain_removed.com>
Subject: TESTING
Content-Transfer-Encoding: 8BIT
Content-Type: text/plain; charset=ISO-8859-1
blat262\full\blat.exe test.bat -server mail.domain_removed.com -f mailer@domain_removed.com -pw pw_removed -to "robert@domain_removed.com" -subject "TESTING"
.
250 Ok: queued as 25AE1EEAA7
QUIT
221 Bye
Logged In: YES
user_id=800692
Originator: NO
First, I would search both computers and ensure that you do not have another copy of Blat.exe somewhere. I know, that's a stretch, but worth doing all the same.
From your trace, I do not see where Blat issues the login request. I also do not see where you specified the userid value via -U option.
The next item I would like to know is what are the timestamps from your trace? These could give a clue about how long system A takes to receive packets versus system B; if system B takes longer, then it might be that system B has timed out and throws an error message because the last 250 message has not arrived, yet. You might also change the timeout value from the default 30 seconds to more like 90 seconds with -ti (timeout) option.
--
Chip