nope, it could be a binary option to match the fact that tls was specified, or it could be an option
with suboptions (tls cipher ..., tls version ...) to match a more specific criteria.
if you implement the more general feature, you still want to put the data for the more specific ones
in the envelope to avoid having to many envelope format changes for foreseen features.
Yeah makes sense.
it means that we have to tell everyone "sorry, the new envelopes are incompatible, you need to empty
the queue and reload smtpd", it's painful for users so you really want to avoid it at all cost. It's
not always avoidable, so if you HAVE to provoke one, we want to make sure it contains all changes we
will need for upcoming features too.
Understood. Yep, painful for sure - maybe it's avoidable, we'll see, not
familiar enough with the code, yet.
I won't hesitate to ask for suggestions/ideas in case of.
