Back in October of 2012 I devised a way of blocking abuse of my mailing list server by detecting mailbait abusers (mailbait.info offers a ‘service’ to fill your, or someone else, mailbox with unwanted mailing list subscriptions). In June of 2013 I refined the technique.
Regardless of the popups, people still try to use mailbait to involuntarily subscribe people to my lists (well, try at least, my lists require a closed loop confirmation system).
Today I received the following threat from a mailbait.info user ..
I’m inclined to ignore the ‘warning’ … but I find it somewhat satisfying that my approach has annoyed someone sufficiently.
As an added measure, I’ve updated my system security mechanism to block any IP that attempts to use the mailbait service more than once.
The problem was, they were a subscriber to the list and had posted before … so the normal counter measures for that didn’t work (the first post for all subscribers are held until approved, to prevent people from subscribing, posting spam, and unsubscribing).
The puzzling thing about this was … the ‘from address’ on the message was not in the subscriber list.
Turns out that Mailman will accept message based on the FROM address of the message or the SENDER address (also known as the envelope-from). The sender addressed is set by the sending mail server and is not normally in the body of the message.
After a bit of digging around, I figured out a way to add this information to the message headers so I can more easily diagnose the problem in the future.
Recently I’ve been getting a lot of mail from the feedback loops I subscribe to indicating that someone has gotten a subscription confirmation message and they considered it spam.
After digging into my logs I noticed a few things …
The subscription requests are being initiated from TOR exit nodes.
The web requests that initiate the subscription have “mailbait.info” as their referrer.
This ‘mailbait.info’ service is supposed to allow you to fill your mailbox … why anyone would want to do this is beyond me … and it has absolutely ZERO protections against submitting someone else’s email address. As such, it just ends up generating spam. And a lot of the twits that are using this ‘service’ are hiding behind TOR nodes, which protects their IP address.
I put together a new SpamAssassin rule that will help identify spam from spoofed email addresses.
Some email providers always sign email with DKIM or DomainKeys … based on this assumption, if you get a message from one of those domains and it isn’t signed, you can assume its more likely to be spam.
This particular rule operates on the assumption that all mail from Yahoo & Gmail will be signed. It does not, however, raise the score a huge amount … because it’s just more LIKELY to be spam if it’s not signed … it’s not guaranteed to be spam. Some people may use the Yahoo or Gmail account’s in the from address, but not actually send from that service. Continue reading →
By now everyone’s probably heard about the data breach at Epsilon … which resulted in a lot of major eCommerce vendors customers mailing list getting stolen.
Personally, I’ve gotten notifications from Chase, Walgreen, Tivo, Best Buy, 1-800-Flowers, and a few others … informing me of the breach and assuring me that no critical information was stolen … just my email address.