Problem getting domain emails in Thunderbird
I'm trying to help someone with using Thunderbird to get emails from a website (online form).
I added the account into my Thunderbird (Ubunto 8.10) and it works fine. Using the exact same settings - username, account name etc - it just wont work on the Mac Thunderbird.
I was just wondering if anyone (probably with an Apple Mac) knows of a certain issue with domain email in Mac's?
Like changing the account name from [email protected] to whoever+domain.com (which incidentally I've tried).
On the Mac it did receive an email once, but wouldn't send them. then without changing any settings it then wouldn't receive them either, and still wont.
Errors:
Sending of message failed. The message could not be sent because connecting to SM
TP server mail.domain.com failed
Any ideas, tips, things to test or try?
pr0gr4mm3r posted this at 09:35 — 24th April 2009.
He has: 1,502 posts
Joined: Sep 2006
What kind of connection does this computer have? That would be another difference from your computer.
greg posted this at 09:44 — 24th April 2009.
He has: 1,581 posts
Joined: Nov 2005
Yeah that is something to consider.
There was a few occasions when apparently the loading bars were going for a long time, instead of an error or failure of incorrect login poping up in a few seconds.
pr0gr4mm3r posted this at 11:07 — 24th April 2009.
He has: 1,502 posts
Joined: Sep 2006
I can't send email out to my SMTP server on the standard port 25, and my ISP is to blame. Try a telnet connection to make sure nothing is blocked. If it is, try an SSL port or see if you can get it changed on the server.
I connect to a server that requires my full email address to log in as well, and I don't have any problems with it. I use the '@' and not the '+'.
greg posted this at 21:19 — 24th April 2009.
He has: 1,581 posts
Joined: Nov 2005
Nice one, you were spot on (unfortunately).
They are with AT&T, and like your findings with Comcast, they block port 25 too.
"In an attempt to control unsolicited email (spam)"
That's plain stupidity. Removing a vital part of a system simply to stop bad things. It's like banning cars simply because there are road traffic accidents.
I cannot believe they do it.
Anyway, they suggested using port 465 with SSL. I haven't had chance to get them to test that yet, but it isn't really a direct alternative.
We have these systems designed, developed and put in place to allow our usages, like port 25 as default for outgoing emails, then a "clever" ISP just blocks it.
Why not just block the entire internet, then their clients wont get any spam, viruses or other problems with the service.
Cheers pr0gr4mm3r. At least I know what the problem is to look for a resolve now.
pr0gr4mm3r posted this at 22:04 — 24th April 2009.
He has: 1,502 posts
Joined: Sep 2006
I agree that it is an unwise move as well. Why can't I send out spam on port 465?
greg posted this at 00:00 — 25th April 2009.
He has: 1,581 posts
Joined: Nov 2005
Yup.
Anyway, using port 465 worked fine if anyone else has a similar issue try it.
The mail server handling the SMTP will need a certificate for SSL, but of course should have one anyway.
Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.