Assume you offer a free trial with LLM capabilities. There’s a very real cost associated with multiple signup abuse. You can card capture or KYC, but now there’s more friction and greater loss of privacy.
The plugin offers users a way to input their own block lists, a pre-existing one, or make use of the API which is constantly getting updated.
As a first time Wordpress plugin developer, the approval process was a bit slow but it’s like that for a good reason.
> "Here is the URL from that email [..] https://sites.google.com[...]"
THAT link is the first red flag, and I think the author should say so right there, not three paragraphs later.
This is still limited in what you can do though. For example you can’t use this to forge messages from other people’s Gmail accounts.
> When the message is forwarded, the original DKIM signature usually remains untouched as long as the email content and headers covered by the signature are not modified
It does seem surprising the To: header isn’t one of the headers that is covered by the dkim signature. They should just change how their signing is configured, and email clients should warn when the email is legit but the intended recipient could have been changed.
It adds friction, but does solve the problem. For banking/systems, I'd much rather have the friction.
You’re essentially playing a game of cat and mouse. There’s 12 new domains added today for one provider for example [0].
Use a 3rd party api to block these (disclaimer, this is what I do) and keep layering your security. Note that I’ve seen an increase in gmail temporary email providers, so while many here will disagree, blocking plus emails and . emails is absolutely a valid tactic during this attack period.
* uBlock Origin and Lite have it as an option under Filter List > Privacy > Block Outsider Intrusion into LAN
* Brave prevents it, tested with Aggressively block Trackers and Ads.