• Content count

  • Joined

  • Last visited

Everything posted by gnarlymarley

  1. Years ago when I first saw multiple providers doing this, I started opening up the source and copying. Nowadays, I have setup my own email server and forward all email to spamcop through that server. I find that when I can control who blocks, it is much easier. If you have a second email account, you can setup that in thunderbird and forward to spamcop using that connection.
  2. Actually, I would agree with Lking as you will see the same issue with quick reporting as you see with normal reporting. I believe the issue is somewhere between earthlink and spamcop mail servers, before you even get to the spamcop code. Quick reporting uses the same mail servers that normal reporting uses. I am guessing that once the problem is resolved, you "should" get all the delayed message coming in. Since I was able to send stuff in successfully, I would tend to believe the issue lies on the earthlink outbound email side.
  3. So far, I have never seen an issue between mailhosts and the returning acknowledgement from forwarded spam. My question is when you login, do you see a line right above where you manually submit where it says to "report unreported spam"? I am thinking the issue might be some sort of delay with the inbound mail server and accepting reports. From what I have seen, if you spam makes it to the mailhosts section of the code, you will see it right above the form on the manual submit page. If the unreported link is missing from that section, then your email is not making it to the spamcop code and the issue could be with your outbound email servers. I has forwarded something this morning (around six and a half hours ago) and did get the acknowledgement back, so that part should be working. For quick reporting, you just change the "submit" portion of your special (and should always be hidden) submit link to "quick". You might also need to see the attached.
  4. yeah. I also noticed that your report has a double dot in the hostnames. I wonder if spammers have figured out to fool SpamCop. It very well could be related to the following post since it appears to be stopping around the same point.
  5. Sounds like you might need to have mailhosts setup. mailhosts is to prevent all of your local servers (which forward email from one to the other) from being listed in the reports.
  6. Interesting that the hostname starts with a dot in the submissions where it stops at: View entire message Parsing header:
  7. I am not sure if hiccup is the right word. Whenever I look at your tracking link, as well as a few of my own, they all show errors. It seems to be an issue that is rare, but consistent. I submitted one a few days ago and have not heard back yet. Maybe they were upgrading the system while you were trying to originally submit.
  8. You might want to edit your post to remove your special reporting email address that I am not supposed to know. as for the error, I usually get that when the email I am reporting is not an attachment when forwarding. see Of course, this could be anything from forwarding and not as an attachment to your spam filter removing the attachment.
  9. This does not have much to do with actual reporting, but probably should be answered. No DNS spoofing. This is nothing more than an ISP who has started using the private address in their routers, but forgot to block it on their borders. We have been seeing private addresses more since the IPv4 runout occurred a few years ago. Also, you forgot about line #14 which is also a private address. For me, I just usually block these private addresses on my border firewall. I am sure if you were able to dig further you would probably see that line #13, #15, #16, and #17 are also private address, but they actually blocked those. Now if you start to see the same IP repeated in multiple lines, you would probably know that they are NAT'ting their private addresses.
  10. Seems to me this might be a parser error as it stops on the double period. Hopefully, the deputies are will be seeing this. If not, then might be good to get Don on this at service[at] Host (checking ip)
  11. The reply email (with subject of something like "[SpamCop] Errors encountered") should have some headers near the bottom. Since this email was not able to submit the spam, it does not contain a tracking URL. The bottom of the email should contain the message or part of it that was attempted to be submitted. If it only has part, you can compare the " Content-Type" to see if your sent email has the same boundary tag. Usually when I had issues in the past, it was due to my mail client not aways sending it as an attachment. If you are not able to figure this out, my email from years ago, suggested to email the service address to get more information. Please check your email for an explanation or email for more information. I would not be surprised if cPanel is doing some sort of spam filtering and randomly removing attachments for you.
  12. I found this thread that talks about cPanel removing attachements after you forward. This this spot on the cPanel where you have to allow attachments to head to users. I am not sure why anyone would make attachment filter a default.
  13. I went to and got the following not listed in My guess is that someone was using to send actual spam, it got reported, and now the issue is resolved. When spammers use legitimate email services, it usually gets solved much quicker with the affending party being kicked off.
  14. All spamcop does for us users is to report spam back to the original administrator. I would tend to agree with InvisiBill. As for the issue at stake, I cannot click that "flag as inappropriate" button as the entry was not sent to me. The only person that can morally click the "flag as inappropriate" button is jazz25.
  15. I am not sure I entirely understand the question. What I see is a email that came from and the email has given authorization through a spf check. What happened is that was involved to send the email. If that IP is behind a NAT, then any number of hosts (which use that NAT) could have been used to send the email, including the NAT router itself. What we do know is that any of these devices could have been hacked or else the email was sent by a legitimate person. I am guessing that this is what you meant by possible forgery. Also, if you have any ties to, it might be in your best interest to check for hacking to prevent further usage of that IP by spammer jerks.
  16. Without the IP, there is not much we as users of the spamcop service can do. Spammers are attacking more than just port 25. I have seen spam come directly from a router, which does not have the SMTP service. It would appear that spammers are trying to hack and use anything that can get their message through.
  17. spamadvertising

    The "report" that was sent by SpamCop that contains the link (previously mentioned is other's posts) would have been sent to the data-center that has suspended your account. This means you will need to work directly with the data-center for both the update to spamcop and to get them to give you your account back.
  18. There have been a number of receiving systems in the past that have copied the blocklist error message about the block coming from spamcop. This can be confusing as one would immediately suspect spamcop when the blocklist came from something like spamhaus instead.
  19. is a microsoft website. In my humble opinion, microsoft and other hosting companies do not care about their site being used in someone else's spam. You might see other sites in there that might care more, Most of the folks that I have seen that care are the ones that control the SMTP side of spam. This is in part why I believe spamcop does the truncation of email.
  20. I used to see this error with the spamcop front end proxy servers. Last time I got this, I dropped an email to the deputies.
  21. I believe weduskabe is just a repeat person that keeps signing up for a new account. I am sure they are signed up with a different account that is being used to check when the emails come out and/or stop. These hits, seem to hit hard and then stop after a while, almost like throw away accounts. What gets me is I wonder if the moderators have thought about a reporting system and a IP blocklist. I mean other than the "report to moderator" at the bottom of each post. Probably do something like make their whole IP range report to a moderator when mulitple of us "mark" the entry as spam. Of course, one issue with that is they would try to hack our systems in order to get our IP range blocked too.
  22. Assuming that is a forwarder as it is part of your mailhosts, both and 2a01:111:f400:7c09:0:0:0:183 belong to hotmail/ (aka microsoft). So it would appear that the proper source is reporting correctly.
  23. You can also get this from the confirmation email once you register. Forward your spam to: submit.XXXXxxXXXXXxxx[at] Add this to your address-book. You may forward spam to this addresses from any account. At least this is what i saw from many many years ago, but I believe they still have the opt-in email. Are you looking to fully automate, or just the submission? At one time I had automated it, and found that the automation caught a false positive. Anyway, I suggest to avoid full automation, but automation to the submit address is good, so you can check the submissions are okay.
  24. Looks like you may have notified the necessary folks. If you feel gutsy, you may want to start blocking based on IP, envelope from, or email content from. With the blocking, maybe the sender will start to complain. The hardest part about blocking, is the chance you have a blocking legitimate folks, but sometimes a little bit of blocking is worth it. I would agree with Lking. Once you have reported it, there is not much you can do to get them to stop. My thoughts are if you own your own email server, you can put in a block. Otherwise, if not, you just have to deal with the stuff until they decide to take action on their side. Maybe you can convince your ISP to put in a blocklist if they own the email server.
  25. From what i have seen, most Spammers/hackers try to login with http proxy, ssh or telnet. Once in with console access to the router, they can then initiate a port connection to someone else's smtp server. On my home web server, I have seen unsuccessful attempts at them trying to use http as a proxy for smtp. The Spammer does not care how, they just want to use your IP to make a SMTP connection to send spam. I am not familiar with the Open Router types specifically, but I have seen attempts for apache/squid connecting to send spam. The major issue with most routers, is that tracking of the "proxy" connections is very hard to track.