Jump to content

Lking

Forum Admin
  • Posts

    31,654
  • Joined

  • Last visited

Everything posted by Lking

  1. The personal tone of this thread is reaching the point "management" may need to step in and temporarily adjust the posting privileges of members. Posters to this forum may, are encouraged to, engage in a free exchange of ideas. That does not include disparaging remarks about the supporters of those ideas.
  2. This is a situation where despair is all to easy to overcome you. I submit all my spam to SpamCop, KnujOn and acma.gov.au. This supports the work of KnujOn to change the effectiveness of ICANN (the long game) and help build the SpamCop block list to protect email users now (the short game). 'Hang in there' is all I can suggest.
  3. As implored time and time again throughout this forum, what is needed, and klappa requested, is a Tracking URL. At the top of your screen, after you have pressed the "Process spam" button you will see: SpamCop v 4.8.5 © 2016 Cisco Systems, Inc. All rights reserved. Here is your TRACKING URL - it may be saved for future reference: https://www.spamcop.net/sc?id=z6316845800z8e04731e5cc30573fc71c1c5db2e64ebz As with the example above, everyone can see the spam, how the parser processed the spam, and the results. The Report id number you provided above lead to a screen only you can see. For example, 6552436687 a report associated with the Tracking URL above. I don't mean to sound harsh. I just get tired of explaining what is described many times.
  4. See the work of KnujOn for an opinion of the effectiveness of ICANN compliance. In paticular "ICANN and your spam" page 5
  5. When you click "send report." The person submitting the spam should be reviewing where the reports are going and "un-check" any reports that are not appropriate. For example, if a The New York Times article was referenced in the body of the spam there would be no point in sending a report to the Times, or to be sure a reconfiguration of you mail server doesn't result in you reporting yourself. The "Checked" /dev/null reports are not sent but retained for statistical analysis.
  6. Things may have changed sense the /dev/null setting was set. I would suggest posting, including IP addresses, abuse{AT} email, example of SendGrid's response, to the <SpamCop Reporting Help> <Routing / Reporting Address Issues> sub forum.
  7. You are correct, I misspoke. A spam report is not bulk email. However, there is no purpose to sending an email that can easily be filtered out. Why spend the cpu resources/bandwidth to send an email that will be ignored/deleted without being read? Having received 182,861 reported spam in the last 24hrs (when I looked) from users/spam traps, SpamCop has other things to do; Look at the "New Feature Request" forum. As posted here several times, the priorities set by SpamCop are: Correctly identify the IP address of the source of spam to support the SpamCop Blocklist used by others to divert suspected spam from client inbox to a "spam" folder for later review. As a service to those reporting spam to SpamCop, send spam Reports to the admin of the source of the offending email. If the policies implemented in this service don't meet a submitter's needs they are free to send the reports to others. Identify links in the body of the spam and send spam Reports to the admin of the "spamvertised" domains. Another motivation for administrators is money. Depending on the economics there are not enough spam Reports to cause a change in action. JMHO as a volunteer here. Thank you for your contribution to the spam fight. It can be frustrating. We all do want we have the motivation and resources to do.
  8. Yes, obviously. But SpamCop can not force an email hosting company to accept help. If abuse{AT} has requested not to receive spam reports, sending them unwanted report email(s), fits the definition of spam. SpamCop does not want contribute to the volume spam in the system. Yes, and Yes.
  9. I combined the two related topics under "500 Internal Server Error"

  10. Lking

    I merged your post with the earlier related post, "500 internal Server error"

  11. kluless, I moved you last post to the Lounge which I think is a better location for your question.  I think "Reporting Help" is more appropriate for problems reporting spam to SpamCop.

    Hope this does not cause you a problem.

  12. I moved your post "Mailpost configuration problem" to

    the "Mailhost Configuration of your Reporting Account" forum.  You should look at other threads in that forum for answers others have found for similar problems.

  13. I moved your post "have we figured out who this spam gang is?" to the lounge.  Reporting Help should be for request for help.  Your post doesn't really fall into that category IMHO.

    hope this does not cause you any problem.

  14. I moved your post "CERT e-mail address" to the Lounge.  I think this is a better place for the thread than where you posted it in the area of 'how to use the forum '

    Hope you don't mind.

    1. klappa

      klappa

      Thank you very much!

  15. I merged your thread with another on the same topic.

    Hope this does not cause any problem.

  16. I merged you message with

    which also has an issue due to bogus internal IPs Seems the resolutions are related.

  17. Submitting spam does feed the blocklist though.
  18. I don't know about ocn.ad.jp but it would seem so. If you would go back to one of the spam you have reported and looking at the reports sent you will find their IP address (SpamCop tracks IP addresses not domains) you could then go to https://www.spamcop.net/w3m?action=map and find the reputation of their IP address.
  19. Well Farelf, I'm glad you are not talking to yourself.
  20. check what knujon.com is trying to do about this issue
  21. I sense your frustration. I don't think anyone on this forum works for/wrights code for/controls software configuration for Yahoo. Steve T's post seems to summerize the confusing/frustrating situation expressed in both threads you posted in.
  22. Seems the correct phrase may be "Mileage may vary."
  23. Above is what I get when I do a whois on the doamin. May be is issue of DNS tables not being updated. try doing a Google on the domain name. the google links work for me.
×
×
  • Create New...