Sunday, June 5, 2016, 6:04:23 AM, Harald wrote: >> On 6/4/2016 Harald Faber wrote:
HF>>> This situation is not amusing. Is Ritlabs informed about this issue in HF>>> the meantime? >> Notice my version of TB... I have had this problem intermittently >> starting in version 4 of TB. In my most recent experience before I moved >> my domain to a VPS only my sub-domains worked. My primary domain did not >> work. Moving my domain to a VPS fixed the SMTP problem. How can this be >> a Ritlabs problem??? HF> If it works with Thunderbird and does not work with TheBat - what could HF> be the reason? The Hoster? Don't think so. HF> Is there anybody out there not having this problem? With which TheBat HF> Version? HF> TBH I am not willing to bite that dust and blame my Email provider when HF> other Email clients have no problem. Especially with a commercial product. There are a number of things that can go wrong, and it's typically a problem with the hosting provider. I don't recall you saying you had upgraded TB! or changed any settings, in fact, you said "starting Tuesday evening, for no apparent reason, I cannot SEND mail from the accounts with the private domains" so that tells me something changed somewhere else. Ocassionally, I do have issues with my provider, either because they're having system issues (hardware issues, a patch that went bad, problem with their network connection, etc.) or they changed settings on their systems such that the way I've been sending and receiving email no longer works. The former they will usually communicate through their status site or in the support section, the latter I usually just have to work out on my own (though I could probably contact support if needed). So yes, things can suddenly stop working, but it's rarely a problem with a client, particularly if nothing changed about the client. I don't know how 1&1 works, so I'll use my own hosting provider as an example. When it comes to sending and receiving mail, I can do it through an address like: mail.somehost.com for both SMTP and POP3. Because this is shared hosting, I can also go to my exact server, myserver.mail.somehost.com and that seems to make things work a little more smoothly when it comes to secure connections. Protocols and ports: -Send mail- Connection: "Secure to dedicated port (TLS)" Port: 465 Authentication: "Perform SMTP Authentication", "Same user/password as for Mail Retrieval" -Receive mail- Username: (I provide) Password: (I provide) Connection: "Secure to dedicated port (TLS)" Port: 995 Authentication: "Regular" When I send a message, it looks like this(blocking out some information): 6/5/2016, 12:10:24: SEND - sending mail message(s) - 1 message(s) in queue 6/5/2016, 12:10:24: SEND - Connecting to SMTP server xxx.mail.xxx.com on port 465 6/5/2016, 12:10:24: SEND - Initiating TLS handshake >6/5/2016, 12:10:25: SEND - Certificate S/N: 0950C56EAE11C0D923512B87F3C96DFC, >algorithm: RSA (4096 bits), issued from 1/25/2012 to 1/24/2017 11:59:59 PM, >for 2 host(s): *.mail.xxx.com, mail.xxx.com. >6/5/2016, 12:10:25: SEND - Owner: "US", "92821", "California", "xxx", "xxx >Rd", "xxx Web Hosting", "admins", "Provided by xxx Network, LLC", "xxx Premium >Wildcard SSL", "*.mail.xxx.com". >6/5/2016, 12:10:25: SEND - Issuer: "US", "XXX CERTIFICATION AUTHORITY", "XXX >SSL CA". Valid from 3/4/2009 to 5/30/2020 10:48:38 AM. >6/5/2016, 12:10:25: SEND - Root: "US", "UT", "Salt Lake City", "The USERTRUST >Network", "http://www.usertrust.com";, "UTN-USERFirst-Hardware". Valid from >7/9/1999 6:10:42 PM to 7/9/2019 6:19:22 PM. 6/5/2016, 12:10:25: SEND - TLS handshake complete 6/5/2016, 12:10:25: SEND - connected to SMTP server 6/5/2016, 12:10:25: SEND - authenticating (login)... 6/5/2016, 12:10:25: SEND - sending message to x...@gmail.com <6/5/2016, 12:10:25: SEND - message to x...@gmail.com sent (425 bytes) 6/5/2016, 12:10:26: SEND - connection finished - 1 message(s) sent So you should see information on the secure connection and just check to make sure all the certificates are valid. I'm not saying this will work for you, it's going to depend on what your provider's systems accept, but there are other options and if their support can't seem to help, then you might just have to play with a lot of different settings to find a working combination. Be sure to check the log when testing any changes, while not as detailed as I'd like, it should give you a general idea where the connection is failing. Good luck! -Sam ________________________________________________ Current version is 7.1 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
