domain/e-mail issue

[Land Locked]

Not sure if this is the right place for this question.

I have 2 domains hosted by the same company, one full hosting and one just e-mail. The full hosting works perfectly. The e-mail only doesn't let me reach the mail server.

Windows error: The connection to the server has failed. Account 'mail.mydomain.co.za',Server: 'mail.mydomain.co.za', Protocol: POP3, Port: 110, Secure(SSL): No, Socket Error: 10060, Error Number: 0x800CCC0E

Thunderbird on linux error: Connection to server mail.mydomain.co.za timed out

traceroute dies after about the 16 step where the other domain goes through.

I'm using i-burst wireless.

I get the idea that it may be a DNS issue.

Any help or ideas are welcome

Thanks

 

[PsyWulf]

From MS:
To troubleshoot this issue, follow these steps:

1. When you receive of the error messages that the "Symptoms" section of this article describes, make a note of the name of the server referenced in the error message.
2. Click Start, click Run, and then type TELNET servername, where servername is the name of your mail server.
3. Click OK. If you cannot connect to the server by using Telnet, there is a network connection problem to your mail server or to your Internet service provider (ISP). Contact your network administrator or ISP to help resolve the connection problem.
4. If Telnet is successful, click Start, point to All Programs, and then click Outlook Express.
5. Try to log on to Outlook Express with your Outlook 2000 mail account. If you cannot log on by using your Outlook 2000 account, the problem may be caused by a Winsock or MAPI issue. See contact information later in this article to contact Microsoft Product Support to help resolve the issue. If you can log on using your Outlook 2000 e-mail account, continue to Step 6.
6. Quit Outlook Express, and then start Outlook 2000.
7. To remove the existing account, click E-mail Accounts on the Tools menu.
8. Click View or change existing e-mail accounts, and then click Next.
9. Click to select the e-mail account, and then click Remove.
10. Click Finish to close the E-mail Accounts window.
11. On the File menu, click Import and Export..
12. Click to select the Import Internet Mail Account Settings check box, and then click Next.

Outlook finds and imports your account from Outlook Express.
13. Quit Outlook 2000, and then restart Outlook 2000.

Try to log on with your account. If you can log on and send and receive messages, this issue was caused by a corrupted account. If you still receive the error messages after you finish these steps, contact Microsoft Product Support to resolve the issue.

 

[RSkeens]

Have you tried using IMAP and also try setting it (POP3 or IMAP) to use SSL.

 

[Land Locked]

Many thanks. Thought I'd get stuck at item 3 and didn't really wanna reboot just to prove me right. Decided that I've spent enough time on it with my own ideas and did the reboot. Yep it got stuck at 3, so now it's time to get onto i-burst.

Thanks for the help.

 

[Land Locked]

Have you tried using IMAP and also try setting it (POP3 or IMAP) to use SSL.

Yes, tried that too. Starting to wish I'd never changed host's for this e-mail account.

 

[RSkeens]

As far as I know iBurst don't allow sending through external mail servers, you need to contact them to unblock it. I know of one client that couldn't and only after he had encrypted the connection did it pass through (he didn't feel like contacting them).

 

[Land Locked]

As far as I know iBurst don't allow sending through external mail servers, you need to contact them to unblock it. I know of one client that couldn't and only after he had encrypted the connection did it pass through (he didn't feel like contacting them).

iburst has blocked port 25 for sending, port 587 still works for sending as does 110 for receiving.

 

[RSkeens]

Well good luck getting it sorted, maybe the host's mail service is actually down. Be sure to post anything iBurst say so other users can be helped.

 

[Land Locked]

Thanks for the assist. I will certainly post the end result.

 

[RSkeens]

In the meantime you could also use a remote tool such as http://pingability.com/mailtest.jsp (If you feel unsafe just use any username and password. The authentication failed return will confirm if the mail service is running properly or not).

 

[Land Locked]

In the meantime you could also use a remote tool such as http://pingability.com/mailtest.jsp (If you feel unsafe just use any username and password. The authentication failed return will confirm if the mail service is running properly or not).

That is an AWESOME tool. Now I know for sure it's a network issue not a host issue.

Thanks.

 

[ramar]

I recently had a very similar problem with a client connecting to their e-mail server hosted in the states. They were connecting through iburst too. The mail server was fine but they were unable to connect to it through iburst. I eventually discovered that it was an international peering issue and it was also an issue on SAIX.
As a temp work around i setup a VPN between my clients and myself to route them through my IS account, which could connect fine to their server.
Although i go no joy from Iburst, fortunately the issue was resolved in 24 hours by someone...

 

[Land Locked]

48 Hours and counting. It does however seem that i-burps is trying, they've only had the issue on their plates for a few hours now.

 

[Land Locked]

The problem is now being escalated to an "upstream" provider.

 

[Land Locked]

The problem seems to be only with i-burst 41.xxx.xxx.xxx ip's, reconnected this morning until i got a 196.xxx.xxx.xxx ip and guess what? It now works to both domains.

Still waiting for them to sort it properly though, The 196. ip's are few n far between.

 

[Land Locked]

Feedback time.

i-burst was slower than molasses to come up with an answer. I will grant that they did escalate the problem several levels up and that the issue in terms of time was basically from the upstream providers trying to pass the buck.

Basically the issue was the e-mail host had the i-burst proxy blocked via IP tables for the one domain.(Why only the one I have no idea.) Once I was able to articulate the problem to the host it was fixed within 24 hours.

 

[RSkeens]

Good to hear, hope it stays that way.

 

[MidnightWizard]

E-Mail Ports

iburst has blocked port 25 for sending, port 587 still works for sending as does 110 for receiving.

I see you got your problem sorted

Protocol: POP3, Port: 110, Secure(SSL):

This bit has me confused surely POP 3 =110 & then SSL is a seperate port
or should we be talking about 995 ????


MW

 

[PsyWulf]

This bit has me confused surely POP 3 =110 & then SSL is a seperate port
or should we be talking about 995 ????
MW

Not necessarily,not everybody runs standards-based ports,our mail server runs in the port 500 range

 

[MidnightWizard]

Telnet

1. When you receive of the error messages that the "Symptoms" section of this article describes, make a note of the name of the server referenced in the error message.
2. Click Start, click Run, and then type TELNET servername, where servername is the name of your mail server.

It is always a good idea to state the MS KB # -- makes looking it up easier.

There is another better way to use TELNET

You can use Telnet from the command line and state a specific PORT NUMBER

You can then log in and view your mail on the server from the CLI

Look it up -- or do you want me to ????


MW