lisati

True. When I was running my own email server a few years back, I had what amounted to private blacklists, hidden from public view until an incoming email ran foul of the filtering I had in place. I never got round to running a DNSBL/RBL.

If it's on abuseat's CBL list, it will usually find its way to spamhaus's ZEN list as well, I think Spamhaus took the list over a year or two back. I'm also seeing listings on other lists as well.

Just a thought: if Google, or any other provider for that matter, does something at their end that interferes with Spamcop's ability to correctly identify the source of an email, it's not necessarily Spamcop's fault. The team at Spamcop are under no obligation to jump to attention and make changes every time we, the users, encounter something that trips up the parsing and reporting process. They will have their priorities, which might not always coincide with what we'd like to see happen. There have been some good suggestions in this and similar discussions. I wish you all well.

Exactly, a nice concise way of saying what I said.

Having seen gmail addreses in some of the spam I receive, I like the idea. Having said that, I anticipate a challenge to whoever works on making the necessary changes at Spamcop's end - I have yet to discover a reliable method of automatically validating email addresses without the risk annoying or inconveniencing innocent bystanders. I suspect that many of the cautions against autoresponders and challenge/response systems apply to email addresses found in the email body too. Take a look here: https://www.spamcop.net/fom-serve/cache/329.html

@nhraj700 Confirmed, I received a similar email.

Agreed, the blank line usually present after the headers appears to be missing. What I'm seeing when I follow the tracking link and then clicking on "View entire message" is just the headers, with absolutely nothing at all after the BCC header. Is this an accurate representation of what actually made it into your inbox?

If the email is being rejected by your server, you won't have any spam to report through Spamcop, which, in some ways is a good thing. If you still want to report or complain, another option would be to do your homework to find out the abuse contact for the IP address, and send them a polite note telling them what is going on. This does not have to involve Spamcop, even though it would be nice to have some data available to help them maintain their blocklist.

It might be a good idea to make sure that your server is not configured to act as an open relay. That way, relay attempts will be blocked, and there will be nothing for you to report.

If you're forwarding the email to your spamcop reporting address, you need to forward it as an attachment.

#metoo - I sometimes have unwanted email arrive at my outlook email account that apparently arrives from yahoo or google, yet the parser decides to use the MSN reporting address. It's annoying having to do so, but when I spot such an email, I uncheck the report to hotmail, and fill in an appropriate abuse address for user submitted reports.

Good luck getting this sorted out. I'm mildly disappointed that the parser detected a problem with the chain of received headers, it would have been nice for Spark NZ (who "own" the xtra.co.nz domain) to have another prod to sort out their email system.

I stopped forward samples to them a couple of weeks back, after I began seeing bounce messages indicating delivery time outs.

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:

I'm in New Zealand - the last time I added fuel (also via PayPal), it took a little while, but it did turn up.