lisati

What I'm seeing with th What I'm seeing is that the modification(s) still seem to be necessary.

My ISP/primary email provider has a similar option available, which can be useful. One thing to watch, however, is that sometimes there are limits to how many domains that are blocked.

One or two of the dodgy emails I've had seem to have their origins the days before my provider moved away from Yahoo, who had had a couple of data breaches. The password was correct but an old one. I'd already seen evidence that something was a bit "off" and had changed my password as a precaution, prior to receiving claims that my account had been hacked. More recent efforts I've seen in my inbox have been of a slightly different character, and would probably warrant a separate thread. I'd suggest, at the very minimum, a change of password a.s.a.p. for people who get one of these "your account has been hacked" emails, or any other evidence that something's not quite right.

Had one of those (or was it Japanese?) a few weeks back. It could be taken as evidence that spammers are stupid.

I haven't bothered looking too closely for a pattern in the similar emails I've received, but have noticed that the ones I've reported tend to get tracked back to different ip addresses.

It might be overkill for your situation, but running your own email server might be one option - I used to run one from home using Postfix (and a few other bits and pieces) using Ubuntu server, querying the Spamcop blacklist was easy enough to implement once the basic setup was complete.

I've had some similar emails, all of which have been reported. The flow to my email account(s) seems to have dried up for now. As Lking has observed, the visible "From:" address is easily forged, it is a notoriously unreliable clue to the true source of the unwanted email. All the unwanted emails of this type that I have received trace back to somewhere other than my provider. One thing of note, from my perspective, is that the email address for which I have received the most doesn't actually have an associated mailbox to be hacked, the email address exists as a simple redirect in a server.

That's a fairly typical example of some I've received, mostly for one particular email address which, because it's little more than a redirect on a server, doesn't actually have an associated mailbox.

Instead of forwarding the spam as an attachment to "my" reporting adddres, I use the "view source" option of whichever email client, copy it to the submission form on the reporting page, and change the "Received" to "X-Received" before clicking "submit"

It's a known issue. Some remove the "broken" ipv6 Received header. In the interests of preserving all the information available, I submit the spam manually, editing it read X-Received. A similar approach is sometimes helpful with emails arriving at Gmail accounts

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.