Jump to content

gnarlymarley

Membera
  • Content count

    134
  • Joined

  • Last visited

Everything posted by gnarlymarley

  1. gnarlymarley

    Definition of spam

    There is a small catch on that FAQ page where emails can be personalized, but still unsolicited. I would still say that they send one to you about your domain and send one to me about my domain, it would fit the definition of opt-out and would be something that the sender is doing in bulk, just trying to use the domain to "kinda personalize" the message.
  2. gnarlymarley

    List / Delist / List / Delist

    The only way to get these listings on the spamcop black is to have actual spam reported by mutliple folks around the world. That said, there are a few things you can check to make sure the spam is not coming from those IP addresses. I believe you have already checked the logs on your mail server. Next you can check for weird activity on those servers, such as malware or viruses. After that, you can check your router and for rouge network traffic. A packet capture utility such as wireshark can be helpful to finding the problem. As for checking the router, I have had some spam come directly from the spamcop IPs before and it turned out that someone had hacked into the router. When folks are accessing the router directly, it is possible that they could spoof your IPs. Also, if these are shared IPs (DHCP) you might want to watch out for that.
  3. gnarlymarley

    Nothing but error messages!

    What do you mean by "long email contents"? I can submit emails as large as 2Mb without issues. (Of course, spamcop truncates these to 50Kb as I expect.) I usually see the following message when I forward the email, but not as an attachment. Forwarding email inline seems to lose the headers and this is why I get this reply. [SpamCop] Errors encountered Gmail has made a change on their view source page where now they have extra stuff that is not RFC compliant at the top, so copying the whole view source page is not suggested. It is best to either figure out how to forward as an attachment or else use that "copy to clipboard" button and paste it in the spamcop window.
  4. gnarlymarley

    What part header

    The issue is with this blank line here: X-SpamCop-note: Converted to text/plain by SpamCop (outlook/eudora hack) Delivered-To: x Which the parser cannot find the from, to, and subject lines above that blank line. In all my years, I have never seen a spam with the X-SpamCop-note header in it. That blank line in the middle of the headers leads me to believe that this is a mutliple copy/paste headers, possibly from different emails.
  5. gnarlymarley

    How to automatically submit spam?

    Automatic reporting is not always a good idea. Years ago, I had a forward as an attachment rule that automatically reported spam. For some reason I had a friend that got caught in that rule and it was automatically reported. Needless to say, we no longer speak. Now if you are saying that you will go through the spam yourself before being it gets "automatically reported", then that maybe a different thing. Having the ability to detect false-positives and false-negatives before reporting is the reason why we have the spamcop page with the information it has on it by the submit button, so we can double check. Maybe I should ask, what do you mean by reporting automatically?
  6. gnarlymarley

    Reported by Mistake

    The tracking link is found at the top of that page after you click on it. SpamCop v 4.8.7 © 2018 Cisco Systems, Inc. All rights reserved. Here is your TRACKING URL - it may be saved for future reference: https://www.spamcop.net/sc?id=
  7. This is why I setup This is why I setup a personal email server with fetchmail years ago because a lot of the the email providers go through these phases, without having a way to turn it off.
  8. gnarlymarley

    ipv6 still unsupported?

    Actually, I think this is an easy fix if they are still using regex like they were years ago. Adding something like a "\s" such as "/\sReceived:\s.../" would probably fix it. "/\WReceived:\s.../" would not as the \W matches the hyphen "-". Another possible fix is "/\bReceived:\s.../" as the \b should match the start. If they were using a //gsm in perl, then the fix could be "/^Received:\s...../". I suspect not as I have not see the deputies in a few years on in the forum. You can probably reach someone at their deputy address: deputies[at]spamcop.net
  9. gnarlymarley

    ipv6 still unsupported?

    So, if these are bogus headers why is spamcop even trying to use them? If I remember correctly Julian had something setup back around the turn of the century about ignoring "X-*" headers. Why are we even trying to report these headers that are added by google, that placed onto the message after it has been accepted? Technically, if spamcop continues to try to accept "X-*" headers, then we will need to just remove them from the spam before we report them as they are not added by the spammer's ISP.
  10. gnarlymarley

    ipv6 still unsupported?

    Another note is that not all gmail message have that header with an IPv6 address. Some have it with a actual IPv4 address. I wonder if they are testing or trying something. Anyhow, I do find it interesting that spamcop accepts the non-routeable IPv4 address as local in its headers, but not the non-routeable IPv6 address, which is in the same exact location in the headers. X-Received: by 10.31.219.6 with SMTP id
  11. gnarlymarley

    mailchimp.com & list-manage.com

    I have seen a bunch of those, with the similar results. What I believe helped stop them was to keep marking them as spam in gmail and to keep reporting them. For some reason, I have not seen them in about two months now. I forget how long I kept reporting those until they stopped, which was probably around two years. Now if more folks would keep reporting these, they would stay on the blocklist and not be able to send any email to folks using the blocklist until they decided to clean up their act. It maybe the only way to catch their attention.
  12. gnarlymarley

    ipv6 still unsupported?

    I just realized something. It seems that the parse is taking the X-Received line and treating it as a Received line. Probably someone did a coding change and didn't have their parser start at the beginning of the line. X-Received: by 2002 0: Received: by 2002
  13. gnarlymarley

    President of Arden Yamanaka Co.

    What I did is to add my problem email addresses to my block list. Then the messages are blocked at my border server. I do not have to worry about sending bad bounce messages, because the problem email is not even accepted on my server. A kinda off topic action that I performed is that I setup SRS and SPF so that it would prevent others from misusing my domain. SRS works off the "return-path". This has stopped the "mail bouncing emails" that I used to get. A side note is that I have opened my my blacklist and current do not see any "bounces" for messages that "appeared to be sent from me". I am guessing that a combination of these two items has been the reason as to why it has stopped for me, however, you situation could be slightly different. If the sending (bouncing) server is on the spamcop blocklist, then just adding the bl.spamcop.net could stop or slow it down. With it all said, like Lking said, the real problem needs to be worked by the postmaster of the server that is "sending you the bounces". If that said individual does not respond, then the blocklisting and/or SPF is probably your next best option.
  14. gnarlymarley

    Misplaced repy-to-all

    if it was truly your submit address, then I would be worried. That is something that only you should know. Now if they replied to your <report_id>@reports.spamcop.net address, then that is different. The reason why your submit address should be kept hidden from others is that folks could abuse it and it could be turned off. If they do not know what the submit address is, you might be okay, but you might need to get a new one through Don at the deputies address. If you are copying folks on the same email as your reporting, it would probably be best if the submit address was in the BCC field.
  15. gnarlymarley

    Wrong sender evaluation

    Sounds to me like you need to setup mailhost in your spamcop configuration options. Mailhosts is mostly used where you have more than one mail server using public IPs and it is forwarding between them. With this setup, spamcop should correctly idenify the servers in the received line up to your border server and be able to correctly identify the real culprit. The neat thing about mailhosts setups is that it will fix your previous attempts of spam reports and those should display properly.
  16. gnarlymarley

    Nothing but error messages!

    IamInnocent. Yep, that is the page, but google maked a change a while ago, where using ctrl-a does not work. Instead, I used the "Copy to clipboard" button and then go to the spamcop reporting form and paste. Now for your original question, I get that message when I forward, but not as an attachment. Apparently a lot of folks prefer the "reply" style of forwarding and this style throws away the full headers. They change it so much, I am no longer sure if there is a key that you can hit when you click forward for it to send as an attachment. Your other option is to click the "Download original" and attach those files to an email, but that is probably as much work as what I do with the "Copy to clipboard" button.
  17. Looking at the spams, it would appear that the spammer is adding the X-Originating-IP header to confuse the matter. I do not see that IP listed in any Received lines. As it stands, I can trust any spam as far back as my border server. I cannot trust it past that. My border server will have the logs with the IP that for whom I need to report. They in turn can use their logs and pass it up to their suspected source.
  18. This would sure be easier to read if we had the tracking URL. If I see this correctly, then it appears that the email was forwarded through 82.165.159.12. Since I am not familiar with this IP, I will take the route of it possibly okay. Another SpamCop user can take that one on. From what I see, the order of the headers are "Our-IP" and then 185.118.164.141. This would mean that 185.118.164.141 probably used your router to send the email. If we assume that it did come from your IP, then I would guess you already checked the server logs. The next thing I would check is your NAT router and make sure did not get hacked. I have had email seen plenty of email come directly from routers, where it completely bypasses the email server.
  19. If you can, please report every email that you receive that is actual spam, which will allow the spamcop blocklist to have all IPs listed. Also, spamtraps only use mole reporting. See below why spamcop only blocks on reported IPs. When a sufficient number of spams are reported, spamcop automatically adds it to the blocklist. Now, to make sure false-positives are not added, spamcop uses a special formula to verify that only actual spammer's IPs are added to the blocklist. This means that it will take more than one report to have the IP listed on the blocklist. I believe the issue is that folks who send legitimate email do not want to have their IP listed. This can cause issues if spamcop just started randomly adding IPs to their block list. Because of this, I maintain my own block list along side of spamcop, where I can and do block whole subnets from repeated spammers. But before I add the whole subnet to my personal blocklist, I have to check and verify that there is no legitimate emails and that there are no IPs that should not be blocked. *.128.80.bl 3600 A 127.0.0.2
  20. The goal of spamcop is to help us (receivers of spam) to get an ISP to do something about their troublesome clients. If that fails, then just block the IP address until those responsible at that ISP decides to do something about those problematic clients. The goal of the munging is to prevent spammers from finding out who is reporting them. Most spammers do not use a mail server and therefore they are not able to figure out who to retaliate against. The spamcop report contains the ID that the mail server put on it, so the true ISP will be able to see who the email was sent to, who logged in (authenticated to) the mail server, and then do something about it. Edit: What is meant by mole reporting is that the report never goes to the ISP administrators, nor to the suspected spammer. It only is used for statistics and populating the blacklist.
  21. gnarlymarley

    No source IP address found

    I usually see this when the spammer is using my local email provider. Since spamcop is external to my email provider, I have to use the "report spam" button to get it sent to the postmaster to deal with. Before the report spam buttons and back around when spamcop began, we used to forward those emails to abuse@[relatedISP].com.
  22. Interesting that the both the command-line version as well as the "Display Data" link show this as plain text. It sure does confuse the parser. I wonder why RIPENCC has changed the data? https://www.spamcop.net/sc?action=showcmd;cmd=whois 185.202.173.233%40whois.ripe.net
  23. 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.
  24. 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.
  25. 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.
×