>> Mozilla T'Bird HELP Please - Dead In Water - Need Assist

[SWATNurse]

I transferred domain to HM; site is Live as of this morning. THEN:

Configured multiple Email accounts in HM per Cpanel. THEN:

Configured T'bird Client, and Email worked for 1 hour via T'bird. THEN:

T'bird will not receive, send except for the 1st hour. Settings reviewed ad nauseum....

ASSIST PLEASE...
THANKS.

[r2b2]

Are you receiving an error? If so, you'll need to provide this to give us an idea on what the issue may be.

Personally it sounds like your client may have been talking to the old domain host and then it switched after an hour and there is a problem with the configuration on your new account...

[SWATNurse]

See attached..

[r2b2]

What port are you trying to connect to SMTP with? 25 or 26 or something else? Make sure its 25 or 26, and also make sure that you don't have any firewall software that may be blocking the connection.

Failing that, its probably best to contact Hostmonster support to ensure that the SMTP server is running properly on the server which is hosting your domain....

[SWATNurse]

Yes, we're on port 26 per instructions. No firewall issues apparent. Per your suggestion, I'll ask HostM. about the SMTP server....

Thanks LOADS EVERYONE !!!

[shadmego]

You should be using port 25 for the SMTP connection. Hostmonster allows port 26 through for SMTP to provide a work around to ISPs that block port 25 traffic not going to their own servers.

Your ISP may also be blocking port 26, but you might have to ask them by contacting support for your ISP.

~regards

[lskeenan]

So the only ports that HM works with are 25 or 26? Comcast ISP has blocked 25, 26 doesn't seem to work either.

[r2b2]

25 is the standard port for SMTP and 26 is one that is often opened as well (to get around this kind of thing presumably). Best thing to do is contact your ISP to see if they can relax the restriction for you...

[Falcon1986]

One of the advantages of migrating your domain's mail handling to Google Apps is that you avoid these common port limitations altogether.

For POP3, port 995 is utilized for both the incoming and outgoing servers. For IMAP, on the other hand, ports 993 and 587 are used for incoming and outgoing respectively.

[shadmego]

One of the advantages of migrating your domain's mail handling to Google Apps is that you avoid these common port limitations altogether.

For POP3, port 995 is utilized for both the incoming and outgoing servers. For IMAP, on the other hand, ports 993 and 587 are used for incoming and outgoing respectively.

They must have changed the way they do things. I have two gmail accounts and they don't seem to be using all the same ports you are using ...

Port 995 is POP3s(ecure).
Port 993 is IMAPs(ecure).
Typically, Port 465 is SMTPs(ecure), which is what I'm using with my gmail accounts.
Port 587 is used in most cases as an alternative to Port 25, which is the common SMTP port. Port 587 is not typically used for secure communications for SMTP as far as I know. That is what 465 is for.

~regards

[Falcon1986]

Port 587 is not typically used for secure communications for SMTP as far as I know. That is what 465 is for.

~regards

I've been using TLS on port 587 for some time now (see Thunderbird setup instructions from Google (http://mail.google.com/support/bin/answer.py?answer=77662)). I believe port 465 still uses the SSL predecessor.

[shadmego]

Thanks for that link. Reading what you wrote sufficiently jogged my memory and now I remember reading that long ago ...

... must be getting old ...

~regards