Marshallsoft & Gmail

[bwolfsohn]

We've successfully used marshallsoft to send emails through gmail for years now... All of a sudden, emails sent to gmail are failing. This is happening in our current software version (xbase++2.0) as well as last year's version (xbase++1.9).

We've gotten reports from 2 different clients as can see the problem in our offices.

Is anyone else having any problems ??? This just started in the past day or so (as far as we can tell)..

*************************
Here is a failed mail log:
*************************
*** seeIntegerParam(0,8,2)
*** seeIntegerParam(0,8,4)
*** seeSetProxySSL(0,1,'C:\CUS12\stunnel\','stunnel.pem','stunnel.exe')
*** seeSmtpConnectSSL(0,8801,465,'smtp.gmail.com','gmailaddresshere@gmail.com','*','<gmailaddresshere@gmail.com>','',''
*** seeStringParam(0,58,gmailaddresshere@gmail.com)
*** seeStringParam(0,57,*)
*** seeIntegerParam(0,29,1)
*** StartStunnel(0,'Smtp')
C:\CUS12\stunnel\stunnel.exe C:\CUS12\stunnel\SmtpConfig(0).txt
CreateProcess 0: pid=2108 thr=2104
Stunnel started (chan 0, process 0)
Connecting...
<200:600923791>
VS Win32 Version 1.3.8 Build 1
SEE Win32 Version 7.1.0 Build 2
CUS Business Systems
CID=5200
<101:600923791>
vs: LogHandle = 2068
vSock 0 created (IP 0)
<102:600923791>
LocalHost = 'Atlantic'
<104:600923791>
Server = 'ATLANTIC'
ServerIP = 192.168.0.17
<105:600923885>
vsConnect(0,'ATLANTIC',8801) attempt 1
Socket=2124, RemoteIP=c0a80011, RemotePort=8801
connect(2124) returns 0
Server has accepted the connection
<106:600924493>
<201:600924524>
recv(0)=-1
<202:600924774>
ERROR(600929376): SockCode=-1 SeeCode=-52 PrevState=201 ThisState=202 NextState=202
vSock write error.
vSock write error.vSock has been closed.
vSock has been closed.vSock write error.
*** seeRelease: Win32 5200 7.1.0 (2) ***
KillStunnel(0) pid=0
TerminateProcess 0: pid=2108 thr=2104
Stunnel killed (chan 0, process 0)
vSocket: 0 closed
*** Releasing channel 0 ***



*************************
Here is a successful mail log:
*************************
*************************
*** seeIntegerParam(0,8,2)
*** seeIntegerParam(0,8,4)
*** seeSetProxySSL(0,1,'C:\CUS11\stunnel\','stunnel.pem','stunnel.exe')
*** seeSmtpConnectSSL(0,8801,465,'smtp.gmail.com','smallcents2@gmail.com','*','<smallcents2@gmail.com>','',''
*** seeStringParam(0,58,smallcents2@gmail.com)
*** seeStringParam(0,57,*)
*** seeIntegerParam(0,29,1)
*** StartStunnel(0,'Smtp')

C:\CUS11\stunnel\stunnel.exe C:\CUS11\stunnel\SmtpConfig(0).txt
CreateProcess 0: pid=1928 thr=1924

Stunnel started (chan 0, process 0)
Connecting...
<200:350736813>
VS Win32 Version 1.3.8 Build 1
SEE Win32 Version 7.1.0 Build 2
CUS Business Systems
CID=5200
<101:350736813>
vs: LogHandle = 1920
vSock 0 created (IP 0)
<102:350736813>
LocalHost = 'Atlantic'
<104:350736813>
Server = 'ATLANTIC'
ServerIP = 192.168.0.17
<105:350736907>
vsConnect(0,'ATLANTIC',8801) attempt 1
Socket=1948, RemoteIP=c0a80011, RemotePort=8801
connect(1948) returns 0
Server has accepted the connection
<106:350737515>
<201:350737547>
recv(0)=55
R: 220 smtp.gmail.com ESMTP e188sm18986571ywc.42 - gsmtp
<202:350737921>
S: EHLO gmail.com
<203:350738171>
recv(0)=211
R: 250-smtp.gmail.com at your service, [98.249.237.219]
R: 250-SIZE 35882577
R: 250-8BITMIME
R: 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN XOAUTH
R: 250-ENHANCEDSTATUSCODES
R: 250-PIPELINING
R: 250-CHUNKING
R: 250 SMTPUTF8
<160:350738171>
S: AUTH LOGIN
<162:350738436>
recv(0)=18
R: 334 VXNlcm5hbWU6
S: c21hbGxjZW50czJAZ21haWwuY29t
<163:350738467>
recv(0)=18
R: 334 UGFzc3dvcmQ6
S: ****************
<164:350738701>
recv(0)=555
R: 534-5.7.14 <https://accounts.google.com/ContinueSig ... =AKgnsbtcf
ERROR(350738701): SockCode=0 SeeCode=-49 PrevState=163 ThisState=164 NextState=164
SMTP returned error. 534-5.7.14 <https://accounts.google.com/ContinueSig ... =AKgnsbtcf

SMTP returned error. 534-5.7.14 <https://accounts.google.com/ContinueSig ... =AKgnsbtcf
SMTP returned error. 534-5.7.14 <https://accounts.google.com/ContinueSig ... =AKgnsbtcf

*** seeRelease: Win32 5200 7.1.0 (2) ***
KillStunnel(0) pid=0
TerminateProcess 0: pid=1928 thr=1924
Stunnel killed (chan 0, process 0)
vSocket: 0 closed
*** Releasing channel 0 ***

[rdonnay]

Stunnel is a complicated process for sending out emails.

That's one of the things I didn't like about the Marshallsoft SSL solution.

I like the Xbase++ 2.0 asinet solution because it is much simpler and doesn't require OpenSSL.
It uses the built in SSL in Windows sockets.

You could try using Alaska's smtp class in your 2.0 version to see if the problem goes away, then you will know that it's an Stunnel problem.
I send out emails via Gmail every day, so does Bobby Drakos app. They all go via port 465. I haven't heard of any problems.

[bwolfsohn]

Everything worked fine until a day or 2 ago... I don't think it's a windows update... it's working elsewhere... so i'm hoping gmail either changed something or the servers are having a bad day...