Pages: 1
RSS
The Bat Gmail error: SessionUnknownContentType ct (50)
 
Using The Bat 3.98.1 with Gmail, upon sending any e-mail, the following error is reported. NOTE: The email is always sent sucessfully, but this error is still reported:

TLS Protocol error: Unexpected message SessionUnknownContentType ct (50)

The settings I am using are:

smtp.gmail.com
Secure to Regular port (STARTTLS) Port 587

Perform SMTP Authenticaion: YES, using same username ans password as for mail retreval.

Require secure authentication: NO

Use POP before SMTP authentication: NO

Any ideas on why this error is reported?

Cheers
Joe
 
Hello,

I am using version 3.99.03 and have the same problem. Would anyone know what to do about it?

--
Lubos  
 
I get the same.
After sending a message TB sends a 'QUIT' command to the server to signal the end of the SMTP session.
TB expects a '221' signal from the server and gmail doesn't send that.
Hence the error.
__________________________________
I'm just a user of The Bat! I don't work for Ritlabs.
 
Quote
Roelof Otten writes:
I get the same.
After sending a message TB sends a 'QUIT' command to the server to signal the end of the SMTP session.
TB expects a '221' signal from the server and gmail doesn't send that.
Hence the error.

Forgive my poor Englisch ;-)
I've got the same problem, the mail is send normaly, so is it possible to turn off that 221 request from TB?

Greats Henk
 
No.
The problem is on the gmail side for not following the smtp protocol. The end of the smtp session needs to be negotiated properly according to the specs.
__________________________________
I'm just a user of The Bat! I don't work for Ritlabs.
 
If this problem still reproducible at your side?
 
I am afraid it is still reproducible. :-(
 
I'm getting the same thing too

Quote

!8/19/2007, 19:07:17: SEND  - TLS protocol error: Unexpected message SessionUnknownContentType ct (50).
 
Is there really nothing we can do about it? Is it a bug of Gmail or The Bat? I haven't got any response from Gmail and the Gmail Groups conferences also haven't found any solution yet...

Lubos
 
Now that Maxim (one of the developers) knows about it, we can only hope that it's going to be fixed.
__________________________________
I'm just a user of The Bat! I don't work for Ritlabs.
 
I think they should just check for the 221 condition and if they don't get it _and_ the server is gmail, just ignore it.

I have several emails in my gmail folder and I get the error message but the message is still in my Outbox. So I have no clue if it was sent our not.

This is really annoying and needs to be worked around because since I've only seen this problem on The Bat!, I don't think other email (Eudora, TB, MS Live Mail!, Pocomail) programs I've used with GMail (and which don't have this problem) don't have this problem at all.  
 
I don't get any error with Gmail using port 465 and "secure to dedicated port."
 
Hi,

last weekend I noticed that this error message disappeared. Gmail seems to have made a correction.

Lubos
 
I have same error while testing my SMTP-server based on exim. Using The Bat! 4.0.34:
The logs of The Bat!:
TLS Protocol error: Unexpected message SessionUnknownContentType ct (53)
The logs of exim:
SMTP protocol synchronization error (input sent without waiting for greeting): rejected connection from H=[MY-IP-ADDRESS] input="\026\003\001"

During testing, I discovered that I get the same error when connecting to same port with telnet and send any command before getting the greeting form server:
"220 MY-HOST-NAME ESMTP Exim 4.69 CURRENT-DATE-AND-TIME"

So, it seems, The Bat! should wait for a greeting (while exim makes a dns-requests). In fact, The Bat! do waits, but no longer than 5 or 6 seconds, and after that sends a command
Edited: Feathered Frog - 09 February 2009 13:54:38
 
Same problem in October, 2025. Switching to 465 port helps
Edited: Alex - 24 October 2025 00:05:04
 
Quote
Alex wrote:
Same problem in October, 2025. Switching to 465 port helps
I configured GMail on TB for the first time a year or two ago. IMAP, OAUTH, and from what I remember ports were configured automatically. I'm having no problems whatsoever. Port 465 is used, so that's the way to go.
Pages: 1