Tim: > > However, if I reply to such a classified (of some kind) message, the > > reply will not have the security header unless I deliberately add one > > while replying. And you'd be unaware of this when replying. > > > > C minus, needs more thought.
Jeffrey Walton: > Not copying previous headers is usually a good strategy. Consider the > case of the Expires: header in marketing email,[1] indicating when a > message should be hidden by the UA or deleted by the server. You would > not want a reply to be hidden based on an old Expires: header. Yes, and no... It depends on the header and its purpose. I remember in my early days of the internet, Outlook Express was widely despised for breaking threading by not including the necessary headers in the replies to maintain the chain. It just, VERY DUMBLY, grouped messages with same subject, but didn't thread replies with their prior message in any sane order. And I think if you were replying to a secret or confidential message that the classification should stay the same until someone deemed it should be deliberately changed. I think that NOT behaving that way would get Evolution vetoed as a viable mail client in a sensitive organisation (pun intended). > And a more interesting use case (to me)... what happens when a > sender's UA specifies one Security: header, and the receiver's server > adds a different Security: header? What does the receiver's UA > display? > > [1] > <https://mailarchive.ietf.org/arch/msg/mailmaint/MgtSuOJFfgWbTFuAZjGwXNDMcqo/> Different kettle of fish. I get marketing mail from various things (electronics shops I've bought products from), that I semi-tolerate. They have special offers with expiry dates. It would be useful if the messages could programatically be assessed for that. I could see a situation with a few status flags just above each message for "Expired" & "Confidential" in the same way we get PGP/GPG "signature valid" And the chance to set a few rules to suit myself. Click on the EXPIRED flag on a marketing mail, and trash it. Click on an EXPIRED flag on non-marketing mail and archive it. Or even periodically review the inbox automatically and perform those actions on expired mail for me (according to *my* rules). At the moment Evolution is displaying a big red banner above the list of mail in the current folder warning me that it can't connect to the contacts list in a gmail account. To me that's NOT a red flag occasion. But I would suggest that the current email being a top secret or confidential one should be. Bold and brassy banner for emails you must use due care with, down to calmer looking banners for unclassified or none. It's easy to suffer from information overload with email. But if you work somewhere where such status are important, then you should have some way to make them always be seen. -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
