Jump to content

lisati

Memberp
  • Content Count

    433
  • Joined

  • Last visited

Everything posted by lisati

  1. What I'm seeing with th What I'm seeing is that the modification(s) still seem to be necessary.
  2. 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.
  3. 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.
  4. Had one of those (or was it Japanese?) a few weeks back. It could be taken as evidence that spammers are stupid.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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"
  10. 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
  11. 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.
  12. 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).
  13. 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.
  14. 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.
  15. lisati

    E-mail reporting -- "No reports filed"

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

    ocn.ad.jp spam

    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.
  17. lisati

    ocn.ad.jp spam

    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.
  18. 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.
  19. 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
  20. 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.
  21. lisati

    SpamCop and Thunderbord plug in

    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......
  22. @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.
  23. Have a look here: https://www.spamcop.net/fom-serve/cache/329.html#bounces
  24. I wish to disavow any connection with the above response.
  25. lisati

    AFKB

    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......
×