Jump to content

fliptop

Members
  • Posts

    42
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    West Virginia
  • Interests
    a chemical engineer, who's a computer geek, who can rebuild a carburetor

fliptop's Achievements

Member

Member (2/6)

0

Reputation

  1. Since I last posted I've submitted a few spam messages for processing and the issue seems to have been resolved.
  2. OK, I restarted my browser, and after logging into the members area a basic authen window popped up. After logging in, I checked and there were no cookies set in my browser. Only when I navigate to the forum did the cookies start appearing. If the problem persists I'll report back later today.
  3. Maybe, I tried restarting my browser and I have it configured to delete cookies upon closing but I'll try it again...
  4. Hi all - for the past day or so I've been receiving multiple httpd basic authentication requests whenever I submit a spam message. AFAIK basic authen is supposed to remain "logged in" until all instances of the browser window are closed. In my case I'm not closing the browser, just submitting spam as always. Anyone else having this same issue?
  5. How likely is it that google will be giving back their IPs? Since their alert emails are being /dev/null'd, they should be forced to go through some kind of procedure to get their offending IPs delisted. Just my $0.02.
  6. Howdy all - some time ago I posted regarding how spam from google servers is being /dev/null'd: In that thread I asked of the reported IP addresses will become part of the SC block list, and was told any IPs reported via SC feed the SCBL. However, since then I've encountered spam from google IPs that I've reported but don't seem to be blacklisted. About a month ago I started keeping track of the IPs and here's a list of the IPs that have sent multiple spam messages even though I have reported them: 209.85.160.187: 3 209.85.161.56: 2 209.85.161.63: 3 209.85.166.177: 2 209.85.166.47: 3 209.85.167.184: 3 209.85.167.65: 2 209.85.208.177: 2 209.85.208.179: 2 209.85.208.45: 2 209.85.208.52: 2 209.85.208.66: 2 209.85.219.172: 2 209.85.219.196: 2 209.85.219.55: 2 209.85.221.51: 2 209.85.222.183: 2 209.85.222.66: 2 the # after the colon is the number of spam messages I've received and reported. I'm guessing these IPs are getting blacklisted but only for a short period of time? Are they automatically removed or does google have to request to be delisted? About 90% of the spam I receive comes from google IPs. I'm getting tired of what seems to be them just thumbing their nose at our efforts to combat this problem. Anyone have any ideas what's going on here?
  7. Do the IPs get blacklisted by SC? As long as that happens I don't care what they do w/ them.
  8. Howdy all - I seem to recall this happening before, perhaps a couple-three years ago? https://members.spamcop.net/sc?id=z6723973700z580d8f6227bc283c1b918450a2e3c366z Spamcop reports for google spam is being /dev/null'd again. Since about 90% of the spam I receive comes from google's servers, this is not good. The submission always responds w/ something similar to this: Tracking message source: 209.85.210.170: Routing details for 209.85.210.170 [refresh/show] Cached whois for 209.85.210.170 : network-abuse@google.com abuse@google.com bounces (25774 sent : 16844 bounces) Using best contacts No reporting addresses found for 209.85.210.170, using devnull for tracking. Yum, this spam is fresh! Message is 0 hours old 209.85.210.170 not listed in cbl.abuseat.org 209.85.210.170 listed in dnsbl.sorbs.net ( 1 ) 209.85.210.170 not listed in accredit.habeas.com 209.85.210.170 not listed in plus.bondedsender.org 209.85.210.170 not listed in iadb.isipp.com Anyone have any idea what's going on? Gmail is so ubiquitous, it's impossible to firewall these IPs w/o upsetting a lot of people...
  9. https://www.spamcop.net/sc?id=z6701008650z8443d041021da58dc93c7fd8f5f68e1az Agreed. Just happened today.
  10. https://www.spamcop.net/sc?id=z6700686795z8eefb6baa04238df0bcefe8cf0f71e01z I was wondering about this too, for many months I've had endless "I've invited you to fill out this form" spam and it all originated from google. Been reporting them using Spamcop dutifully and they were going to (IIRC) network-abuse@google.com. But this week, well see above. Even if a report email isn't sent does the IP address still find its way into Spamcop's blacklist? One would think google would *want* to not allow spam to originate from their servers.
  11. I included the 1st line of the body in the original submission. The $null causes the parser to gobble up the blank line separating the headers from the body and incorporate part of the body into the Message-ID: value. If you remove just the $null from the aforementioned header and resubmit it gets parsed correctly. This is the reason I offered to post the original message instead of the tracking URL. If doing that will be helpful, let me know. Thanks, Paul
  12. the last header is as mentioned, then there's a blank line, and the first line of text from the message reads: Do you need an Investor?
  13. here ya go https://www.spamcop.net/sc?id=z6620853362z4a1334258458d03c2ed000ed00bb6c9ez
  14. Lately I've been getting spam where the last line of the header reads: Message-ID: $null when reporting this using the web form it causes the parser to somehow misinterpret the end of the headers and beginning of the body text. As a workaround I just remove the $null portion and post the report. I've kept an example that fails, so if need be I can post the headers for inspection. Thanks, Paul
×
×
  • Create New...