<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 01/25/2015 03:30 AM, Michael
Schwendt wrote:<br>
</div>
<blockquote cite="mid:20150125103003.7b2d87f7@gmx.net" type="cite">
<pre wrap="">On Sun, 25 Jan 2015 09:55:16 +0100, Andrej Kacian wrote:
</pre>
<blockquote type="cite">
<pre wrap="">From the available data, it looks like this is a server issue. There
is no way a server can not understand "AUTH" command after it told
the client that it supports authentication.
</pre>
</blockquote>
<pre wrap="">Agreed. One can clearly see that the server responds to "AUTH LOGIN" in
the working case. And if it once did and later doesn't, it's a server
issue:
[15:37:35] ESMTP> AUTH LOGIN
[15:37:35] ESMTP< 334 VXNlcm5hbWU6
[15:37:35] ESMTP> [USERID]
[15:37:35] ESMTP< 334 UGFzc3dvcmQ6
[15:37:35] ESMTP> [PASSWORD]
[15:37:35] ESMTP< 235 Authentication succeeded
[15:45:59] ESMTP> AUTH LOGIN
[15:45:59] ESMTP< 500 unrecognized command
</pre>
<blockquote type="cite">
<pre wrap="">Can you get someone to look at the server logs?
</pre>
</blockquote>
<pre wrap="">
Also, what appears in the log with TLS enabled? Talking to the server
from the outside, it doesn't offer plain auth for a test:
$ telnet mercury.linksky126.com 25
Trying 184.173.222.73...
Connected to mercury.linksky126.com.
Escape character is '^]'.
EH220-mercury.linksky126.com ESMTP Exim 4.84 #2 Sun, 25 Jan 2015 03:25:02 -0600
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
EHLO blubb
250-mercury.linksky126.com Hello XXX [xxx.xxx.xxx.xxx]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-STARTTLS
250 HELP
STARTTLS
220 TLS go ahead
…
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.claws-mail.org">Users@lists.claws-mail.org</a>
<a class="moz-txt-link-freetext" href="http://lists.claws-mail.org/cgi-bin/mailman/listinfo/users">http://lists.claws-mail.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
Remember I'm smiling as I say this. Traditional IT users trap, "I
didn't do it" from both sides (I really am smiling).<br>
<br>
The host is thinking it's on the software side. I'll pass on their
tidbits and then I add some things I've teste as well.<br>
<br>
The first message I got from them was that they had found a log
entry and had a comment:<br>
<br>
2015-01-25 13:39:04 dovecot_login authenticator failed for <a
href="http://173-31-180-217.client.mchsi.com" target="_blank">173-31-180-217.client.mchsi.<wbr>com</a>
(#localhost.localdomain) [173.31.180.217]:47843: 535 Incorrect
authentication data<br>
<br>
"The above log example indicates a login failure due to "Incorrect
authentication data". This could be use of a bad password, or it may
have to so with an incorrect configuration on the client side."<br>
<br>
Later, they also commented on Andrej's <span class="im">thought
"From the available data, it looks like this is a server issue.
There is no way a server can not understand "AUTH" command after
it told the client that it supports authentication." <br>
<br>
with this:<br>
<br>
</span>"Please know - if that were true, (There is no way a server
can not understand "AUTH" command ) then no email clients would be
able to connect to any of our mail services." <br>
<br>
Basically they are saying that they have mail traffic moving and an
"AUTH" working this badly would cause chaos.<br>
<br>
Now for my observations trying to get set up. First I have set up
this hosted email account and a gmail account using Claws on Windows
7. Both accounts can send mail and receive mail no problems. These
two accounts and others I have all work in Thunderbird on both
Windows and Linux as well (the one's on Thunderbird Linux were set
up the same day just before and after I'd started trying Claws). So
I think I've got all my username, password, settings pretty well in
hand.<br>
<br>
It's only when I try to use Claws on Fedora 20, LXDE desktop (I did
try once from KDE). I took screen captures on the Windows Claws
account settings, all 8 screens, and used that to enter the same
settings on the Linux Claws. I've also re-entered user and passwords
(I typed passwords in on the Windows side where it worked, so I at
least type them in right there). There is also a "saved passwords"
addon for Thunderbird which allows one to copy the user and password
out of an account which I used to get text to paste into Claws. All
these things failed to get me going with Claws on Linux.<br>
<br>
At this point, I've passed on the Windows (working) and Linux (not
working) network logs for my hosted email account when I sent the
original email. So here's the working (windows) and not working
(Linux) network logs captured out of Claws when I tried to send mail
using gmail. It's a might different than for my hosted email, but it
fails at that AUTH LOGIN on gmail just like the other (I X'd out my
mail info):<br>
<br>
Windows log <br>
<br>
* Account 'XXXXXXXXXX': Connecting to SMTP server:
smtp.googlemail.com:465...
<br>
[16:54:30] SMTP< 220 mx.google.com ESMTP 14sm4965540iot.22 -
gsmtp
<br>
[16:54:30] ESMTP> EHLO localhost
<br>
[16:54:30] ESMTP< 250-mx.google.com at your service,
[173.31.180.217]
<br>
[16:54:30] ESMTP< 250-SIZE 35882577
<br>
[16:54:30] ESMTP< 250-8BITMIME
<br>
[16:54:30] ESMTP< 250-AUTH LOGIN PLAIN XOAUTH XOAUTH2
PLAIN-CLIENTTOKEN
<br>
[16:54:30] ESMTP< 250-ENHANCEDSTATUSCODES
<br>
[16:54:30] ESMTP< 250-PIPELINING
<br>
[16:54:30] ESMTP< 250-CHUNKING
<br>
[16:54:30] ESMTP< 250 SMTPUTF8
<br>
[16:54:31] ESMTP> AUTH LOGIN
<br>
[16:54:31] ESMTP< 334 VXNlcm5hbWU6
<br>
[16:54:31] ESMTP> [USERID]
<br>
[16:54:31] ESMTP< 334 UGFzc3dvcmQ6
<br>
[16:54:31] ESMTP> [PASSWORD]
<br>
[16:54:31] ESMTP< 235 2.7.0 Accepted
<br>
[16:54:31] ESMTP> MAIL FROM:<a class="moz-txt-link-rfc2396E" href="mailto:XXXXXXXXXX@gmail.com"><XXXXXXXXXX@gmail.com></a>
SIZE=577
<br>
[16:54:31] SMTP< 250 2.1.0 OK 14sm4965540iot.22 - gsmtp
<br>
[16:54:31] SMTP> RCPT TO:<a class="moz-txt-link-rfc2396E" href="mailto:XXXXXXXXXX@gmail.com"><XXXXXXXXXX@gmail.com></a>
<br>
[16:54:31] SMTP< 250 2.1.5 OK 14sm4965540iot.22 - gsmtp
<br>
[16:54:31] SMTP> DATA
<br>
[16:54:31] SMTP< 354 Go ahead 14sm4965540iot.22 - gsmtp
<br>
[16:54:31] SMTP> . (EOM)
<br>
[16:54:31] SMTP< 250 2.0.0 OK 1422226465 14sm4965540iot.22 -
gsmtp
<br>
* Mail sent successfully.<br>
<br>
Linux log<br>
<br>
* Account 'XXXXXXXXXX': Connecting to SMTP server:
smtp.googlemail.com:465...<br>
[16:41:30] SMTP< 220 mx.google.com ESMTP vk4sm4817764igc.11 -
gsmtp<br>
[16:41:30] ESMTP> EHLO #localhost.localdomain<br>
panlap.guypan<br>
[16:41:30] ESMTP< 250-mx.google.com at your service,
[173.31.180.217]<br>
[16:41:30] ESMTP< 250-SIZE 35882577<br>
[16:41:30] ESMTP< 250-8BITMIME<br>
[16:41:30] ESMTP< 250-AUTH LOGIN PLAIN XOAUTH XOAUTH2
PLAIN-CLIENTTOKEN<br>
[16:41:30] ESMTP< 250-ENHANCEDSTATUSCODES<br>
[16:41:30] ESMTP< 250-PIPELINING<br>
[16:41:30] ESMTP< 250-CHUNKING<br>
[16:41:30] ESMTP< 250 SMTPUTF8<br>
[16:41:30] ESMTP> AUTH LOGIN<br>
[16:41:30] ESMTP< 502 5.5.1 Unrecognized command.
vk4sm4817764igc.11 - gsmtp<br>
** error occurred on SMTP session<br>
*** Error occurred while sending the message:<br>
502 5.5.1 Unrecognized command. vk4sm4817764igc.11 - gsmtp<br>
<br>
<br>
If there's anything else I could try, just let me know. I kind of
like the flexibility and responsiveness of Claws and would like to
get over this hump!<br>
</body>
</html>