Hallo Everybody!
Thanks for 2 replies, which replied, that mail.gmx.net:465 is not a propper ssl server: well, i tried with another email client (Opera), sending AUTH PLAIN and AUTH LOGIN and both worked.
So I tried all possible configs in Calypso to get a successful smtp login, but it fails everytime with the same err.msg(see below)
The funny thing is, the getting mail, login pop.gmx.net:995 works perfect via stunnel, but smtp fails....
So I want to ask, if there is anyone out there, who works successully with CALYPSO, stunnel and GMX-Provider??
In case, please tell me your settings - would be great!
Thanks Johann
my last question: ------ trying hard to get stunnel worked with Calypso email client! When I only check emails, it works via stunnel at ssl port 995. But sending email fails with following message from Calypso:
*** Sending pending mail from account xyz@gmx.net' @ 13.12.2013 01:54 *** Connecting to: '127.0.0.1' -> Successful Logging into the SMTP server as: "xxx" The server does not support any secure password authentication providers Disconnecting -> Successful Failed to send one or more pending messages. Smtp.c[287] Smtp.dll
the config file via stunnel looks so:
cert = stunnel.pem [gmx-pop3] client = yes accept = 127.0.0.1:108 connect = pop.gmx.net:995 [gmx-smtp] client = yes accept = 127.0.0.1:107 connect = mail.gmx.net:465
the mailserver- config of Calypso is so:
pop3: 127.0.0.1 port 108 smtp: 127.0.0.1 port 107 smtp authentication method: user pop account....
So, I am really out of ideas to get the very best email client of the world - CALYPSO - running to send emails via ssl connection, wich my provider forces me to send via ssl from 1.jan.2014...
Anyone can help? thanks allot! johann
On 13 Dec 2013 at 14:39, greeksalad wrote:
To: stunnel-users@stunnel.org Date sent: Fri, 13 Dec 2013 14:39:18 +0100 From: greeksalad greeksalad@gmx.net Subject: [stunnel-users] stunnel and Calypso and GMX: Anyone out there where stunnel works with Calypso?
Hallo Everybody!
Thanks for 2 replies, which replied, that mail.gmx.net:465 is not a propper ssl server: well, i tried with another email client (Opera), sending AUTH PLAIN and AUTH LOGIN and both worked.
So I tried all possible configs in Calypso to get a successful smtp login, but it fails everytime with the same err.msg(see below)
The funny thing is, the getting mail, login pop.gmx.net:995 works perfect via stunnel, but smtp fails....
So I want to ask, if there is anyone out there, who works successully with CALYPSO, stunnel and GMX-Provider??
In case, please tell me your settings - would be great!
Just as a test I added the following to my stunnel.conf to see what happens. [gmxsmtp] client = yes accept = 25465 connect = mail.gmx.net:465
[root@setzco stunnel]# telnet 127.0.0.1 25465 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. 220 gmx.com (mrgmx103) Nemesis ESMTP Service ready
I use Pegasus Mail, and with it I have to set the ssl to off, since it isn't doing the ssl, but stunnel is. What are you seeing in the load file after the failed connection.
My stunnel.conf shows these lines with debug = 5
2013.12.13 23:55:11 LOG5[7134:140038679107328]: Service [gmxsmtp] accepted connection from 127.0.0.1:50903 2013.12.13 23:55:11 LOG5[7134:140038679107328]: connect_blocking: connected 212.227.17.190:465 2013.12.13 23:55:11 LOG5[7134:140038679107328]: Service [versmtp] connected remote server from 192.168.128.201:48297 2013.12.13 23:55:18 LOG5[7134:140038679107328]: Connection closed: 5 byte(s) sent to SSL, 52 byte(s) sent to socket
Thanks Johann
my last question:
trying hard to get stunnel worked with Calypso email client! When I only check emails, it works via stunnel at ssl port 995. But sending email fails with following message from Calypso:
*** Sending pending mail from account xyz@gmx.net' @ 13.12.2013 01:54 *** Connecting to: '127.0.0.1' -> Successful Logging into the SMTP server as: "xxx" The server does not support any secure password authentication providers Disconnecting -> Successful Failed to send one or more pending messages. Smtp.c[287] Smtp.dll
the config file via stunnel looks so:
cert = stunnel.pem [gmx-pop3] client = yes accept = 127.0.0.1:108 connect = pop.gmx.net:995 [gmx-smtp] client = yes accept = 127.0.0.1:107 connect = mail.gmx.net:465
the mailserver- config of Calypso is so:
pop3: 127.0.0.1 port 108 smtp: 127.0.0.1 port 107 smtp authentication method: user pop account....
So, I am really out of ideas to get the very best email client of the world - CALYPSO - running to send emails via ssl connection, wich my provider forces me to send via ssl from 1.jan.2014...
Anyone can help? thanks allot! johann _______________________________________________ stunnel-users mailing list stunnel-users@stunnel.org https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
+----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes@kuentos.guam.net mailto:msetzerii@gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +----------------------------------------------------------+
http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489)
BOINC@HOME CREDITS ROSETTA 9510771.215339 | SETI 16971978.540877 ABC 16473629.939784 | EINSTEIN 14580179.819852
On 13.12.2013 14:57, Michael D. Setzer II wrote:
On 13 Dec 2013 at 14:39, greeksalad wrote:
Thanks for 2 replies, which replied, that mail.gmx.net:465 is not a propper ssl server: well, i tried with another email client (Opera), sending AUTH PLAIN and AUTH LOGIN and both worked.
My stunnel.conf shows these lines with debug = 5
2013.12.13 23:55:11 LOG5[7134:140038679107328]: Service [versmtp] connected remote server from 192.168.128.201:48297 2013.12.13 23:55:18 LOG5[7134:140038679107328]: Connection closed: 5 byte(s) sent to SSL, 52 byte(s) sent to socket
FWIW, I connected to both IPs of "mail.gmx.net" with OpenSSL's s_client command and found that they wouldn't reply to HELO/EHLOs (but instead time out the connection after a while of not replying).
220 gmx.com (mrgmx101) Nemesis ESMTP Service ready HELO mydom.ain
[~100s later]
421 gmx.com Service closing transmission channel - command timeout closed
IMHO the (E)SMTP implementation of these servers is broken.
Regards, J. Bern