graphic e-mail attachments

yew · 27. Sep 2009, 09:50 AM

Using Thunderbird, the graphic e-mail attachments are rejected by the server with a message of "failure to connect". The same isp server accepts the attachment when I use the isp email service. The account settings are the same for the isp and Thunderbird. A trial with Hotmail and attachments is successful. What is the situation with Thunderbird? No add-ons to the Bird program presently.
Is Thunderbird made to send the attachments in the common extensions, jpg, bmp,?

MidnightCowboy · 27. Sep 2009, 04:10 PM

Are these attachments being "sent" individually or "forwarded" to others?
There is a difference in how Thunderbird sees these and if you Google the topic you will find lots of threads on this subject, one of which I'm sure will match your own circumstances.

It's possible that someone else here might have a better specific knowledge of how to overcome this other than by researching the threads I've mentioned yourself.

Jojoyee · 27. Sep 2009, 05:31 PM

Quote:

Originally Posted by yew

... with a message of "failure to connect"...

I send the image files using the mail client Thunderbird with no issue. "Failure to connect" when sending an email will be more likely related to the Outgoing Server (SMTP) settings.

If you're setting up a Gmail account, check if the server name is smtp.gmail.com in the outgoing server setting.

Other mail server settings are available here.

Hope this is of help.

yew · 27. Sep 2009, 07:12 PM

presently, am following up on replies. My attachments are self originated sends. The smtp setting is as specified by the isp and not secure socket required.

MidnightCowboy · 27. Sep 2009, 07:12 PM

As an afterthought, I know that some security apps can also interfere with this process. It shouldn't be a blocked port in your firewall if other stuff is getting out with Thunderbird, and usually it's only attachments coming in that trigger a response but it's another area you might like to check.

27. Sep 2009, 09:50 AM	#1 (permalink)
yew Junior Member Join Date: Sep 2009 Posts: 2	graphic e-mail attachments Using Thunderbird, the graphic e-mail attachments are rejected by the server with a message of "failure to connect". The same isp server accepts the attachment when I use the isp email service. The account settings are the same for the isp and Thunderbird. A trial with Hotmail and attachments is successful. What is the situation with Thunderbird? No add-ons to the Bird program presently. Is Thunderbird made to send the attachments in the common extensions, jpg, bmp,?

27. Sep 2009, 04:10 PM	#2 (permalink)
MidnightCowboy Site Manager Join Date: Aug 2008 Location: South American Banana Republic, third bunch from the left Posts: 8,812	Are these attachments being "sent" individually or "forwarded" to others? There is a difference in how Thunderbird sees these and if you Google the topic you will find lots of threads on this subject, one of which I'm sure will match your own circumstances. It's possible that someone else here might have a better specific knowledge of how to overcome this other than by researching the threads I've mentioned yourself. __________________ Knows nothing and cares even less

27. Sep 2009, 07:12 PM	#5 (permalink)
MidnightCowboy Site Manager Join Date: Aug 2008 Location: South American Banana Republic, third bunch from the left Posts: 8,812	As an afterthought, I know that some security apps can also interfere with this process. It shouldn't be a blocked port in your firewall if other stuff is getting out with Thunderbird, and usually it's only attachments coming in that trigger a response but it's another area you might like to check. __________________ Knows nothing and cares even less

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

27. Sep 2009, 07:12 PM	#4 (permalink)
yew Junior Member Join Date: Sep 2009 Posts: 2	presently, am following up on replies. My attachments are self originated sends. The smtp setting is as specified by the isp and not secure socket required.