My private account. Posts/Opinions are my own. Focused on # Open and TCP/ID, identity ownership in the real and digital world. 3D printer. Can solder and repair. Antifascist. European. Policy hacker. Rambles around at times. He/Him/His $argon2id$v=19$m=512,t=256,p=1$SWmoDffV/hOu+/Vii5Nxsw$zYZ5n+cXxZLKoLnXZJjll1JWcCFyiRVli7xOPqu63GM Blocks threads.net Works at Red Hat.
My private account. Posts/Opinions are my own. Focused on # Open and TCP/ID, identity ownership in the real and digital world. 3D printer. Can solder and repair. Antifascist. European. Policy hacker. Rambles around at times. He/Him/His $argon2id$v=19$m=512,t=256,p=1$SWmoDffV/hOu+/Vii5Nxsw$zYZ5n+cXxZLKoLnXZJjll1JWcCFyiRVli7xOPqu63GM Blocks threads.net Works at Red Hat.
When spammers don't like you reporting their spam, they will:
- set up a forwarding email address on one of their servers with good DKIM/SPF/DMARC, typically on a domain that will expire soon
- Run a script that spams hundreds of support addresses/web forms with nonsense content using that forwarding address
- Forward all the confirmation receipts to your email address
That stuff is easy to block, but can be quite a nuisance to the affected support teams.