• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About lisati

  • Rank
    Advanced Member
  • Birthday 11/01/1960

Profile Information

  • Gender
  • Location
    Porirua, New Zealand

Recent Profile Visitors

1,210 profile views
  1. I ran my own mail server for a few years, until the machine I was using gave up on me. Weighing up the options, and fine-tuning the automated processes for dealing with unwanted incoming mail can take a little bit of work, but it can be extremely satisfying. I never got round to setting up my own RBL/DNSBL, but that's one of the things I'd consider if I did ever run my own server again.
  2. Am I to understand that you have a cron job on your server which you use to process unwanted email, and you then forward the processed data to Spamcop?
  3. Forwarding the offending emails as attachments to your Spamcop reporting account should be fine most of the time. One advantage is that you can send them in batches, and, depending on your settings, Spamcop will mung (disguise) your email address in any reports it sends out.
  4. Agreed, it's a pain. It's one of those things that seem to be sent to trip us up when using automated tools to assist the reporting process,.
  5. I'm mildly surprised that your email was rejected, but an outright rejection for a "4XX" code has been known to happen. (A "4XX" code, 451 in your example, usually means "Try again later." While waiting for other suggestions, I'd suggest looking into why the list maintainer might have thought that your IP address had a spamtrap hit.
  6. As far as I know, the most important thing is to leave the "Received:" headers intact, as they potentially provide a chain of custody that can be used to determine where to submit reports.
  7. Using confirmed opt-in is a good idea. If you're using a sign-up form on your website which blindly accepts email addresses without doing at least some kind of check on the validity of the information provided, you're setting yourself up for trouble. Anyone can enter any rubbish on the form, and if what is entered happens to match someone's spamtrap address, chances are extremely low that a real person will be clicking on an unsubscribe link.
  8. Have you updated your mailhost configuration for your Spamcop reporting account?
  9. A popular response I've had from places like Yahoo is "The most effective way of reporting spam is to use the report button" - I do, thanks to the Habul plugin for Thunerbird, and off go the reports to Spamcop, Knujon, and a couple of other places.
  10. You are not alone. I occasionally have this happen with a couple of email accounts I have with Yahoo. Sometimes the reports turn up at SpamCop's end after a delay, sometimes the reports go AWOL. I haven't quite figured it out yet. Even if it's related to Yahoo's anti-spam processing, it's still annoying.
  11. It might be a good idea to change your passwords, a.s.a.p. Yahoo has had some data breaches in the last few months. A couple of the email providers I use have additional options available to help reduce the risk of people snooping. For example, every so often gmail/google sends me a text message before I can login via webmail. Without access to the phone, access to the email account will be more difficult.
  12. I think a year or two back, Yahoo made some changes so that emails didn't always play nice with the parser. I commonly see Received: headers in email that come through Yahoo that begin "Received from" (suggesting internal handling) but continue as if they were received from an external IP adddress. I regularly report to multiple places, including Spamcop, Knujon and spam[at]
  13. It often takes reports from more than one person for an IP address to be listed. Even if an IP address is listed, there is no guarantee that an email provider will check the SCBL as part of its spam filtering process.
  14. Gmail probably thinks your legitimate email is spam. At least they linked to a help page - Yahoo tends to send reports of mine it doesn't like to the bit bucket without notice.
  15. When I took a look at the tracking link, it was showing that reports were disabled for the intended recipient. This could be part of the explanation why you're unable to report.