Jump to content

jondoran

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jondoran

  • Rank
    Newbie
  1. I'm with you. I appreciate your mailing list, by the way. I have been too busy to participate, but I do try to read the messages. I have my university email forwarded to SpamCop (so that I only have one mailbox to monitor). Fortunately I can access some logged messages there. But I have too many important things going on these days to live without reliable email. I don't care if I have to pay more. It doesn't matter to me if CESmail reads these. I think of them as a way to vent that doesn't run the risk of jail time.
  2. jondoran

    Spamcop Webmail Down

    It seems like we just went through this. I'm rather busy these days, but I cannot afford to be without email. It looks like I'm going to need to spend time migrating off of SC. :angry:
  3. I would hope that Don would be able to call/page JT. I too would feel better if I knew that the folks on site were responding.
  4. I'm glad the forums are working, or I would be in the dark completely. Good hunting.
  5. Regarding this report: http://www.spamcop.net/sc?id=z924259737z3b...db10c6e7c3d0caz Repeating the relevant section Received: from unknown (192.168.1.103) by blade5.cesmail.net with QMQP; 20 Apr 2006 16:02:44 -0000 Received: from sccrmxc22.comcast.net (204.127.202.102) by mx53.cesmail.net with SMTP; 20 Apr 2006 16:02:44 -0000 Received: from pool-138-88-74-46.res.east.verizon.net ([138.88.74.46]) by sccrmxc22.comcast.net (sccrmxc22) with SMTP id <20060420160226s22000ejd2e>; Thu, 20 Apr 2006 16:02:37 +0000 This was mail I had forwarded from comcast.net to spamcop.net. Would it be correct to interpret this as a misconfigured comcast server? (I didn't think that 192.168 was routable, but it has been a while since I've worked in this area). If so, who would I contact at comcast to point this out? Edit: by the way... goodeatingg.com is reachable (some sort of diet spam). It resolves to 217.170.20.22 OrgName: RIPE Network Coordination Centre OrgID: RIPE Address: P.O. Box 10096 City: Amsterdam StateProv: PostalCode: 1001EB Country: NL ReferralServer: whois://whois.ripe.net:43 NetRange: 217.0.0.0 - 217.255.255.255 CIDR: 217.0.0.0/8 NetName: 217-RIPE NetHandle: NET-217-0-0-0-1 Parent: NetType: Allocated to RIPE NCC NameServer: NS-PRI.RIPE.NET NameServer: NS3.NIC.FR NameServer: SUNIC.SUNET.SE NameServer: NS-EXT.ISC.ORG NameServer: SEC1.APNIC.NET NameServer: SEC3.APNIC.NET NameServer: TINNIE.ARIN.NET Comment: These addresses have been further assigned to users in Comment: the RIPE NCC region. Contact information can be found in Comment: the RIPE database at http://www.ripe.net/whois RegDate: 2000-06-05 Updated: 2005-07-27 Somehow the automated link testing didn't catch this.
×