Jump to content

priruss

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About priruss

  • Rank
    Member
  1. priruss

    Yahoo Headers

    Thanks for the update, Don. I hope this gets resolved soon, and I'll continue to keep an eye on these pages in anticipation of that happy news.
  2. priruss

    Parsing error

    Today, I received occurrence number 12 of these "identified internal IP as source" spam emails that Spamcop cannot seem to trace without human intervention. WHILE I APPRECIATE SPAMCOP ADMIN'S CONTINUING AND ONGOING ASSISTANCE WITH THEM, I simply do not have the time or inclination to continue to submit these spam emails "back-channel", as doing so introduces an inordinate and unacceptable delay in correctly identifying their true source. Changing email providers is not a viable option for me at this point either. Spamcop is obviously vulnerable to being bamboozled by what appears to be an issue with flawed Yahoo! headers, and I therefore cannot continue to utilize Spamcop to parse spam I receive in my Yahoo! email until this issue is rectified. I will therefore use my own devices as best I can to trace the spam headers and submit reports to the originating ISPs. Or, failing in that and as appears much more likely, I will simply shut up and eat my spam. Good luck with fixing this, Spamcop. I really do like your service and hope you can one day rectify this situation.
  3. Note: Being posted in Announcements, there was no way for us "ordinary" users to weigh in on the topic at the place where it actually occurred, so I chose this venue to do so. Indeed, the item was the only pinned item that I saw that did not permit replies of any kind. If that was inappropriate of me, I will happily accept correction and will move or accept the movement of this discussion to wherever it IS appropriate. Executive Summary: In a nutshell, Wazoo's Announcement was a public spanking of a frustrated user who apparently used the PM functionality provided by Spamcop to contact other multiple users in a perhaps inappropriate attempt to get an answer to his or her question. The aforementioned user apparently had his or her PM privileges suspended for a couple of days as well. Full disclosure: I am not the publicly spanked user in question, nor do I know him or her from Adam or Eve. I do still have "reporting fuel" on the books and currently intend to acquire more as the need arises. Repeated readings of Wazoo's announcement left me asking several questions about how this matter was (or wasn't) handled: - Was an attempt made by Wazoo or anybody else to actually answer the user's question in that or any other venue? If so, a link to that attempt would have been usefully deployed in the Announcement. - Is there a stated and codified limit on the number of PMs that an individual user may send over (X) amount of time? Again, this is information that would have been useful in the Announcement. - The spanked user referenced his or her attempts to receive an answer to his or her question being thwarted by "smug" and apparently unhelpful replies by other Spamcop users. Did this actually occur? If so, is such behavior permitted, and were these users disciplined as well? Remembering back when I was a new user, I can confirm that the way that the FAQs and forum topics are laid out can be utterly baffling and really do constitute a "wall of text" that only the bravest and most determined have a prayer of navigating successfully. This is not as much criticism as it is an acknowledgement that the topic of spam itself is complicated and can be "a maze of twisty little passages, all alike".
  4. Just FYI, as of today (10/8), shift alt F no longer works in Yahoo! for forwarding spam. It now opens the File pulldown at the top of the screen instead. Haven't found the "new" sequence that will let you do it yet, but will update this if I do.
  5. I'm getting inundated by spam containing links pointing to IPs 157.231.100.50 and 157.231.100.51. The closest I can get a traceroute to get to these IPs is: TraceRoute from Network-Tools.com to 157.231.100.50 Hop (ms) (ms) (ms) IP Address Host name 1 24 0 0 206.123.64.46 - 2 0 0 0 64.124.196.225 xe-4-2-0.er2.dfw2.us.above.net 3 25 0 0 64.125.27.81 xe-0-1-0.cr2.dfw2.us.above.net 4 0 0 0 64.125.31.86 xe-0-2-0.er3.dfw2.us.above.net 5 0 0 0 64.124.193.221 64.124.193.221.t01263-01.above.net 6 1 1 1 198.154.100.146 switchport1.hostwindsdns.com 7 0 0 0 157.232.64.2 - 8 Timed out Timed out Timed out - 9 Timed out Timed out Timed out - 10 Timed out Timed out Timed out - 11 Timed out Timed out Timed out - Trace aborted. hostwindsdns.com is obviously an upstream DNS provider for these IPs. So why when I add abuse[at]hostwindsdns.com to my spam complaints is Spamcop not allowing them to be sent? I'll happily accept correction if hostwindsdns.com isn't involved, but please tell me why they would show up on the traceroute as an upstream if they're not. And, if they're not the DNS provider, then who is? Edit: Some tracking URLs for these turds: http://www.spamcop.net/sc?track=http%3A%2F...511b3cb62f75%2F http://www.spamcop.net/sc?track=http%3A%2F...8b3a98606593%2F http://www.spamcop.net/sc?track=http%3A%2F...SM3FMNTDMMLC%2F http://www.spamcop.net/sc?track=http%3A%2F...RWGM4DENDCG4%2F
  6. My feet are like wings/your wish is my command/et al. http://www.spamcop.net/sc?track=http%3A%2F...TCHAZTIMBVGU%2F 157.231.100.50 http://www.spamcop.net/sc?track=http%3A%2F...DQZRQMNRGCZQ%2F 157.231.100.50 http://www.spamcop.net/sc?track=http%3A%2F...CYZZGY2WCY3F%2F 157.231.100.51 http://www.spamcop.net/sc?track=http%3A%2F...KNJUGYYTGYRU%2F 157.231.100.51
  7. tippingthescalesinyourflavor.com myfastsaleclick.com ourpossibilitiesareendlesss.com everythinghereischeaper.com areyoureadyformassivesavings.com And many many more. spam complaints to these entities go to the titled email address and subsequently straight into the bit bucket. Is this a spam gang who just registered a bunch of dot coms with some poor schlub's email address?
  8. I've seen other discussions here that seem to indicate that this is a Yahoo! problem, not a Spamcop problem. They have said that Yahoo! is seeing this email as spam itself and not allowing it to be sent. I've run across several of these, and the only remedy I've found is manual copy-and-paste into the Spamcop interface. I await and will accept correction if I'm wrong about this.
  9. Noted, again. I'll just shut up and eat my spam.
  10. Noted, and noted the rationale for this. However, unlike almost every other Spamcop reporting breakout I've seen, no mention is made in the report that reports are being forwarded to abuse[at]ntu.edu.tw. Here's the breakout of the response I received: Tracking message source: 210.59.14.2: Routing details for 210.59.14.2 [refresh/show] Cached whois for 210.59.14.2 : tanetadm[at]moe.edu.tw Using best contacts tanetadm#moe.edu.tw[at]devnull.spamcop.net Message is 35 hours old 210.59.14.2 not listed in dnsbl.njabl.org ( 127.0.0.8 ) 210.59.14.2 not listed in dnsbl.njabl.org ( 127.0.0.9 ) 210.59.14.2 not listed in cbl.abuseat.org 210.59.14.2 not listed in dnsbl.sorbs.net 210.59.14.2 not listed in accredit.habeas.com 210.59.14.2 not listed in plus.bondedsender.org 210.59.14.2 not listed in iadb.isipp.com Finding links in message body Parsing text part no links found Reports regarding this spam have already been sent: Re: 210.59.14.2 (Administrator of network where email originates) Reportid: 4939297280 To: tanetadm#moe.edu.tw[at]devnull.spamcop.net If reported today, reports would be sent to: Re: 210.59.14.2 (Administrator of network where email originates) tanetadm#moe.edu.tw[at]devnull.spamcop.net Nowhere in the above report does it indicate that the report was forwarded to abuse[at]ntu.edu.tw. In other words, there is no way I could have known that the report was being forwarded to abuse[at]ntu.edu.tw if you hadn't told me here.
  11. Spamcop is still forwarding complaints to tanetadm[at]moe.edu.tw Submitted: Sunday, May 09, 2010 7:19:48 PM -0500: ATM Card Value is $1,000,000,00 Million USD * 4939297280 ( 210.59.14.2 ) To: tanetadm#moe.edu.tw[at]devnull.spamcop.net Apparently not enough spam coming from Taiwanese sources for Spamcop to bother fixing this, even after over a year?
  12. Thanks for the reply. Here are several tracking links for the Forona/Swift/Yipes spam. I had to let my mouse cool off because you only get 10 or so reports on each page, so I only went back a couple of weeks (but there are many more of these things, all within the IP ranges I mentioned in the OP). Today: http://www.spamcop.net/sc?id=z2219220239z4...e10106d570ba93z 67.159.193.66 http://www.spamcop.net/sc?id=z2219219557z8...e0ab6ad3226174z 67.159.193.119 September 1 http://www.spamcop.net/sc?id=z2205556976z0...292b89aba7b53fz 67.159.193.229 August 28 http://www.spamcop.net/sc?id=z2194538236zd...f82671c09d9255z 67.159.193.243 August 22 http://www.spamcop.net/sc?id=z2181187541z0...8e4308e43f3377z 67.159.203.150 August 16 http://www.spamcop.net/sc?id=z2159727747z4...be25e05bb4dee9z 67.159.193.228 I think you called it correctly that Forona/Swift/Yipes might be "snowshoe spamming" (rotating through the large number of IPs within their range) - there are a few exact IP number matches, but not that many. That information increases my pessimism that anything can be done about these unrepentant repeat spammers. I guess it IS just me, so shut up and eat your spam. Thanks again. Rant off.
  13. I have been getting hammered with spam, as many as 20 per day, from the 67.159.193.* and 74.55.187.* netblocks for the past 90 days. These blocks belong to Forona Technologies, Swiftco, and are downstream from Yipes. I carefully report each and every one via Spamcop, but these netblocks never seem to end up on any kind of blocklist and the spam continues to flow. Am I spinning my wheels by reporting these netblocks? Are they protected or special somehow? Spamcop assures me that LARTs are being dispatched to abuse[at]yipes.com (forona's and swift's contact email addresses bounce). Is Spamcop simply dev nulling these reports? What can I do to put these spam complaints into the hands of somebody who can actually do something about the Forona/Swift/Yipes spam? Thanks for letting me rant.
×