Дилян Палаузов writes: Please trim, your questions below don't need the quoted material above.
> Should topics in the X-Topics I just noticed this. We probably shouldn't produce "X-", that usage is deprecated. We probably should accept it, however (Postel Principle). "Topic(s)" alone is too generic. Since "List-" headers are RFC- defined, that's probably not a good idea (unless other implementations are very similar to Mailman 2's, or we're willing to promise to adapt to best practice). So I think "Mailman-Topics" which indicates our implementation of topics is best. Comments very welcome > Should topics in the X-Topics header be RFC2047 encoded? Yes, but I don't promise the implementation will be robust. > It should be defined what characters can be / cannot be part of a > topic. Per Mark's message, this is defined in Mailman 2. We have to accept whatever was acceptable in Mailman 2, since our target is people upgrading from Mailman 2 who use topics. I think spaces should be allowed in topics, but not commas. Perhaps the semicolon would be a better separator going forward (as in structured headers in general). Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan _______________________________________________ Mailman-Developers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
