From: Eirik Byrkjeflot Anonsen <eirik@eirikba.org>
To: notmuch@notmuchmail.org
Subject: Re: Automatic suppression of non-duplicate messages
Date: Mon, 05 Nov 2012 16:22:30 +0100 [thread overview]
Message-ID: <87sj8ot6q1.fsf@star.eba> (raw)
In-Reply-To: <87390pf14v.fsf@nikula.org> (Jani Nikula's message of "Mon, 05 Nov 2012 00:34:40 +0200")
Jani Nikula <jani@nikula.org> writes:
> On Sat, 03 Nov 2012, David Bremner <david@tethera.net> wrote:
>> Offhand I'm not sure of a good method of automatically deciding what is
>> the same message (with e.g. headers and footer text added by a mailing
>> list).
>
> Assuming there was good method, what would you do with two different
> messages that have the same message id? That is the unique id we use to
> identify messages (which should be fine per RFC 5322 and its
> predecessors; we're talking about messages from broken systems here).
We're also talking about data from "untrusted" sources. Assuming that
such data is always non-broken seems overly optimistic. (See
e.g. http://cr.yp.to/immhf/thread.html, the section "Security and
reliability issues" for one view on the matter.)
In fact, I'd say that it should be a design goal for any mail client to
deal with as much invalid input as possible. Show big, fat warning
messages if you want to, but don't just drop the message and pretend it
does not exist.
eirik
prev parent reply other threads:[~2012-11-05 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-03 10:17 Automatic suppression of non-duplicate messages Eirik Byrkjeflot Anonsen
2012-11-03 20:53 ` David Bremner
2012-11-04 10:06 ` Eirik Byrkjeflot Anonsen
2012-11-04 22:34 ` Jani Nikula
2012-11-05 4:28 ` Austin Clements
2012-11-05 15:22 ` Eirik Byrkjeflot Anonsen [this message]
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=87sj8ot6q1.fsf@star.eba \
--to=eirik@eirikba.org \
--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).