hok Posted May 24, 2005 Share Posted May 24, 2005 I had been reporting most spam by forwarding spam as attachment to submit.x[at]spam.spamcop.net. Unfortunately, starting Sunday, May 22, 2005 3:03:40 p.m. Pacific Daylight-saving Time (-0700UTC) spam.spamcop.net no longer can be resolve to IP address. My primary DNS is 68.238.64.12, and secondary DNS is 68.238.96.12. It appears to me that I cannot change neither DNS server IP addresses as DHCP client is enable. As a result, I can no longer forward spam to SpamCop, please help! Link to comment Share on other sites More sharing options...
Farelf Posted May 24, 2005 Share Posted May 24, 2005 Sounds like a problem with your nameservers - http://www.dnsstuff.com/tools/mail.ch?doma...pam.spamcop.net resolves fine. Therefore a matter to resolve through your ISP's customer support (they may be able to allocate optional NS). Presume you should start from: http://www22.verizon.com/customerSupport/contactus/contacts/ If anyone has any better ideas, help out here, if you would. Of course Verizon currently has 8 IP addresses in the top 200 in the SCBL could have something to with it. Still a support matter if so. Good luck ... Link to comment Share on other sites More sharing options...
hok Posted May 24, 2005 Author Share Posted May 24, 2005 Sounds like a problem with your nameservers - http://www.dnsstuff.com/tools/mail.ch?doma...pam.spamcop.net resolves fine. In contrast, http://www.dnsstuff.com/tools/tracert.ch?ip=spam.spamcop.net got "Sorry, I could not determine the IP for spam.spamcop.net (error 11004)." Likewise for http://www.dnsstuff.com/tools/ping.ch?ip=spam.spamcop.net also got "Sorry, I could not determine the IP for spam.spamcop.net (error 11004)." :angry: Link to comment Share on other sites More sharing options...
Farelf Posted May 24, 2005 Share Posted May 24, 2005 In contrast, http://www.dnsstuff.com/tools/tracert.ch?ip=spam.spamcop.net got "Sorry, I could not determine the IP for spam.spamcop.net (error 11004)." Likewise for http://www.dnsstuff.com/tools/ping.ch?ip=spam.spamcop.net also got "Sorry, I could not determine the IP for spam.spamcop.net (error 11004)." :angry: 28426[/snapback] I'm embarrassed by the fact you probably know more about this stuff than do I, but I don't think that is the correct usage - try http://www.dnsstuff.com/tools/traversal.ch...op.net&type=ALL Link to comment Share on other sites More sharing options...
Jeff G. Posted May 24, 2005 Share Posted May 24, 2005 spam.spamcop.net does not have an A or CNAME Record because it is not a hostname, but a mail recipient subdomain. It authoritatively has the following MX Records per http://www.dnsstuff.com/tools/lookup.ch?na...cop.net&type=MX at present: DNS Lookup: spam.spamcop.net MX record Generated by www.DNSstuff.com How I am searching: Searching for spam.spamcop.net MX record at i.root-servers.net [192.36.148.17]: Got referral to A.GTLD-SERVERS.net. [took 7 ms] Searching for spam.spamcop.net MX record at A.GTLD-SERVERS.net. [192.5.6.30]: Got referral to asia3.akam.net. [took 10 ms] Searching for spam.spamcop.net MX record at asia3.akam.net. [63.241.73.214]: Reports vmx1.spamcop.net. [took 79 ms] Answer: Domain Type Class TTL Answer spam.spamcop.net. MX IN 3600 vmx1.spamcop.net. [Preference = 5] spam.spamcop.net. MX IN 3600 vmx2.spamcop.net. [Preference = 5] vmx1.spamcop.net. A IN 3600 64.74.133.248 vmx2.spamcop.net. A IN 3600 64.74.133.250 To see the DNS traversal, to make sure that all DNS servers are reporting the correct results, you can Click Here. Note that these results are obtained in real-time, meaning that these are not cached results. These results are what DNS resolvers all over the world will see right now (unless they have cached information). © Copyright 2000-2005 R. Scott Perry and clicking that last link http://www.dnsstuff.com/tools/traversal.ch...cop.net&type=MX shows the following at present:DNS Traversal for spam.spamcop.net. Generated by www.DNSstuff.com Getting NS record list at l.root-servers.net... Done! Looking up at the 13 net. parent servers: Server Response Time a.gtld-servers.net [192.5.6.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 107ms g.gtld-servers.net [192.42.93.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 107ms c.gtld-servers.net [192.26.92.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 108ms l.gtld-servers.net [192.41.162.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 108ms f.gtld-servers.net [192.35.51.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 108ms k.gtld-servers.net [192.52.178.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 108ms e.gtld-servers.net [192.12.94.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 108ms h.gtld-servers.net [192.54.112.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 217ms i.gtld-servers.net [192.43.172.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 217ms d.gtld-servers.net [192.31.80.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 217ms j.gtld-servers.net [192.48.79.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 217ms b.gtld-servers.net [192.33.14.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 326ms m.gtld-servers.net [192.55.83.30] asia3.akam.net. ns1-109.akam.net. ns1-11.akam.net. ns1-117.akam.net. ns1-73.akam.net. ns1-90.akam.net. ns1-93.akam.net. use1.akam.net. 326ms Status: Records all match. Looking up at the 8 spamcop.net. parent servers: Server Response Time ns1-109.akam.net [193.108.91.109] 5-vmx1.spamcop.net. 5-vmx2.spamcop.net. 5ms asia3.akam.net [63.241.73.214] 5-vmx1.spamcop.net. 5-vmx2.spamcop.net. 108ms ns1-11.akam.net [193.108.91.11] 5-vmx1.spamcop.net. 5-vmx2.spamcop.net. 108ms ns1-117.akam.net [193.108.91.117] 5-vmx1.spamcop.net. 5-vmx2.spamcop.net. 108ms ns1-73.akam.net [193.108.91.73] 5-vmx1.spamcop.net. 5-vmx2.spamcop.net. 108ms ns1-90.akam.net [193.108.91.90] 5-vmx1.spamcop.net. 5-vmx2.spamcop.net. 108ms ns1-93.akam.net [193.108.91.93] 5-vmx1.spamcop.net. 5-vmx2.spamcop.net. 108ms use1.akam.net [63.209.170.136] 5-vmx1.spamcop.net. 5-vmx2.spamcop.net. 108ms Status: Records all match. © Copyright 2000-2005 R. Scott Perry Link to comment Share on other sites More sharing options...
hok Posted May 24, 2005 Author Share Posted May 24, 2005 I have used 3 totally different mail servers to forward spam to SpamCop. 2 were web based e-mail, and one was SMTP run by myself. Except the SMTP server run by myself said “Mail Server for spam.spamcop.net could not be contacted at this time.”, “Mail Server for vmx1.spamcop.net could not be contacted at this time.” and “Mail Server for vmx2.spamcop.net could not be contacted at this time.” as I have also tried vmx1.spamcop.net and vmx2.spamcop.net as well, both web based e-mail services have not sent me “Message Delivery Delay” thus far. Mostly importantly, none of mail servers can get SpamCop to process my spam thus far as I have no spam waiting for me to confirm is indeed spam for reporting at all. :angry: Link to comment Share on other sites More sharing options...
DavidT Posted May 24, 2005 Share Posted May 24, 2005 I was able to do a command-line SMTP connection to vmx1.spamcop.net from a web hosting box in a server farm, but I can't test one from my broadband-connected PC because my provider doesn't allow direct SMTP connections in order to reduce spew from zombies, etc. The servers have been very busy for the last few days, and people are reporting delays in processing, so the stuff you're sending via conventional mail servers (the web-based one) might just be held up in processing. DT Link to comment Share on other sites More sharing options...
hok Posted May 24, 2005 Author Share Posted May 24, 2005 Following is the latest error message I got: Received: from vmx2.spamcop.net ([64.74.133.250]) by x with MailEnable ESMTP; Tue, 24 May 2005 08:04:23 -0700 Received: from unknown (0.0.0.0) by vmx2.spamcop.net with ; 24 May 2005 08:04:18 -0700 Date: 24 May 2005 08:04:18 -0700 To: x From: Mail Delivery System <MAILER-DAEMON[at]vmx2.spamcop.net> Subject: Delivery Status Notification (Failure) MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="11527509221353876.vmx2.spamcop.net" Precedence: bulk --11527509221353876.vmx2.spamcop.net content-type: text/plain The following message to <submit.x[at]vmx2.spamcop.net> was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 554-'Too many hops' --11527509221353876.vmx2.spamcop.net content-type: message/delivery-status Final-Recipient: rfc822;submit.x[at]vmx2.spamcop.net Action: failed Status: 5.0.0 (permanent failure) Diagnostic-Code: smtp; 5.1.0 - Unknown address error 554-'Too many hops' (delivery attempts: 0) Reporting-MTA: dns; vmx2.spamcop.net --11527509221353876.vmx2.spamcop.net content-type: message/rfc822 Received: from vmx2.spamcop.net (64.74.133.250) by vmx2.spamcop.net with ESMTP; 24 May 2005 08:04:18 -0700 Received: from vmx2.spamcop.net (64.74.133.250) by vmx2.spamcop.net with ESMTP; 24 May 2005 08:04:18 -0700 Received: from vmx2.spamcop.net (64.74.133.250) by vmx2.spamcop.net with ESMTP; 24 May 2005 08:04:18 -0700 <Wazoo snipped approximately 100 lines of duplicated code here> Received: from vmx2.spamcop.net (64.74.133.250) by vmx2.spamcop.net with ESMTP; 24 May 2005 08:04:16 -0700 Received: from vmx2.spamcop.net (64.74.133.250) by vmx2.spamcop.net with ESMTP; 24 May 2005 08:04:16 -0700 Received: from vmx2.spamcop. --11527509221353876.vmx2.spamcop.net-- Link to comment Share on other sites More sharing options...
Wazoo Posted May 24, 2005 Share Posted May 24, 2005 1. other users are submitting their spam via e-mail without this issue. 2. The "too many hops" is an interesting error, possibly due to the Akanai servers in the mix, but you shouldn't really be trying to send directly to the vmx servers anyway. 3. nslookup spamcop.net 68.238.64.12 *** can't find server name for address 68.238.64.12: Timed out *** Default servers are not available 4. nslookup spamcop.net 68.238.96.12 Server: nsdall01.verizon.net Address: 68.238.96.12 Non-Authoritative answer: Name: spamcop.net Addresses: 63.147.175.100, 63.147.175.118 I'd say you need to bitch at Verizon about their DNS issue. You say you can't change your DNS due to being DHCP ... this gets into configuring your browser which is not what this Forum section is about .. let me just say that you can use any DNS server you want (if that server allows 'public' access) .. depending on your operating system, you can even run your own Link to comment Share on other sites More sharing options...
hok Posted May 30, 2005 Author Share Posted May 30, 2005 I appreciate everyone’s response. From Sunday, May 22, 2005 afternoon to Tuesday, May 24, 2005 afternoon, for the two days whole period, all outgoing mail must go through outgoing.verizon.net. Otherwise, the recipient will not get the mail as it could not connect to remote servers. After Tuesday, May 24, 2005, everything went back to normal as before; it could connect all remote servers without going through outgoing.verizon.net. Again, thanks for everyone’s response! As to You say you can't change your DNS due to being DHCP ... this gets into configuring your browser which is not what this Forum section is about .. let me just say that you can use any DNS server you want (if that server allows 'public' access) .. depending on your operating system, you can even run your own 28490[/snapback] I was talking about DSL modem router Westell VersaLink 327W provided by Verizon. Link to comment Share on other sites More sharing options...
StevenUnderwood Posted May 30, 2005 Share Posted May 30, 2005 I appreciate everyone’s response. From Sunday, May 22, 2005 afternoon to Tuesday, May 24, 2005 afternoon, for the two days whole period, all outgoing mail must go through outgoing.verizon.net. Otherwise, the recipient will not get the mail as it could not connect to remote servers. After Tuesday, May 24, 2005, everything went back to normal as before; it could connect all remote servers without going through outgoing.verizon.net. Again, thanks for everyone’s response! 28679[/snapback] Thanks for the update. That configuration, by itself, should not have been a problem. There must have been a reason that messages were not getting through to spamcop. As toI was talking about DSL modem router Westell VersaLink 327W provided by Verizon. 28679[/snapback] And Wazoo was refering to your end machine, which does NOT need to use the default DNS settings provided by your DSL modem. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.