N.B. Using service-specific emails is trivial - you don't need separate email accounts. Just use email aliases, e.g. "john.smith+github@gmail.com" -- which is an alias called "github" for "john.smith@gmail.com"
replyA simple regex filter will get rid of that. Now, if you use your own domain and have it configured as a catch-all, then you could do github@domain.tld.
replyI'm not saying I do this but if I were as smart as I think I am I would have given a Gmail example rather than the example you've given to avoid bots just looking up my website and starting to bypass my setup... ;) ;) ;)
replyAlso, spammers generally don't seem to be going to the effort to apply regex filters to the data they've scraped...
IF alias NOT ON allowList MOVE TO specialLittleFolder
replyBy far the worst one is always going to be something generic like contact@, but my email provider is very good at filtering out those appropriately. :)
I self host email, and I have never gotten spam to any email "constructed" from the domain, other than random attempts to things like "accounting@domain.tld" etc.
replyBut the email I used to interact with the Linux kernel mailing list I had to null route after a while, it got so much spam. I used a throwaway for just that purpose of course, so no big deal.
Don't spammers have an automatic filter to cleanup that?
replyYou'd have thought so, but no, in my experience this works very well. People doing this kind of spamming don't seem to be particularly bright, nor do they seem to spend any time/effort to clean up their scraped database.
reply