Re:JMAP – a much needed modern email open standard
by gcanyon on Tuesday May 30, 2023 @06:37PM
(#36132020)
Yeah, I abbreviated the spec. If I were putting together a full requirements doc for this feature, it would have to include different levels/types of filtering. So e.g. if I registered my email with [email protected] and then received email from [email protected], that wouldn't receive the same sort of blackholing as an email using the same token but from *@sospammy.com
Re:JMAP – a much needed modern email open standard
by ilyt on Thursday June 01, 2023 @08:40AM
(#36150301)
If it was new protocol the XMPP approach would most likely be saner.
Which is "if I don't put it on my contact list you ain't getting thru". The invite spam is far easier to handle than message spam.
* Making a wildcard email address for domain, say @example.com
making a filter that only allows [email protected] (or [email protected]) to accept mails from @sourcedomain
Could replace it with hash in second part hashing whole sender's address with some secret but that might be annoying if you have to tell the email via phone and now it needs to be generated manually
But
> 4. Even if the original authorized party tries to email me from a different address at the same domain, that email will be handled as in (3). 5
Would likely bite you HARD as it isn't too uncommon practice to respond from other email if say you are contacting some generic alias (contact@) but get answer from (john.doe@) that handles your case.