@darthnull @danwing And for completeness there's a brand new draft doc for more, https://www.ietf.org/archive/id/draft-jenkins-mail-keywords-00.html
But the problem as it intersects your requirement is one of applicability.
The IMAP keyword mechanism is for functional tagging. The keywords have consistent meaning as defined in their relevant standards.
What you've described as a requirement is an account-based content/logical tagging mechanism. Inter-op registration/discovery would be a nightmare to get through standards adoption, and then there's still the matter of anybody implementing it. Not to say that's it's not desirable but the inertia on older protocols is huge (I have scars and my newest proposal is being held back until the current SMTP “this decade it's complete" draft gets its carcass pushed over the line).
Until then, best bet might be some agreed header that can be fiddled with so clients can filter accordingly.
=> More informations about this toot | View the thread | More toots from QuatermassTools@infosec.exchange
=> View darthnull@infosec.exchange profile | View danwing@infosec.exchange profile
text/gemini
This content has been proxied by September (3851b).