Thunderbird unable to send email attachements

Forums › Desktop computing › Thunderbird unable to send email attachements

veryshort

81 posts

Master Geek

#254405 10-Aug-2019 21:36

Hi Guys ,

For the last couple of weeks I have been unable to send any email with an attachement via thunderbird . The error I'm getting is "the smtp server has timmed out . I'm running Thunderbird 60.8, a fresh win 10 home install .

I can send a normal email but just nothing with an attachment { the above error occures} I have tried the Win 10 email app and the same problem , I have an ISP { 2degrees } supplied fritz box running 7.12 firmware .I can send an email with an attachment from 2degrees web based mail but not my home desktop . I have pinged my snap smtp server and I get request timmed out . I'm now at a complete loss as to why this is happening , 2degrees say its not their end and I'm a little confused as with a fresh install of the os and a correctly configured thunderbird to send and receive I still cant send attachments via my email client . Any help would be great please .

Cheers

Andrew W

1101

3141 posts

Uber Geek
+1 received by user: 1143

#2294550 12-Aug-2019 09:50

What size attachment "
What type of attachment ? zip, doc, exe

Disable any firewall , as a test

As a test
try using gmail or smtp2go as smtp in Tbird & see if that works

Try changing smtp port settings

Outgoing Mail Server (SMTP): smtp.snap.net.nz

Outgoing Mail Server Port (SMTPS): 465 (preferred) or 587 and requires authentication

Quinny

926 posts

Ultimate Geek
+1 received by user: 208

Trusted

#2294740 12-Aug-2019 12:40

I have had issues with Nod32 and Thunderbird and sending mail. Agree - Look at your Windows Defender and any other firewall to see what blocking what. For me disabling SSL/TLS fixed the send issue and then updating definition profile to beta and reenabling.

Finally fixed after much hair-pulling. Broke it trying to fix Chromecast issues under Windows 10 on 1 pc (reset all my firewall settings, chrome flags, routers you name it) only to later find out was a Nod32 and Chromecast issue now fixed in a new profile (disabling firewall did not fix).