gnarlymarley

Outernaut, I expect to see an IP somewhere in the Received line such as the following. Received: from oksupp ([IP.add.re.ss]) by elm.nocdirect.com Without the IP address in the Received line, I would have to assume this came from the internal site directly. Which is probably what SpamCop is doing.

I was reading on https://cwiki.apache.org/confluence/display/SPAMASSASSIN/WhitelistingEverybody and see that one should be able to match the IP using the following: header LOCAL_RCVD Received =~ /from .*\[173\./ describe LOCAL_RCVD Received from a local machine score LOCAL_RCVD 50 This will depend on how your mail server formats the Received: line.

I wonder if SpamCop might be having problems with the IP of the receiving server too. If you change it to the follow, it will probably work. It may only want one entry for the receiving host. by www.enchanter.net with esmtps

Spammers use the unicode and base64 to try to hide from spam filters. (Most spam filters can be plain text.) If your filtering can do regular expressions then you can look for UTF-8. Some filtering programs will let you filter for the "raw" headers or the decoded headers. From: "=?eq7rzAaUmUTF-8?B? I suspect this might be a mix, but I do see a UTF-8 in the middle. Usually that start the unicode section.

You can try reporting to deputies[at]admin[dot]spamcop[dot]net, or by requesting a feature in the New feature forum. Many have mentioned a similar problem in the past Microsoft mailhosts missing IP addresses. LaserMoon, I believe the issue to be that microsoft opened themselves up to using around 5,192,296,858,534,827,628,530,496,329,220,096 IP addresses when they moved to using IPv6 public addresses and spamcop might not be able to store them all.

mgolden, I am not sure if this could be your problem but last time I saw this message, it turned out to be one email of mine was forwarding to another. If you have multiple emails involved in a chain then you might need to report them in a backwards order, such as under the "how" section of https://www.spamcop.net/fom-serve/cache/397.html.

I noticed my reports seem to be going through now to abuse[at]hetzner.de. (https://www.spamcop.net/sc?id=z6647053450zec936806eef4e1db9b66291bdb6b3a51z) Maybe something has changed and they are ready to take action?

fritz2cat, The link you gave seems to be only accessible by you or SpamCop deputies. However, you can find an accessible link with munged information if you click on that link and then click on "Parse". That page should have your Tracking URL near the top. (As a side note, if you view that while logged out, you should see the munged information on it.) Here is your TRACKING URL - it may be saved for future reference:https://www.spamcop.net

I automated this using cron scri_pt and a firewall. The problem I saw is the scri_pt happened to catch some legitimate emails and blocked those hosts until it was too late for me to get them back. (There is a grey area of false positives and false negatives where something will be missed and legitimate stuff will be caught. This is why I prefer filtering the emails rather than straight blocking.)

Hopefully your website uses something like a confirmed opt-in. There are spammers that have been going around to websites and signing up other people's email addresses in order to get revenge for being reported for actual spam. The reports don't seem to be enough to make it onto the blocklist: https://www.spamcop.net/w3m?action=checkblock&ip=173.249.157.30

I don't get auto-acks from OVH. I am guessing that 192.99.191.216 was an IP OVH (such as a router) that they didn't lease out because the spam stopped so fast. https://www.spamcop.net/sc?id=z6645272240z11289f59c30f6cd5bc6b75151bc01042z Maybe that is why OVH might takes action on some and no action on others.

I did want to make a note that last night some spam scri_pt started sending me spam from a OVH.net server and about three minutes after I reported it, the spam stopped. I am not sure if I lucked out or if I happened to report at the time someone was in their office.

Outernaut, Lking is talking bout the search box on http://forum.spamcop.net in the top right of the page that you can use to search for "Tracking URL". This limits the search to just forum.spamcop.net. As a side note, the "Tracking URL" can be found at the top of the report page or in the reply email (if you submitted via email). The tracking URL happens to be the same link as URL itself before you submit the page. Incidentally, you can also find this from your past reports if you were able to submit them.

For TLD, I use the blacklist_from annd it works for me. blacklist_from *.su blacklist_from *.ga blacklist_from *.cn For the IP, it maybe it doesn't like too many wildcards, so you might want to try: blacklist_from 170.* blacklist_from 173.*

Hmmmm, are you saying the bitcoin email is too old? When I copied it to my account and cancelled the report, it says it is new enough to report it. https://www.spamcop.net/sc?id=z6644990035z0e890411edb1e0e0d2060b4fd4260904z By tracking URL, they mean the one at the top of the SpamCop report page where it says the email is too old.

I suspect you might be able to do that with the following but the manual is not completely clear on how: blacklist_from [170.0.0.0/8] Since I run my own name server, I setup my own black list there such as: *.170.blacklist.local. IN A 127.0.0.1 *.170.blacklist.local. IN TXT "blocked whole range 20200802"

SCBL means SpamCop Blocking List or SpamCop Black List. Also, for me google says it is "Southern Collegiate Baseball League".

Interesting, I had submitted a copy to my account without mailhosts and it appears to have worked. https://www.spamcop.net/sc?id=z6644191965z228c8ee5751b9ef3fba5a127fdc8818fz When I try to submit with mailhosts, I get the same pause (yes, I know I don't have your mail hosts.) https://www.spamcop.net/sc?id=z6644192306zf677ca6824be06de2a49d01b38114656z This would almost indicate maybe the double dot hostname problem. Hang on, maybe try changing the two dots as below to a single and try submitting again. Received: from DESKTOP-JQ04P8P..home

Nothing immediately stands out for me, but I do see an IPv6 address: whois.ripe.net found abuse contacts for 2a01:4f8:211:2c54::2 = abuse@hetzner.de Might be good to get the deputies looking at this at deputies[at]admin[dot]spamcop[dot]net.

Nope, I am saying that it came from 51.79.145.214 is the source, but user/owner of the computer tied to that IP probably didn't send the message themselves. They "let" someone else use their computer because they didn't patch it. Spammers love it when they can use someone else's cameras, routers, computer, refrigerator, or other IOT device to send their stuff so they don't get caught. Keep reporting these as we at least need to get them to patch or fix the problem. If it is a person that has let someone else use their machine, they need to deal with the problem.

Nope, I am saying that OVH customers were probably hacked. The spammer is just using the Newegg hostname to try to get past spam filters. (Some people who get a spam report that supposedly came from their discount it and ignore it because they "didn't send it".)

Two decades ago, spammers were advertising the wrong hostname to get past blocking filters. When spam filtering kept getting them, some of them went to using their real hostname of the computer they had hacked. I think most of the OVH spammers might be the "fly by night" salesman, where the OVH computers are not patched. I think that by the time we file a report, they may have already abandoned the machine.

I am not sure if this is the issue because I have a juno account on my mailhosts with 179 webhosts and I don't have any problems with it. Looking at your tracking URL, the Received: lines appear to be out of order. Received: from outlook by outlook Received: from exhangelabs by reliablemail Received: from exhangelabs by exchangelabs Received: from exhangelabs by outlook Received: from reliablemail by reliabledns Received: from reliableedns by reliabledns In searching the forums, the first thing that popped up was an outlook issue: https://www.spamcop.net/fom-serve/cache/122.html Are you using outlook? (Apparently there don't have issues with outlook express, only outlook.)

I would suggest you start with deputies[at]admin[dot[spamcop[dot]net. They will be able to analyze it.

Ricardo_63, this "Received:" line should be added by the receiving email server. And should not be disabled by any spammer. Though RFC2882 might be confusing, RFC5321 explains this well in section 3.7.2, where your ISP should be adding that line. 3.7.2. Received Lines in Gatewaying When forwarding a message into or out of the Internet environment, a gateway MUST prepend a Received: line, but it MUST NOT alter in any way a Received: line that is already in the header section. Another way to think of it, is if your ISP refused to put this line on your email, then they must provide another way for you to get the information via a phone call or log access. If they refused to tell you the sending IP and helo hostname, then the offending email must be counted as spam send "by your email provider".