thawki1 Posted March 6, 2004 Share Posted March 6, 2004 My e-mail seems to be working ok now. Link to comment Share on other sites More sharing options...
Wazoo Posted March 6, 2004 Share Posted March 6, 2004 thanks for that feedback .. oddly enough, I just came from the newsgroups and there's someone over there complaining that he/she can't login tonight .... Link to comment Share on other sites More sharing options...
anthony55 Posted March 6, 2004 Share Posted March 6, 2004 Now if a few more of the folks with issues yesterday would check in again .. FTR, I'm still having problems (as of Saturday 6Mar 10:30 GMT). According to my POP session log, there have been a number of instances where a few lines of the mail header following a "RETR 1" were retrieved during the last 24 hours, but then the data flow just stops and my client eventually times out. I'm not at all convinced that this is necessarily SpamCop's problem but am at a loss to diagnose it any better from where I'm sat. Anthony Link to comment Share on other sites More sharing options...
Wazoo Posted March 6, 2004 Share Posted March 6, 2004 anthony55 .. is there a way for you to try setting up an IMAP account? On one hand, it may (or may not) help you handle your e-mail, but I believe that's on a different server, but the path between you and SpamCop ought to stay pretty much the same ... not sure if this would rule anything out or just add more to the mystery ... Based on JT's monitoring at the system, it doesn't seem to be a hard failure there, and again, the biggie is that so few folks seem to be affected ... Link to comment Share on other sites More sharing options...
anthony55 Posted March 6, 2004 Share Posted March 6, 2004 anthony55 .. is there a way for you to try setting up an IMAP account? [...] so few folks seem to be affected ... I'll try... good suggestion. The problem is that my employer completely blocks certain ports and I can't get to anything external using port 110, for example (port 995 for POP using TLS being an exception ;-) ). I'll experiment just as soon as the after effects of the local beer festival have dissipated... Anthony Link to comment Share on other sites More sharing options...
jmw1937@cqmail.net Posted March 6, 2004 Share Posted March 6, 2004 anthony55 .. is there a way for you to try setting up an IMAP account? [...] so few folks seem to be affected ... I'll try... good suggestion. The problem is that my employer completely blocks certain ports and I can't get to anything external using port 110, for example (port 995 for POP using TLS being an exception ;-) ). I've not been able to get e-mail since 0615 GMT, and when I try Traceroute, I see what appears to be an endless loop at my ISP: QUOTE Traceroute to: pop.spamcop.net IP address: [216.154.195.50] 1: [195.173.57.17] anchor-du-17.access.demon.net ( 183 ms) ! ( 170 ms) ! ( 187 ms) ! 2: [195.173.57.251] anchor-core-21-fxp3.router.demon.net ( 170 ms) ! ( 186 ms) ! ( 171 ms) ! 3: [158.152.0.185] anchor-border-1-4-0-2-3.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 171 ms) ! 4: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 5: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 6: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 187 ms) ! 7: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 8: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 9: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 170 ms) ! ( 186 ms) ! ( 171 ms) ! 10: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 11: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 311 ms) ! ( 202 ms) ! 12: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 13: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 280 ms) ! ( 201 ms) ! ( 202 ms) ! 14: [195.173.72.17] lon1-border-1-225.router.demon.net ( 170 ms) ! ( 169 ms) ! ( 171 ms) ! 15: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 296 ms) ! ( 201 ms) ! ( 202 ms) ! 16: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 17: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 169 ms) ! ( 170 ms) ! ( 171 ms) ! 18: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 19: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 171 ms) ! ( 186 ms) ! ( 171 ms) ! 20: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 21: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 22: [195.173.72.17] lon1-border-1-225.router.demon.net ( 170 ms) ! ( 186 ms) ! ( 160 ms) ! 23: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 171 ms) ! 24: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 25: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 171 ms) ! 26: [195.173.72.17] lon1-border-1-225.router.demon.net ( 170 ms) ! ( 170 ms) ! ( 171 ms) ! 27: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 28: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 29: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 170 ms) ! ( 183 ms) ! ( 171 ms) ! 30: [195.173.72.17] lon1-border-1-225.router.demon.net ( 186 ms) ! ( 169 ms) ! ( 171 ms) ! 31: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 171 ms) ! ( 170 ms) ! ( 171 ms) ! 32: [195.173.72.17] lon1-border-1-225.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 187 ms) ! 33: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 171 ms) ! ( 186 ms) ! ( 171 ms) ! 34: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 186 ms) ! ( 171 ms) ! 35: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 187 ms) ! 36: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 186 ms) ! ( 171 ms) ! 37: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 201 ms) ! ( 187 ms) ! 38: [195.173.72.17] lon1-border-1-225.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 187 ms) ! 39: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 170 ms) ! ( 185 ms) ! ( 171 ms) ! 40: [195.173.72.17] lon1-border-1-225.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 171 ms) ! 41: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 186 ms) ! ( 171 ms) ! 42: [195.173.72.17] lon1-border-1-225.router.demon.net ( 170 ms) ! ( 184 ms) ! ( 171 ms) ! 43: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 169 ms) ! ( 187 ms) ! 44: [195.173.72.17] lon1-border-1-225.router.demon.net ( 186 ms) ! ( 186 ms) ! ( 187 ms) ! 45: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 171 ms) ! 46: [195.173.72.17] lon1-border-1-225.router.demon.net ( 184 ms) ! ( 170 ms) ! ( 187 ms) ! 47: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 185 ms) ! ( 186 ms) ! ( 171 ms) ! 48: [195.173.72.17] lon1-border-1-225.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 187 ms) ! 49: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 171 ms) ! ( 186 ms) ! ( 170 ms) ! 50: [195.173.72.17] lon1-border-1-225.router.demon.net ( 170 ms) ! ( 186 ms) ! ( 171 ms) ! 51: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 185 ms) ! ( 187 ms) ! 52: [195.173.72.17] lon1-border-1-225.router.demon.net ( 171 ms) ! ( 186 ms) ! ( 186 ms) ! 53: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 169 ms) ! ( 186 ms) ! 54: [195.173.72.17] lon1-border-1-225.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 187 ms) ! 55: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 186 ms) ! ( 171 ms) ! 56: [195.173.72.17] lon1-border-1-225.router.demon.net ( 186 ms) ! ( 169 ms) ! ( 187 ms) ! 57: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 169 ms) ! ( 170 ms) ! ( 187 ms) ! 58: [195.173.72.17] lon1-border-1-225.router.demon.net ( 186 ms) ! ( 186 ms) ! ( 171 ms) ! 59: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 187 ms) ! 60: [195.173.72.17] lon1-border-1-225.router.demon.net ( 183 ms) ! ( 186 ms) ! ( 186 ms) ! 61: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 170 ms) ! ( 186 ms) ! ( 171 ms) ! 62: [195.173.72.17] lon1-border-1-225.router.demon.net ( 186 ms) ! ( 170 ms) ! ( 187 ms) ! 63: [195.173.72.18] anchor-border-1-4-0-2-225.router.demon.net ( 218 ms) ! ( 201 ms) ! ( 202 ms) ! 64: [195.173.72.17] lon1-border-1-225.router.demon.net ( 186 ms) ! ( 186 ms) ! ( 187 ms) ! Link to comment Share on other sites More sharing options...
Jeff G. Posted March 6, 2004 Share Posted March 6, 2004 cqmail.net,Mar 6 2004, 12:30 PM] I've not been able to get e-mail since 0615 GMT, and when I try Traceroute, I see what appears to be an endless loop at my ISP: QUOTE Traceroute to: pop.spamcop.net   IP address: [216.154.195.50]  1: [195.173.57.17]  anchor-du-17.access.demon.net    ( 183 ms) ! ( 170 ms) ! ( 187 ms) !  2: [195.173.57.251] anchor-core-21-fxp3.router.demon.net    ( 170 ms) ! ( 186 ms) ! ( 171 ms) !  3: [158.152.0.185]  anchor-border-1-4-0-2-3.router.demon.net    ( 186 ms) ! ( 170 ms) ! ( 171 ms) !  4: [195.173.72.17]  lon1-border-1-225.router.demon.net    ( 171 ms) ! ( 170 ms) ! ( 171 ms) !  5: [195.173.72.18]  anchor-border-1-4-0-2-225.router.demon.net    ( 171 ms) ! ( 170 ms) ! ( 171 ms) !  6: [195.173.72.17]  lon1-border-1-225.router.demon.net    ( 171 ms) ! ( 170 ms) ! ( 187 ms) ! 8< Please ask the tech support folks for Demon Internet and/or Thus plc about this issue. Thanks! Link to comment Share on other sites More sharing options...
dwc Posted March 6, 2004 Share Posted March 6, 2004 OK I had the same problem and spent 30 mins on the phone with Demon support. The problem is very intermittent, I don't think it is in either Demon or Spamcop, but somewhere in between. Here are 3 cases of traceroute, done within 10 mins of eachother, which Demon also have (hop 1 removed): 2 18 ms 17 ms 17 ms thus1-hg2.ilford.broadband.bt.net [217.32.64.73] 3 17 ms 18 ms 17 ms 217.32.64.34 4 21 ms 24 ms 21 ms 217.32.64.110 5 22 ms 23 ms 21 ms anchor-border-1-4-0-2-191.router.demon.net [212.240.162.126] 6 23 ms 21 ms 21 ms lon1-border-1-225.router.demon.net [195.173.72.7] 7 22 ms 23 ms 22 ms anchor-border-1-4-0-2-225.router.demon.net [195173.72.18] 8 23 ms 22 ms 22 ms lon1-border-1-225.router.demon.net [195.173.72.7] 9 22 ms 21 ms 23 ms anchor-border-1-4-0-2-225.router.demon.net [195173.72.18] 10 23 ms 22 ms 21 ms lon1-border-1-225.router.demon.net [195.173.72.7] *** loops in Demon 2 15 ms 15 ms 15 ms thus1-hg1.ilford.broadband.bt.net [217.32.64.72] 3 15 ms 15 ms 16 ms 217.32.64.34 4 20 ms 19 ms 19 ms 217.32.64.110 5 21 ms 20 ms 20 ms anchor-border-1-4-0-2-191.router.demon.net [212.240.162.126] 6 20 ms 20 ms 19 ms lon1-border-1-225.router.demon.net [195.173.72.17] 7 19 ms 21 ms 20 ms tele-border-1-g4-0-2-224.router.demon.net [195.173.72.14] 8 19 ms 19 ms 18 ms tele-border-4-228.router.demon.net [195.173.72.29] 9 432 ms 412 ms 379 ms tele-core-11-1-0-238.router.demon.net [194.159.176.113] 10 31 ms 32 ms 33 ms ams3-border-1-at-1-2-3-102.router.demon.net [194.217.238.254] 11 318 ms 397 ms 485 ms core01.ams01.atlas.cogentco.com [195.69.144.234] 12 111 ms 112 ms 112 ms p1-0.core01.ams02.atlas.cogentco.com [130.117.1.5] 13 114 ms 113 ms 114 ms p1-0.core01.lcy01.atlas.cogentco.com [130.117.1.1] 14 112 ms 113 ms 112 ms p13-0.core02.jfk02.atlas.cogentco.com [130.117.1.18] 15 23 ms 23 ms 21 ms anchor-border-1-4-0-2-225.router.demon.net [195.173.72.18] 16 22 ms 21 ms 24 ms lon1-border-1-225.router.demon.net [195.173.72.17] 17 23 ms 21 ms 22 ms anchor-border-1-4-0-2-225.router.demon.net [195.173.72.18] 18 23 ms 22 ms 22 ms lon1-border-1-225.router.demon.net [195.173.72.17] *** reaches Cogento and is outed back to Demon where it loops 2 15 ms 14 ms 16 ms thus1-hg1.ilford.broadband.bt.net [217.32.64.72] 3 16 ms 15 ms 15 ms 217.32.64.34 4 20 ms 21 ms 18 ms 217.32.64.110 5 20 ms 19 ms 19 ms anchor-border-1-4-0-2-191.router.demon.net [212.240.162.126] 6 18 ms 19 ms 20 ms lon1-border-1-225.router.demon.net [195.173.72.17] 7 21 ms 21 ms 22 ms tele-border-1-g4-0-2-224.router.demon.net [195.173.72.14] 8 18 ms 20 ms 19 ms tele-border-4-228.router.demon.net [195.173.72.29] 9 23 ms 21 ms 21 ms tele-core-11-1-0-238.router.demon.net [194.159.176.113] 10 40 ms 32 ms 38 ms ams3-border-1-at-1-2-3-102.router.demon.net [194.217.238.254] 11 124 ms 114 ms 113 ms core01.ams01.atlas.cogentco.com [195.69.144.234] 12 341 ms 398 ms 391 ms p1-0.core01.ams02.atlas.cogentco.com [130.117.1.5] 13 117 ms 115 ms 112 ms p1-0.core01.lcy01.atlas.cogentco.com [130.117.1.1] 14 113 ms 111 ms 111 ms p13-0.core02.jfk02.atlas.cogentco.com [130.117.1.18] 15 112 ms 112 ms 114 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.13] 16 113 ms 111 ms 112 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81] 17 124 ms 132 ms 123 ms p14-0.core01.atl01.atlas.cogentco.com [66.28.4.161] 18 124 ms 124 ms 124 ms g49.ba01.b000173-0.atl01.atlas.cogentco.com [66.28.5.242] 19 124 ms 125 ms 122 ms ITCDeltacomCommunications.demarc.cogentco.com [66.28.30.134] 20 123 ms 122 ms 124 ms 66.35.174.109 21 125 ms 128 ms 125 ms 66.35.174.106 22 126 ms 125 ms 127 ms suw02.gig6-0.edeltacom.com [66.35.174.154] 23 124 ms 126 ms 123 ms suwC1-gig3-5.edeltacom.com [216.154.207.13] 24 125 ms 125 ms 125 ms suwE1N-gig1-1-4.edeltacom.com [216.154.207.22] 25 128 ms 124 ms 127 ms webmail.spamcop.net [216.154.195.51] *** gets through I suspect there is a rogue route somewhere in Cogento ... but if you keep trying Traceroutes you will eventually see all 3 scenarios. Interestingly Demon couldn't reproduce it at their HQ. Link to comment Share on other sites More sharing options...
anthony55 Posted March 6, 2004 Share Posted March 6, 2004 is there a way for you to try setting up an IMAP account? I've had a quick play with IMAP (I confess to never having used IMAP before, so any comments I have on the subject may well be bogus). However, I seem to be getting a similar kind of result as with POP3. I took a guess and pointed my mail client at imap.spamcop.net for the test (which seems to have the same IP address as pop.spamcop.net). My mail client (Ritlabs' TheBat! v2.04.7) yields this knd of log: *** Session started : 06/03/2004 18:49:42, 18:49:42 S: * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN] Courier-IMAP ready. Copyright 1998-2003 Double Precision, Inc. See COPYING for distribution information. C: E00001 CAPABILITY S: * CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN S: E00001 OK CAPABILITY completed C: B00002 Login "xxxxxxxx[at]spamcop.net" "xxxxxxx" S: B00002 OK LOGIN Ok. C: N00003 LSUB "" "*" C: F00004 SELECT "INBOX" S: * LSUB (\Marked \HasNoChildren) "." "INBOX" S: N00003 OK LSUB completed S: * FLAGS (\Draft \Answered \Flagged \Deleted \Seen \Recent) S: * OK [PERMANENTFLAGS (\* \Draft \Answered \Flagged \Deleted \Seen)] Limited S: * 14 EXISTS S: * 0 RECENT S: * OK [uIDVALIDITY 1068319704] Ok S: F00004 OK [READ-WRITE] Ok C: U00005 FETCH 1:* (UID FLAGS) S: * 1 FETCH (UID 38 FLAGS (\Seen)) S: * 2 FETCH (UID 39 FLAGS ()) S: * 3 FETCH (UID 40 FLAGS ()) S: * 4 FETCH (UID 42 FLAGS ()) S: * 5 FETCH (UID 43 FLAGS (\Seen)) S: * 6 FETCH (UID 45 FLAGS ()) S: * 7 FETCH (UID 47 FLAGS ()) S: * 8 FETCH (UID 50 FLAGS ()) S: * 9 FETCH (UID 51 FLAGS ()) S: * 10 FETCH (UID 54 FLAGS ()) S: * 11 FETCH (UID 55 FLAGS ()) S: * 12 FETCH (UID 56 FLAGS ()) S: * 13 FETCH (UID 57 FLAGS ()) S: * 14 FETCH (UID 58 FLAGS ()) S: U00005 OK FETCH completed. C: U00006 UID FETCH 1:* (RFC822.SIZE ENVELOPE INTERNALDATE) C: A00007 NOOP S: !! Socket status: 10060 The "socket status 10060" is a winsock error (meaning timeout). Again, the connectivity clearly isn't completely broken. Things just seem to stop when an attempt to retrieve mail is made... Dunno if this adds any useful info! Anthony Link to comment Share on other sites More sharing options...
jefft Posted March 6, 2004 Share Posted March 6, 2004 anthony55 .. is there a way for you to try setting up an IMAP account? [...] so few folks seem to be affected ... I'll try... good suggestion. The problem is that my employer completely blocks certain ports and I can't get to anything external using port 110, for example (port 995 for POP using TLS being an exception ;-) ). I'll experiment just as soon as the after effects of the local beer festival have dissipated... Anthony Anthony, I'll be glad to work with you on this, but I suspect it's something in your email client or in the network between us and you. One thing you could try is to login to webmail at http://webmail.spamcop.net and look at the first few messages. If the RETR 1 is always failing, maybe there's some message first in your list that is totally confusing either the POP server or your mail client. If you can read it and delete it from the server, then try to POP and see if things run any better. JT Link to comment Share on other sites More sharing options...
Wazoo Posted March 7, 2004 Share Posted March 7, 2004 jmw1937[at]cqmail.net One item / router in common with your failed paths (and not existing in your successful path) is this; anchor-border-1-4-0-2-225.router.demon.net [195173.72.18] Interestingly Demon couldn't reproduce it at their HQ perhaps the techs are "on the other side" of this router. I'd say send the contents of that post to your demon techs and point this little tidbit out to them. (might want to verify the data, there's a missing period in one IP for example, I'm blaming a cut/paste thing) .. imagine that, the line I grabbed for my idenified example is one of those missing a period .. <g> Link to comment Share on other sites More sharing options...
Wazoo Posted March 7, 2004 Share Posted March 7, 2004 anthony55 The "socket status 10060" is a winsock error (meaning timeout Although the usual complaint is "not able to connect to anything", how about taking a look at http://mvps.org/winhelp2002/unwanted.htm .. especially scrolling down close to the bottom and checking out the links offered for "Repairing your Winsock Connection" not suggesting that yours is bad, just asking that you take a look and rule out this possibility .... Link to comment Share on other sites More sharing options...
anthony55 Posted March 7, 2004 Share Posted March 7, 2004 I'll be glad to work with you on this, but I suspect it's something in your email client or in the network between us and you. Thanks for the positive noises, Jeff. I'm entirely willing to believe that the problem does indeed lie somewhere between us. This is borne out by the fact that access to pop.spamcop.net appears to work fine for me using a computer with a direct ADSL connection rather than my main machine which routes via my employer's network. My problem is one of somehow trying to find out what and where that something is... As for my email client being at fault... well, I guess it could be. But I've tried, temporarily, setting up an account in Outlook Express and I get the same effect. One thing you could try is to login to webmail at http://webmail.spamcop.net and look at the first few messages. If the RETR 1 is always failing, maybe there's some message first in your list that is totally confusing either the POP server or your mail client. If you can read it and delete it from the server, then try to POP and see if things run any better. As it happens, using that reasoning, I've done exactly that a number of times now. I've deleted the first email in the list a number of times and I've also completely emptied my inbox (and trash, FWIW) and the problem reappeared when items entered my inbox. Although I don't want to waste your time or resources, would it be possible for you to log my POP accesses such that you can see what, if any, data the spamcop server is sending in response to a RETR 1 from me? Very occasionally I do seem to receive around 16 header lines from the first email and, once since this problem began, some complete emails. I'll raise the issue with my employer's sysadmins on Monday and see if they've made any configuration changes that are likely to have caused this, or if they're aware of anything untoward with the company's connection to the outside world. Thanks, Anthony Link to comment Share on other sites More sharing options...
dwc Posted March 7, 2004 Share Posted March 7, 2004 anchor-border-1-4-0-2-225.router.demon.net [195173.72.18] there's a missing period in one IP for example That would be my fault, cutting & pasting between XP DOS Window, mail clients and web clients did all sorts of nasty wrapping which I tried to fix to reduce the number of lines in the post! Still down today. Link to comment Share on other sites More sharing options...
chrism Posted March 7, 2004 Share Posted March 7, 2004 Another Demon customer here with a similar problem. In my case it's slightly different, in that I can download mail via POP3, but I can't get to the "webmail" web site. A "tracert" to "webmail.spamcop.net" gives: 2 30 ms 46 ms 31 ms 217.32.64.2 3 46 ms 46 ms 46 ms 217.32.64.110 4 46 ms 46 ms 46 ms anchor-border-1-4-0-2-191.router.demon.net [212.240.162.126] 5 46 ms 46 ms 46 ms lon1-border-1-225.router.demon.net [195.173.72.17] 6 46 ms 77 ms 46 ms anchor-border-1-4-0-2-225.router.demon.net [195.173.72.18] 7 46 ms 46 ms 46 ms lon1-border-1-225.router.demon.net [195.173.72.17] 8 46 ms 46 ms 46 ms anchor-border-1-4-0-2-225.router.demon.net [195.173.72.18] 9 46 ms 46 ms 46 ms lon1-border-1-225.router.demon.net [195.173.72.17] 10 46 ms 46 ms 46 ms anchor-border-1-4-0-2-225.router.demon.net [195.173.72.18] 11 46 ms 46 ms 46 ms lon1-border-1-225.router.demon.net [195.173.72.17] 12 46 ms 46 ms 46 ms anchor-border-1-4-0-2-225.router.demon.net [195.173.72.18] etc. etc. Is there any common factor here, I wonder? I'm on Demon ADSL pipe "anchor-r26a". Are you other chaps using ADSL, or dial-up? If you're using ADSL, which pipe? I've been onto Demon tech support about this, and they say they've passed it on to the engineers, but nothing will be done about it until Monday. Regards, Chris Link to comment Share on other sites More sharing options...
Wazoo Posted March 7, 2004 Share Posted March 7, 2004 The thing in common is the same router - (makes 3 of you so far) anchor-border-1-4-0-2-225.router.demon.net [195.173.72.18] I thought I'd heard good things about demon support, but .. wow, surely thay've got more folks complaining by now, and this shouldn't be quite that big of a deal to swap out a box ... but, I'm surely speaking out of turn .. It may be just like here, where the Tier one tech support has got all those complainers re-installing Windows and such .... Maybe if you get a few more folks involved to see if this router is getting in the way for them .. a few more notes with these details to demon support just might wake somebody up a bit quicker ..?? Link to comment Share on other sites More sharing options...
dwc Posted March 7, 2004 Share Posted March 7, 2004 I just spoke again to Demon, they acknowledge it is a problem in the r26a route but "unfortunately are not going to be able to fix it before Monday". Link to comment Share on other sites More sharing options...
anthony55 Posted March 7, 2004 Share Posted March 7, 2004 I'll be glad to work with you on this, but I suspect it's something in your email client or in the network between us and you. I've been doing some more experiments this morning and I've a nasty feeling that my company's NAT configuration might have gone bad. It looks like private IP addresses may be getting out beyond the local network. Jeff, to confirm this, it would be interesting to know if you've been getting connection attempts to pop.spamcop.net from IP addresses like 10.0.0.*. If that's the problem, the issue is definitely going to be for me to have resolved... and, if it is indeed the case, I'm astounded that any data ever got back to me... and I'll apologise for wasting everyone's time. On the off-chance that you have enough log data already, I tried a number of connection attempts around 13:21:07 GMT (Sun 7Mar)... and one email was successfully retrieved! I've stopped automated mail collection for the time being until I can talk to our sysadmin folk. Anthony Link to comment Share on other sites More sharing options...
Wazoo Posted March 7, 2004 Share Posted March 7, 2004 Glad you've got them agreeing finally that there is a problem, even better that they agree knowing where it is ... that time lag sucks though .. feel for ya .... thanks for the update. Link to comment Share on other sites More sharing options...
chrism Posted March 7, 2004 Share Posted March 7, 2004 Thank you very much for passing that on, dwc; it appears as though r26a is the "culprit" here! Would you let me know if you hear anything else from Demon about this, please, and obviously I'll do likewise. Regards, Chris Link to comment Share on other sites More sharing options...
chrism Posted March 8, 2004 Share Posted March 8, 2004 Just thought I'd report that Demon appear to have fixed the routing problem; I can now get through to the "webmail" site successfully. Regards, Chris Link to comment Share on other sites More sharing options...
anthony55 Posted March 9, 2004 Share Posted March 9, 2004 I've been doing some more experiments this morning and I've a nasty feeling that my company's NAT configuration might have gone bad. It looks like private IP addresses may be getting out beyond the local network. That, fortunately, turned out to be (almost) complete rubbish. However, to bring this thread to a conclusion following discussions with our local sysadmin folk, it seems that there was a "path MTU discovery" problem which has now been fixed. The phenomenon I was experiencing, of small chunks of data getting through but larger amounts of data just not making it, is apparently a well-known problem. It is nicely decribed in various places, including here: http://www.netheaven.com/pmtu.html Maybe that'll help someone in the future. Anyway, for now, I'm happy to report that it's working again... :-) Anthony Link to comment Share on other sites More sharing options...
Wazoo Posted March 9, 2004 Share Posted March 9, 2004 Yes, that is well known, but I just remember totally different symptoms the last time it was a big issue ... thinking it was a btinternet networking issues that was in the path of a large number of European users ... combination of their settings and the settings of a couple routers on the SpamCop side when they were being hosted on the east coast ... took a lot of effort on quite a few folks to sort that one out ... The catch was in your case, you were the only one complaining <g> but definitely glad it's sorted out .... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.