[Users] [Bug 3252] New: smtp authentication at smtp server of GMX fails - permanent error - no sending
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Wed Aug 20 22:56:27 CEST 2014
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3252
Bug ID: 3252
Summary: smtp authentication at smtp server of GMX fails -
permanent error - no sending
Classification: Unclassified
Product: Claws Mail
Version: 3.9.2
Hardware: PC
OS: Linux
Status: NEW
Severity: critical
Priority: P3
Component: SMTP
Assignee: users at lists.claws-mail.org
Reporter: jpg153 at yahoo.de
Since some month GMX changed to SSL/STARTTLS when accessing the mail account
(free mail).
Retrieving emails from the POP3 server runs flawless.
Sending emails worked, since some weeks ago it stopped because of an
authetication error when logging in to the smtp server. After a few days all
went normal.
Now I have the same issue again and this time persistent.
I tried to change settings in Clawsmail to get around the problem, but
regardless which setting I chose, none works.
The most common and so critical error is:
* Konto: 'XXXXXX at gmx.de': Verbinde mit SMTP-Server: mail.gmx.net:587...
[22:52:44] SMTP< 220 gmx.com (mrgmx102) Nemesis ESMTP Service ready
[22:52:44] ESMTP> EHLO gmx.net
[22:52:44] ESMTP< 250-gmx.com Hello gmx.net [88.76.173.36]
[22:52:44] ESMTP< 250-SIZE 69920427
[22:52:44] ESMTP< 250-AUTH LOGIN PLAIN
[22:52:44] ESMTP< 250 STARTTLS
[22:52:44] ESMTP> STARTTLS
[22:52:44] ESMTP< 220 OK
[22:52:44] ESMTP> EHLO gmx.net
[22:52:44] ESMTP< 250-gmx.com Hello gmx.net [88.76.173.36]
[22:52:44] ESMTP< 250-SIZE 69920427
[22:52:44] ESMTP< 250 AUTH LOGIN PLAIN
[22:52:44] ESMTP> AUTH LOGIN
[22:52:44] ESMTP< 334 VXNlcm5hbWU6
[22:52:44] ESMTP> [USERID]
[22:52:44] ESMTP< 334 UGFzc3dvcmQ6
[22:52:44] ESMTP> [PASSWORD]
[22:52:44] ESMTP< 535 Authentication credentials invalid
** Fehler bei der Anmeldung
*** Authentifizierung schlug fehl:
535 Authentication credentials invalid
I have no idea whether this is a bug in Clawsmail or a bug at GMX. However, GMX
support is too busy or not replying.
Thanks for looking into the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list