Hello:
I recently came across stunnel as a solution (THE solution) to Pegasus Mail 4.63 having some sort of incompatibility with SSL versions in use at gmx.de and xsmail.com mail services.
As I was absolutely unwilling to let go of my trusty PMailo, stunnel proved to be a godsend. =-)
At first the problem was with xsmail only and after setting up stunnel everything went along perfectly well, no problems whatsoever.
Now, gmx.de is enforcing the use of SSL on ports 993, 995 and 465 instead of 110, 25 and 143 so I edited my stunnel.conf accordingly.
---
;*********************************************************************** ;Configured service ;***********************************************************************
;Pegasus Mail ;SSL connections to XSMail's servers ;Reason: there's some incompat between PMail 4.63 and SSL - 01/11/2013
[xsmail-POP3-SSL] client = yes accept = 10995 connect = mail.messagingengine.com:995
[xsmail-smtp-SSL] client = yes accept = 10465 connect = mail.messagingengine.com:465
[xsmail-IMAP-SSL] client = yes accept = 10993 connect = mail.messagingengine.com:993
;Pegasus Mail ;SSL connections to GMX's servers ;Reason: there's some incompat between PMail 4.63 and SSL - 01/11/2013
[gmx-POP3-SSL] client = yes accept = 10995 connect = pop.gmx.net:995
[gmx-smtp-SSL] client = yes accept = 10465 connect = mail.gmx.net:465
[gmx-IMAP-SSL] client = yes accept = 10993 connect = imap.gmx.net:993
---
The issue at hand is that stunnel in not working properly now.
This is the log file for a successful connection to xsmail:
---
2013.12.14 17:15:08 LOG5[500:284]: Service [xsmail-POP3-SSL] accepted connection from 127.0.0.1:1182
2013.12.14 17:15:08 LOG5[500:284]: connect_blocking: connected 66.111.4.51:995
2013.12.14 17:15:08 LOG5[500:284]: Service [xsmail-POP3-SSL] connected remote server from 192.168.1.102:1183
2013.12.14 17:15:10 LOG5[500:284]: Connection closed: 58 byte(s) sent to SSL, 112 byte(s) sent to socket
---
And this is the log file for a (failed) connection to gmx:
---
2013.12.14 17:17:15 LOG5[500:452]: Service [xsmail-POP3-SSL] accepted connection from 127.0.0.1:1184
2013.12.14 17:17:15 LOG5[500:452]: connect_blocking: connected 66.111.4.52:995
2013.12.14 17:17:15 LOG5[500:452]: Service [xsmail-POP3-SSL] connected remote server from 192.168.1.102:1185
2013.12.14 17:17:21 LOG5[500:452]: Connection closed: 36 byte(s) sent to SSL, 126 byte(s) sent to socket
---
The PMail trace is this as follows:
[*] Connection established to 127.0.0.1
0016 +OK POP3 ready
<< 0015 USER 14067985
0005 +OK
<< 0015 PASS XXXXXXXX
0083 -ERR You must use your full username of the form
yourusername@domain.tld to login
Figures ... It is attempting to connect to gmx with xsmail credentials.
As youcan see, for some strange reason it is connecting to gmx with xsmail settings.
Must be a *.conf file problem but I am at a loss as to what is gong on Any ideas?
Thanks in advance,
CIV
On 14 Dec 2013 at 17:25, sawbona@flashmail.com wrote:
From: sawbona@flashmail.com Organization: Marx Brothers & Co. To: stunnel-users@stunnel.org Date sent: Sat, 14 Dec 2013 17:25:32 -0300 Priority: normal Subject: [stunnel-users] stunnel and Pegasus Mail Send reply to: sawbona@flashmail.com patches" <stunnel-users.stunnel.org>
Hello:
I recently came across stunnel as a solution (THE solution) to Pegasus Mail 4.63 having some sort of incompatibility with SSL versions in use at gmx.de and xsmail.com mail services.
As I was absolutely unwilling to let go of my trusty PMailo, stunnel proved to be a godsend. =-)
At first the problem was with xsmail only and after setting up stunnel everything went along perfectly well, no problems whatsoever.
Now, gmx.de is enforcing the use of SSL on ports 993, 995 and 465 instead of 110, 25 and 143 so I edited my stunnel.conf accordingly.
You need to use a different set of ports for the gmx setup.
I have two different accounts on gmail, one personel, and one that my college now uses. So, the one identity uses the ports in the 20xxx range and the other uses the ones in the 21xxx range. It is the port numbers that need to be different, not just the names in the configuration. Also, need to set this in the configurations of pegaus to use the correct port for each connection.
[gmailpop] client=yes accept = 20995 connect = pop.gmail.com:995
[gmailsmtp] client=yes accept = 20465 connect = smtp.gmail.com:465
[gmailimap] client=yes accept = 20993 connect = imap.gmail.com:993
[gccpop] client = yes accept = 21995 connect = pop.guamcc.edu:995
[gccsmtp] client = yes accept = 21465 connect = smtp.guamcc.edu:465
[gccimap] client = yes accept = 21993 connect = imap.guamcc.edu:993
;********************************************************************* ** ;Configured service ;********************************************************************* **
;Pegasus Mail ;SSL connections to XSMail's servers ;Reason: there's some incompat between PMail 4.63 and SSL - 01/11/2013
[xsmail-POP3-SSL] client = yes accept = 10995 connect = mail.messagingengine.com:995
[xsmail-smtp-SSL] client = yes accept = 10465 connect = mail.messagingengine.com:465
[xsmail-IMAP-SSL] client = yes accept = 10993 connect = mail.messagingengine.com:993
;Pegasus Mail ;SSL connections to GMX's servers ;Reason: there's some incompat between PMail 4.63 and SSL - 01/11/2013
[gmx-POP3-SSL] client = yes accept = 10995 connect = pop.gmx.net:995
[gmx-smtp-SSL] client = yes accept = 10465 connect = mail.gmx.net:465
[gmx-IMAP-SSL] client = yes accept = 10993 connect = imap.gmx.net:993
The issue at hand is that stunnel in not working properly now.
This is the log file for a successful connection to xsmail:
2013.12.14 17:15:08 LOG5[500:284]: Service [xsmail-POP3-SSL] accepted connection from 127.0.0.1:1182
2013.12.14 17:15:08 LOG5[500:284]: connect_blocking: connected 66.111.4.51:995
2013.12.14 17:15:08 LOG5[500:284]: Service [xsmail-POP3-SSL] connected remote server from 192.168.1.102:1183
2013.12.14 17:15:10 LOG5[500:284]: Connection closed: 58 byte(s) sent to SSL, 112 byte(s) sent to socket
And this is the log file for a (failed) connection to gmx:
2013.12.14 17:17:15 LOG5[500:452]: Service [xsmail-POP3-SSL] accepted connection from 127.0.0.1:1184
2013.12.14 17:17:15 LOG5[500:452]: connect_blocking: connected 66.111.4.52:995
2013.12.14 17:17:15 LOG5[500:452]: Service [xsmail-POP3-SSL] connected remote server from 192.168.1.102:1185
2013.12.14 17:17:21 LOG5[500:452]: Connection closed: 36 byte(s) sent to SSL, 126 byte(s) sent to socket
The PMail trace is this as follows:
[*] Connection established to 127.0.0.1
0016 +OK POP3 ready
<< 0015 USER 14067985
0005 +OK
<< 0015 PASS XXXXXXXX
0083 -ERR You must use your full username of the form
yourusername@domain.tld to login
Figures ... It is attempting to connect to gmx with xsmail credentials.
As youcan see, for some strange reason it is connecting to gmx with xsmail settings.
Must be a *.conf file problem but I am at a loss as to what is gong on Any ideas?
Thanks in advance,
CIV
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 9533100.818147 | SETI 16984998.016618 ABC 16504452.679097 | EINSTEIN 14605086.419852
On 14 Dec 2013 at 17:25, sawbona@flashmail.com wrote:
From: sawbona@flashmail.com Organization: Marx Brothers & Co. To: stunnel-users@stunnel.org Date sent: Sat, 14 Dec 2013 17:25:32 -0300 Priority: normal Subject: [stunnel-users] stunnel and Pegasus Mail Send reply to: sawbona@flashmail.com patches" <stunnel-users.stunnel.org>
Hello:
I recently came across stunnel as a solution (THE solution) to Pegasus Mail 4.63 having some sort of incompatibility with SSL versions in use at gmx.de and xsmail.com mail services.
Just an added note. You need to restart the stunnel after making changes to the conf file, since it loads the info at startup. That is why I have all the configurations I use in the file using different port settings, and just load it as part of the startup process.
I would assume you are using windows, so would have to use the task manager to end the task, and then restart it, or just restart the machine. I run Pegasus via wine on my linux machines, so use the linux version of stunnel with no problem.
+----------------------------------------------------------+ 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 9533100.818147 | SETI 16984998.016618 ABC 16504452.679097 | EINSTEIN 14605086.419852
-
Michael D. Setzer II -
sawbonaï¼ flashmail.com