From: David Bremner <david@tethera.net>
To: Jameson Graef Rollins <jrollins@caltech.edu>,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: v4 of repairing Mixed-up mangled MIME messages
Date: Sat, 14 Sep 2019 14:33:56 -0300 [thread overview]
Message-ID: <87d0g2zssb.fsf@tethera.net> (raw)
In-Reply-To: <87v9tu508a.fsf@caltech.edu>
Jameson Graef Rollins <jrollins@caltech.edu> writes:
> On Sat, Sep 14 2019, David Bremner <david@tethera.net> wrote:
>> Jameson Graef Rollins <jrollins@caltech.edu> writes:
>>
>>> Can we have notmuch auto-apply a tag, like the "encrypted" and "signed"
>>> tags, that indicates mail has been mangled in this way? I'm feeling
>>> somewhat morally opposed to just silently fixing mail that's been broken
>>> by bad/irresponsible actors on the net. We need to keep pushing on MS
>>> to fix this issue globally, so I for one would like to be reminded if
>>> I'm still being affected by this.
>>
>> It's side point, but it should rather be a property than a tag if we do
>> something like that. In hindsight I think "auto tags" were probably a
>> design mistake, since they are (easily) mutable by users.
>
> Right, sorry, yes it should be a property. I agree.
>
> Any reason not to move "encrypted" and "signed" to be properties as
> well?
I guess it would require some client code to be adapted. I'm not sure
what really relies on those tags other than ad hoc searches.
d
next prev parent reply other threads:[~2019-09-14 17:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 3:27 v4 of repairing Mixed-up mangled MIME messages Daniel Kahn Gillmor
2019-09-09 3:27 ` [PATCH v4 1/4] test: add test for "Mixed-Up Mime" message mangling Daniel Kahn Gillmor
2019-09-09 3:27 ` [PATCH v4 2/4] util/repair: identify and repair "Mixed Up" mangled messages Daniel Kahn Gillmor
2019-09-14 1:58 ` David Bremner
2019-09-15 7:37 ` Daniel Kahn Gillmor
2019-09-15 7:38 ` [PATCH v5 " Daniel Kahn Gillmor
2019-09-15 20:26 ` Tomi Ollila
2019-09-15 23:09 ` Daniel Kahn Gillmor
2019-09-09 3:27 ` [PATCH v4 3/4] index: repair "Mixed Up" messages before indexing Daniel Kahn Gillmor
2019-09-09 3:27 ` [PATCH v4 4/4] cli/{show, reply}: use repaired form of "Mixed Up" mangled messages Daniel Kahn Gillmor
[not found] ` <87zhj5xcet.fsf@tethera.net>
2019-09-16 10:49 ` David Bremner
2019-09-17 5:59 ` Daniel Kahn Gillmor
2019-09-17 23:36 ` David Bremner
2019-09-14 7:29 ` v4 of repairing Mixed-up mangled MIME messages Jameson Graef Rollins
2019-09-14 11:30 ` David Bremner
2019-09-14 16:08 ` Jameson Graef Rollins
2019-09-14 17:33 ` David Bremner [this message]
2019-09-15 3:05 ` Daniel Kahn Gillmor
2019-09-14 17:54 ` Daniel Kahn Gillmor
2019-09-14 23:58 ` Jameson Graef Rollins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0g2zssb.fsf@tethera.net \
--to=david@tethera.net \
--cc=dkg@fifthhorseman.net \
--cc=jrollins@caltech.edu \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).