Bug 3012 - smtp for gmx.net no longer working
Summary: smtp for gmx.net no longer working
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (Windows)
Classification: Unclassified
Component: default (show other bugs)
Version: 3.9.1
Hardware: PC Windows XP
: P3 critical
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2013-10-15 14:40 UTC by t.st
Modified: 2015-07-25 16:35 UTC (History)
1 user (show)

See Also:


Attachments

Description t.st 2013-10-15 14:40:53 UTC
Maybe sombody can help ?!

i've installed gpg4win 2.2.0 end of August on several PC's with the same gmx.net-adress (only this one account) in claws mail and for many weeks it works fine with and without PGP/MIME.
These PC's working with WinXP, Win7proX64 and Win7ultimateX64.
But without changing anything, they all stop sending smtp-messages with the same Problem: ESMTP> EHLO unknown.
I've updated to gpg4win 2.2.1 and also tried claws mail 3.9.2 - nothing changed.
With same settings, the gmx.net-account works fine in WindowsLiveMail, Thunderbird and Outlook 2003/2007/2010 (GnuOL and PGP works too in all Outlooks)...

gmx.net-settings:
pop3 pop.gmx.net  ssl-port 995
smtp mail.gmx.net ssl-port 465

i've tried every possible setting in claws mail with/without ssl, but i get everytime the same errorlog:

* Konto 'pop.gmx.net': Verbinde mit POP3-Server: pop.gmx.net:995...
[14:00:57] POP3< +OK POP server ready H migmx108 0MVSgh-1VG8is0mBK-00Y6XU
[14:00:57] POP3> USER example@gmx.net
[14:00:57] POP3< +OK password required for user "example@gmx.net"
[14:00:57] POP3> PASS ********
[14:00:57] POP3< +OK mailbox "example@gmx.net" has 24 messages (1628605 octets) H migmx108
[14:00:57] POP3> STAT
[14:00:57] POP3< +OK 24 1628605
[14:00:57] POP3> UIDL
[14:00:57] POP3< +OK
[14:00:57] POP3> LIST
[14:00:57] POP3< +OK
[14:00:57] POP3> RETR 23
[14:00:57] POP3< +OK
[14:00:57] POP3> RETR 24
[14:00:57] POP3< +OK
[14:00:57] POP3> QUIT
[14:00:58] POP3< +OK POP server signing off
* Konto: 'pop.gmx.net': Verbinde mit SMTP-Server: mail.gmx.net:465...
[14:04:36] SMTP< 220 gmx.com (mrgmx103) Nemesis ESMTP Service ready
[14:04:36] ESMTP> EHLO unknown
[14:04:36] ESMTP< 550-Requested action not taken: mailbox unavailable
** Fehler bei der SMTP-Sitzung
*** Fehler beim Senden der Nachricht:
550-Requested action not taken: mailbox unavailable
Comment 1 Michael Rasmussen 2013-10-15 14:56:37 UTC
Hi,

If I am not mistaken there have been a recent fix to claws-mail solving problems with connecting to gmx.net. The fix is only available in GIT until a newer package is build. I do not know your skills in building claws-mail and especially claws-mail on Windows but if you are not able to do that you will have to wait until Colin releases a new Windows package. I have no knowledge of building claws-mail on Windows so I am not able to help you further.

Commit: http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=1907a085b18ccb65520d1f51d4f98164b1013496
Comment 2 t.st 2013-10-15 15:12:45 UTC
Hi Michael,

thank you very much, simple changes but i've never done it before and no tools installed for that, i think it's better to wait...
Comment 3 t.st 2013-10-15 16:27:52 UTC
OK thanks, Domainname "localhost" is working, but now smtp-communication stopps at this Point:

* Konto 'example@gmx.net': Verbinde mit POP3-Server: pop.gmx.net:995...
[16:15:12] POP3< +OK POP server ready H migmx005 0M75hT-1VionQ2VxW-00wY7t
[16:15:12] POP3> USER example@gmx.net
[16:15:12] POP3< +OK password required for user "example@gmx.net"
[16:15:12] POP3> PASS ********
[16:15:13] POP3< +OK mailbox "example@gmx.net" has 24 messages (1628605 octets) H migmx005
[16:15:13] POP3> STAT
[16:15:13] POP3< +OK 24 1628605
[16:15:13] POP3> UIDL
[16:15:13] POP3< +OK
[16:15:13] POP3> LIST
[16:15:13] POP3< +OK
[16:15:13] POP3> RETR 21
[16:15:13] POP3< +OK
[16:15:13] POP3> RETR 22
[16:15:14] POP3< +OK
[16:15:15] POP3> RETR 23
[16:15:15] POP3< +OK
[16:15:15] POP3> RETR 24
[16:15:15] POP3< +OK
[16:15:16] POP3> QUIT
[16:15:16] POP3< +OK POP server signing off
* Konto: 'example@gmx.net': Verbinde mit SMTP-Server: mail.gmx.net:465...
[16:18:25] SMTP< 220 gmx.com (mrgmx001) Nemesis ESMTP Service ready
[16:18:25] ESMTP> EHLO localhost
[16:18:25] ESMTP< 250-gmx.com Hello localhost [84.190.166.32]
[16:18:25] ESMTP< 250-SIZE 69920427
[16:18:25] ESMTP< 250 AUTH LOGIN PLAIN
[16:18:25] ESMTP> AUTH LOGIN
[16:18:25] ESMTP< 334 VXNlcm5hbWU6
[16:18:25] ESMTP> [USERID]
[16:18:25] ESMTP< 334 UGFzc3dvcmQ6
[16:18:25] ESMTP> [PASSWORD]
[16:18:26] ESMTP< 235 Authentication succeeded
[16:18:26] ESMTP> MAIL FROM:<example@gmx.net> SIZE=2385
[16:18:26] SMTP< 250 Requested mail action okay, completed
[16:18:26] SMTP> RCPT TO:<example@o2mail.de>
[16:18:26] SMTP< 550-Requested action not taken: mailbox unavailable
** Fehler bei der SMTP-Sitzung
*** Fehler beim Senden der Nachricht:
550-Requested action not taken: mailbox unavailable
Comment 4 t.st 2013-10-15 16:31:51 UTC
P.S.
Without PGP/MIME it is working, but i needed...
Comment 5 Manfred Schmitt 2013-10-17 18:22:09 UTC
It looks like the GMX/Web.de spam-admins borked the antispam-rules:

https://www.heinlein-support.de/blog/mailserver/gmx-blockt-e-mail-adressen-ohne-aaaaa-record/

english version via google:
http://translate.google.de/translate?sl=auto&tl=en&u=http%3A%2F%2Fwww.heinlein-support.de%2Fblog%2Fmailserver%2Fgmx-blockt-e-mail-adressen-ohne-aaaaa-record

Rough english translation:
Since a few days gmx.de/.net and web.de (-> same company) are blocking mails from domains without A or AAAA Record but with correct MX Record (which should be enough). The blocking based on irregular/invalid or not existing helo seems to be a side effect.
The technicians are trying to resolve the issue but when it will be
fixed completely and/or working again on all servers is unclear.
I don't think the blocking has something to do with gnupg at all, try hard enough and the mail will be sent successfully ;-)
I could at least sent some gnupg-encrypted testmails via GMX from within claws without a problem.
Comment 6 Andrej Kacian 2015-07-25 16:35:16 UTC
Not a Claws Mail bug, this is something on gmx.net side.

Note You need to log in before you can comment on or make changes to this bug.