lisati

The only one I recall receiving that mentioned a password had one which wouldn't have worked. A few months earlier I had noticed that something was a bit off, and had taken the precaution of changing my password.

I've received one or two similar emails. I'd go with the advice previously given, i.e. report them, and send them to the circular filing system (delete them).

If the spam you're having trouble with is in your inbox, clicking on the "Report spam" (or eqivalent) in your provider's webmail might be of some value. Some providers not only use it to train their filters, but sends off a complain to the sender's provider, I've seen it happen with Yahoo.

I suspect that something similar to what others have reported for Gmail is happening. The workaround I generally use is similar to the Gmail workaround, commenting out the first Received line encountered as you scroll down the message source.

Note to self: check to see if Quick Reporting is still working "correctly" on my account.

Most of the spam I receive at my hotmail/outlook accounts gets flagged for reporting to report_spam@..... as well. There are a couple of options. If you've done the "add fuel to your account" thing you might want to consider looking for the abuse address for the apparent sending server/device, and adding that as a user defined report.

Jumping in relatively late into this discussion, I've had Google block my attempts to submit reports from time to time too. My ISP does it as well. One workaround I use is to send the reports and submissions from an email account that I'm paying a little extra money for that lets me whitelist recipients. It's not perfect, but I have seen a significant improvement.

Short answer: you do the best you can with the information at your disposal. It is possible to develop a sense of which parts of the information in any given email will be the most useful in figuring out where to send your complaints. Sadly, it's sometimes necessary to stop short of using what would seem intuitive, e.g. doing a deep scan of ALL the received header, flicking off a grumpy response to the alleged sender, etc.

Apologies for the delay in replying. As helpful as the "X-Originating-IP" address can be in gathering clues to an email's apparent source, they can be forged. What some providers do is an analysis of the content of the email, sometimes the headers only, sometimes the complete email. Depending on the results of the analysis, the options open to the provider include (1) rejecting the email outright (works best when done BEFORE the complete email has been accepted for delivery), (2) flag the email as spam (possibly by altering the subject), (3) flicking the mail into a spam or Junk folder, or (4) accept the email unchallenged. Be extremely wary of solutions based on some kind of challenge-response system. Because the sender address can easily be forged, it's very easy to annoy innocent third parties

The only Received header that you can trust with any degree of certainty is one inserted by a server you administer, preferably the server that drops the incoming email into the recipient's inbox.

Thanks for the heads-up. The copy I have on my machine seems to have auto-updated to 1.21.0, and I didn't even notice......

@Bernhard: I'm not sure why your server is blocking based on the mailspike "rep" (reputation) list. I had a look at their web page, and get the impression that it's not a general purpose list suitable for blocking everything from a listed IP address. Mailspike's "bl" and "z" lists seem better suited to blocking/rejecting unwanted incoming emails.

Have a look here: https://www.spamcop.net/fom-serve/cache/329.html#bounces

I wish to disavow any connection with the above response.

What? Did I blink and miss something by not visiting this forum for a few days? Anyway, it must be time to consider a hot cuppa in anticipation of a speedy recovery......