Overwhelmed with Spam in the last three days!
Wow, what is going on? In the last three days, I have gotten over 70 spam emails, some purporting to come from me! Bad spelling, phony gift cards, **bleep** enhancement, sexual positions, you name ...
Forum Discussion
When the hack happened, I immediately wiped the drive (I actually wrote three passes of zeroes) and reinstalled Windows (I think I had 8.1 at the time), and I changed my password on another computer, as well as changing all of my passwords for the other sites I frequent, especially those that have personal info. I now use passwords at least 16 characters long (where allowed) and with no discernible pattern. I have to keep them all written down as there is NO way I could ever remember types of passwords I use, and it would take hackers quite some time, even with a great program, to decipher them. It was a hard lesson learned. And what's really frustrating is that I still know some people that use single word passwords, and when I tell them how important indecipherable passwords are, they do something ridiculous like adding a # sign to the end. Sure, adding a # sign makes it uncrackable. SMH. Derp!
I had occasional spam, but it wasn't until this incident that I started getting bombarded with it. And, unfortunately, even with blocking the domains it doesn't help much. I could spend a few hours each week blocking the domains, and the next week there would be just as many to block again. It's tedious, to say the least, and quite frustrating. Luckily, Outlook has a great spam filter, so that makes it so it's not quite on the level of wanting to pull my hair out. :p
As for my Hughes email, I only use it for the forwarding of notifications from the HughesNet Community, and the first time I signed into my Hughes email was shortly before this new Community started. I actually still had my original HughesNet welcome email from 2004 in the inbox. It was sitting there, unread, for over 12 years. LOL.
The trick is not to block the domain of the email address, those are forged anyway. The trick is to block the domain of the IP that the email came from. I'm building a pseudo-mini-DNS to do this that comprises a regex of the full range of IPs for that domain, a username for the abuse address (bfore the "@"), and the domain itself (after the "@")...
Eventually I wanted this system to return the favor by auto-spamming their abuse address with a forward of each one I get. That kind of backfired, since there are truly foul email servers that collect received emails to... you can guess the rest.
That's how I knew Comcast was hacked to do that some time back. I was getting ten+ back for every one I sent. You can see how that escalates exponentially if I'm "returning the favor".
MarkJFine wrote:The trick is not to block the domain of the email address, those are forged anyway. The trick is to block the domain of the IP that the email came from. I'm building a pseudo-mini-DNS to do this that comprises a regex of the full range of IPs for that domain, a username for the abuse address (bfore the "@"), and the domain itself (after the "@")...
I have no clue how to do any of that, so, for the interim, the best I can do is block the domain and hope for the best. Again, though, due to Outlook having a great spam filter, it doesn't really affect me any more than being an annoyance.
For all I know they do that, but I can tell you that 90% of the spam you get comes from only a handful of server domains.
All the spam is coming from <random>@<random>.nelottery.com
Since the parameter after the "@" appears to be randomly generated, I don't know how to shut it out. Outlook, indeed, is sweeping all of these to the Junk Folder, but boy, I would love to be able to get to Hughes so that THEIR master spam blocker would stop these in their tracks.
And, it is totally possible that nothing can do this. I am SOOOOO darned careful online, so I get really pissed when someone gets my email address and either spams me or spoofs me.
I'll have to see if I can find the IP addresses - but I don't know how to filter those, unfortunately.
