Jump to content

[Resolved] Cannot access webmail.spamcop.net


Recommended Posts

Hi Guys,

As of about 6 pm GMT+10 I have been blocked from pop3 and webmail access to my

spamcop account.

I am with the ISP Exetel, in Sydney Australia.

I cannot see any posts on system maintainance involving email outages.

I can access webmail from another ISP. My blackberry is getting mail from the account.

Help would be greatfully accepted.

Spamcop user for 5 years.

Ping results

C:\>ping webmail.spamcop.net

Pinging webmail.spamcop.net [216.154.195.51] with 32 bytes of data:

Reply from 66.35.174.102: TTL expired in transit.

Reply from 66.35.174.102: TTL expired in transit.

Reply from 66.35.174.102: TTL expired in transit.

Reply from 66.35.174.102: TTL expired in transit.

Ping statistics for 216.154.195.51:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Link to comment
Share on other sites

Hmmm - not a mail user but I'm seeing the same ping results from iinet.net.au in Perth - also the tracert results indicate a brick wall at 66.35.174.101 & 66.35.174.102:

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Steve>nslookup webmail.spamcop.net

...

Non-authoritative answer:

Name: webmail.spamcop.net

Address: 216.154.195.51

C:\Documents and Settings\Steve>ping webmail.spamcop.net

Pinging webmail.spamcop.net [216.154.195.51] with 32 bytes of data:

Reply from 66.35.174.102: TTL expired in transit.

Reply from 66.35.174.102: TTL expired in transit.

Reply from 66.35.174.102: TTL expired in transit.

Reply from 66.35.174.102: TTL expired in transit.

Ping statistics for 216.154.195.51:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Steve>tracert webmail.spamcop.net

Tracing route to webmail.spamcop.net [216.154.195.51]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ...

2 16 ms 16 ms 16 ms nexthop.wa.ii.net [203.59.14.16]

3 16 ms 16 ms 16 ms gi2-6.per-qv1-bdr2.ii.net [203.215.4.74]

4 73 ms 73 ms 72 ms gi0-15-1-0.syd-stl-core1.ii.net [203.215.20.64]

5 73 ms 74 ms 73 ms 202.139.19.37

6 229 ms 229 ms 229 ms 203.208.148.1

7 227 ms 228 ms 228 ms peer-01-ge-3-3-0-13.lsag.twtelecom.net [66.192.252.45]

8 288 ms 288 ms 289 ms 66.192.245.132

9 280 ms 280 ms 280 ms 66.162.21.234

10 284 ms 284 ms 284 ms pos3-0.suwangaeq00w.cr.deltacom.net [66.35.174.102]

11 284 ms 284 ms 283 ms pos5-0.atlngapk22w.cr.deltacom.net [66.35.174.101]

12 286 ms 285 ms 285 ms pos3-0.suwangaeq00w.cr.deltacom.net [66.35.174.102]

13 285 ms 285 ms 285 ms pos5-0.atlngapk22w.cr.deltacom.net [66.35.174.101]

14 287 ms 286 ms 287 ms pos3-0.suwangaeq00w.cr.deltacom.net [66.35.174.102]

15 287 ms 287 ms 287 ms pos5-0.atlngapk22w.cr.deltacom.net [66.35.174.101]

16 289 ms 288 ms 288 ms pos3-0.suwangaeq00w.cr.deltacom.net [66.35.174.102]

17 288 ms 288 ms 288 ms pos5-0.atlngapk22w.cr.deltacom.net [66.35.174.101]

18 290 ms 290 ms 290 ms pos3-0.suwangaeq00w.cr.deltacom.net [66.35.174.102]

19 290 ms 290 ms 290 ms pos5-0.atlngapk22w.cr.deltacom.net [66.35.174.101]

20 292 ms 292 ms 291 ms pos3-0.suwangaeq00w.cr.deltacom.net [66.35.174.102]

21 291 ms 292 ms 291 ms pos5-0.atlngapk22w.cr.deltacom.net [66.35.174.101]

22 293 ms 292 ms 294 ms pos3-0.suwangaeq00w.cr.deltacom.net [66.35.174.102]

23 292 ms 293 ms 292 ms pos5-0.atlngapk22w.cr.deltacom.net [66.35.174.101]

24 296 ms 294 ms 295 ms pos3-0.suwangaeq00w.cr.deltacom.net [66.35.174.102]

25 294 ms 294 ms 294 ms pos5-0.atlngapk22w.cr.deltacom.net [66.35.174.101]

26 296 ms 296 ms 295 ms pos3-0.suwangaeq00w.cr.deltacom.net [66.35.174.102]

27 295 ms 296 ms 295 ms pos5-0.atlngapk22w.cr.deltacom.net [66.35.174.101]

28 298 ms 297 ms 297 ms pos3-0.suwangaeq00w.cr.deltacom.net [66.35.174.102]

29 298 ms 297 ms 298 ms pos5-0.atlngapk22w.cr.deltacom.net [66.35.174.101]

30 299 ms 299 ms 299 ms pos3-0.suwangaeq00w.cr.deltacom.net [66.35.174.102]

Trace complete.

C:\Documents and Settings\Steve>

Dunno what that's all about - you should ask JT to take a look I think - support[at]spamcop.net

Link to comment
Share on other sites

Thanks Steve, glad to know I am sane, will write to support and hope for the best.
Y'r welcome - I just noticed a few whinges in the NGs along similar lines though it looks like no-one has contacted support yet - JT/Support should be at work in another few hours.
Link to comment
Share on other sites

Y'r welcome - I just noticed a few whinges in the NGs along similar lines though it looks like no-one has contacted support yet - JT/Support should be at work in another few hours.

Seems to be back up. I have access again to pop3 and webmail.spamcop.net.

Thanks all

P

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...