Glacial email server response

Gentlemen:

I'm experiencing extremely slow email server reponse and transfer rates. This is not the first time this has happened recently. It's particularly irritating because I just tried to file a support ticket, only to find out I need to get authenticated... vai email, and guess what? Assuming the authentication message IS there, I can't download it.

Little help?

 

The ticket was created and the response was 'We had a problem but it has now been fixed'.

And now again, one day later, a 20KB email message takes over 2 minutes to download. I imagine I'll get the same 'We had a problem but it's now fixed' response once again.

The mail service has been very unstable for weeks. I guess I'll just create a new ticket every day, notifying DASP of the trouble, and then they'll fix it, for the remainder of that day.

Hardly satisfactory.

 

I too have experienced at least 6 different occassions in the past year where where email ceased to function for anywhere from a few minutes to hours. The recent incident where a backbone went down is certainly understandable, but repeated occasions for "glacial" or non-existent email service has me looking around for another host.

I have a technical firm and we exchange 1-5MB files regularly with architects and engineers. Today it took me over 20 minutes to download a 514kb (thats KB) file. WHY was firewall service scheduled for BUSINESS HOURS? NOT very user service minded!

I have voted every year for ASP.net as the top host, but I can tell you that if there is not some acknoweledgement ontheir part they are going to re-evaluate their uptime performance and provide better service - I WILL BE LEAVING!

Michael Hemmer
[email protected]

 

I have not done a traceroute. Good suggestion. I will do so the next time the problems occurs and post the route.

 

my email is laboriously slow almost everyday for the last week. I'm using Outlook 2003. What is a "traceroute?"

 

Hello Forum Administrator

I just recieved a notice of the post by "imfrgvn" when lo and behold my own email service slowed to a crawl.

Below is the tracerouteI ran immediately (OS is WinXP SP3 with all updates):

Tracing route to mail.fmhls.com [67.63.55.3]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 9 ms 8 ms 10.32.192.1
3 8 ms 10 ms 7 ms opti38-161.nassau.cv.net [167.206.38.161]
4 * * * Request timed out.
5 10 ms 12 ms 9 ms rtr4-tg11-2.wan.hcvlny.cv.net [64.15.4.25]
6 * * * Request timed out.
7 * * * Request timed out.
8 20 ms 18 ms 27 ms ashbbrc01gew020300.r2.as.cox.net [68.105.30.73]
9 19 ms 35 ms 24 ms ip70-167-150-62.at.at.cox.net [70.167.150.62]
10 21 ms 20 ms 19 ms border2.pc1-bbnet1.wdc002.pnap.net [216.52.127.1
9]
11 21 ms 20 ms 21 ms infospaceinc-3.border2.wdc002.pnap.net [64.94.31
.142]
12 23 ms 25 ms 23 ms 67.63.55.3
Trace complete.

Does this help explain the "glacial performance"?

 

I've also notice pretty damned slow access -SMTP andIMAP anyway, I'm not using POP- and sometimes access just quits altogether. My other SMTP/IMAPsetups with other providers (gmail, work, etc.) are flawless. Look here -> http://community.discountasp.net/default.aspx?f=31. There's always some kind of problem with one server or another.

I think they just don't realize there's a problem. Usually DASP is very good about keeping the customers in the loop about things. They're not the types to just lie about it, so it must be that they just don't believe there's an issue.

So, I suggest that each and every time any of us encounters slower than usual e-mail response or the servers just stop responding, open a ticket. Maybe once they see a ton of tickets being opened up, they'll realize that the problem does exist and look for ways to fix it.

 

Excellent suggestion Jamie - Will do and by the way I think you are probably right that they are unaware of the problem because we don't take time to make an issue unless the service deteriorates badly or does not function for some significant time.