• 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,686 profile views
  1. The IP address is there. I checked using an online blacklist checking site, and the good news is that the IP address apprears clean.
  2. Odd..... I wouldn't worry about it too much, since it's part of the body. The parser seems to have discovered enough useful information from the headers to be able to flick off reports and feed the stats database for the blacklist.
  3. I suspect that Google (or whoever) are looking at the message content rather than who it's from. Sometimes it's necessary to log in to webmail and click on "Not spam" for the message(s) that you believe have been misdirected. This will help retrain your provider's filters to treat reports arriving from Spamcop as "normal" mail.
  4. I occasionally get similar autoresponses, and tend to ignore them.
  5. Works well for me, not just for gmail, but for email accounts with other providers as well.
  6. I second that. I, too, use Thunderbird to access my accounts by IMAP, and then use Habul to assist with the reporting, and have been doing so for a number of years.
  7. Reporting to spamcop does not guarantee that the spam will stop. The way you might expect a reduction is if (a) enough reports are made by different people for the offending IP addresses for them to get listed, and (b) your email provider uses Spamcop's ist.
  8. @Teresai: We understand that you are grumpy with your situation, but without providing us with the information we need to take a proper look, there is little we can do to help. It is also bad form to disrespect the forum admins.
  9. 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.
  10. 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?
  11. 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.
  12. 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,.
  13. 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.
  14. 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.
  15. 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.