3 ms·
Alternatively don't accept any internal @foo.com email addresses in your contact us form unless you're an email provider would work too.
by rtkwe 4y ago
Alternatively don't accept any internal @foo.com email addresses in your contact us form unless you're an email provider would work too.
- jrumbut 4y agoHave you ever seen anyone do that though? The only real solution is not allowing contact form emails to be customized with free text input. I guess you could have a manual approval loop for "weird" names (more than 30 characters, has a dot in it, etc) or other signs of spam. It would still leave some space for spamming though (I can't imaging a rule that stops "Buy More ETH" but doesn't stop any unusual real name).
- rtkwe 4y ago> Have you ever seen anyone do that though? I don't know I haven't really probed random contact forms to see if they block this kind of thing. There's a lot more to do to block this kind of proxy spam entirely for sure I was just talking about the particular problem of using the contact for to send to an mailing list.
- jrumbut 4y agoIt's definitely evil genius stuff. I'm sure enough organizations have a mailing list called "customers@company" or "clients@company" to make it worth a shot. Colleges probably have "students@school" or "faculty@school" list. Might be enough names you can profitably do it by hand.