• 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,947 profile views
  1. Almost there, but not quite. Most of us won't be able to view those reports. The tracking URL that's more useful to the rest of us typically appears below this:
  2. I'm in New Zealand - the last time I added fuel (also via PayPal), it took a little while, but it did turn up.
  3. When I report spam that appears to come via mailchimp and it gets devnulled, I manually forward a copy to abuse[at] This commonly gets an autoresponse, and occasionally gets a follow-up email.
  4. I've noticed the pattern of having spam coming in waves, and recently noticed a flood of grumpy customers of the ISP I use on Facebook. I'm currently experiencing a lull in the amount of spam I'm receiving - the flow hasn't dried up completely, but it's a lot quieter for me.
  5. When I checked the link you provided, I noticed this line: Have you configured the mailhost(s) for your email accounts?
  6. I've seen similar, where the message appears to be placed in the subject. It's a minor nuisance when reporting, and a good sign that you're dealing with a spammer. What lking said to do usually works for me.
  7. 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.
  8. 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.
  9. 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.
  10. I think the uce[at\ address was phased out back in 2004, and replaced with spam[at] Source:
  11. 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.
  12. 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.
  13. 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.
  14. 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