From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] CCing to self mail id when composing mail
Date: Mon, 08 Sep 2008 11:47:43 -0700 [thread overview]
Message-ID: <1220899449-sup-112@entry> (raw)
In-Reply-To: <1220507464-sup-1482@buckwheat>
Reformatted excerpts from Daniel Wagner's message of 2008-09-03:
> I don't know if this is related, but I have noticed that sup is a
> little bit too smart for itself. I sometimes also CC myself. Though
> these messages appear in my procmail.log, sup seems to recognize that
> they are a duplicate of a message already in the index, and silently
> hides them.
Oh yeah. Sup collapses dupes. That would do it.
That's another interesting lesson I've learned about email in the
process of writing Sup. Two messages with the same message id are more
likely than not to NOT be exactly the same message. For example, any
time you get a message both cc'ed and through a mailing list, they'll
have the same message id, but the mailing list one will probably have
extra content (ML signatures and taglines) and different headers.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-09-08 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 12:03 Manish Sapariya
2008-09-04 3:29 ` William Morgan
2008-09-04 5:53 ` Daniel Wagner
2008-09-08 18:47 ` William Morgan [this message]
2008-09-08 19:29 ` Nicolas Pouillard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1220899449-sup-112@entry \
--to=wmorgan-sup@masanjin.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox