• 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

2,637 profile views
  1. Sometimes Spamcop decides not to bother the abuse contacts for the reasons already given. When reports aren't sent, for whatever reason, the data gleaned from the submitted spam is still useful for helping to build the SCBL. Any reports that are sent and subsequently acted on are a bonus.
  2. I'm putting in my vote for tools like SPF. I believe backscaterrer[dot]org have on their website some examples of configuration for different servers that will help block bounces without restricting legitimate mail.
  3. I've noticed that spam I've received that tracks back to a mailchimp account tends to get devnulled. When I see this, I usually manually forward the offending email(s) to abuse[at], which commonly results in an autoresponse, and occasionally a follow-up email.
  4. I think the uce[at\ address was phased out back in 2004, and replaced with spam[at] Source:
  5. The community who regularly contribute to this forum is made up of volunteers from a variety of backgrounds. Some of us (myself included) live outside of the USA, and have a different set of legal and cultural considerations to bring to any discussions. One thing we have in common is a dislike of unwanted email. It's not always easy to effectively deal with the "spam" issue when the people who receive the reports sent on behalf of Spamcop users don't seem to care.
  6. That sounds like an annoying situation. I occasionally receive suspicious mail claiming to be from PayPal. One or two I've received in recent months appear to come from the same email provider as the one I normally use, which can be a pain when the parser stops in its tracks with a message about "No source IP address found" - there's usually sufficient information available to report those ones manually.
  7. I noticed a similar message earlier, and likewise noticed that it seems to be fine now. I'm pencilling it in as a busy period for the servers doing the hard work on our behalf.
  8. There's always the option of forwarding a copy of the suspicious email to spoof [at] As far as I know, it doesn't require you to have a Paypal account. See
  9. This usually means that Spamcop has decided not to bother the intended recipient with reports. There are a number of possible reasons for this, perhaps the email address that Spamcop has a histroy of bouncing, meaning the reports Spamcop have sent haven't made it to the recipient's inbox.
  10. I use Habul version 1.21.0 with Thunderbird 52.5.0, even though some of the documentation I've read suggests that it hasn't been tested on more recent versions of Thunderbird. If you install it and use it to send reports to multiple recipients, I'd suggest checking that the recipients list is set to "BCC" instead of "To"
  11. Thanks, that sounds good.
  12. The initial email I received had all the same email addresses I normally use with Habul, and I subsequently received a Spamcop notification indicating that there was a problem with "my" submission, as if I'd forgotten to forward something as an attachment. I have a feeling that I'm probably safe, in the past the same recipiients have seemed a bit clueless about what Spamcop is or what they do.
  13. This morning I received a response to an email complaint I'd sent using the Habul plugin for Thunderbird. It looks likes the sender hit "Reply-to-all" and ended up sending a copy of their response to the submit.xxxxxxxxxxx[at] email address I normally use to report spam. Do I need to be worried?
  14. ^^^This.
  15. When you log in to the spamcop reporting site, you should see a tab "mailhost" which is used to give the parser some information that helps it correctly identify the source of spam. An explanation can be found here: