Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@northernlight.com>
Subject: Re: Mailing list and Gcc header in nnimap groups
Date: Fri, 09 Nov 2001 12:31:49 -0500	[thread overview]
Message-ID: <m3668jluka.fsf@onyx.nimbus.northernlight.com> (raw)
In-Reply-To: <m31yj7anch.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Fri, 09 Nov 2001 12:02:48 -0500")

prj@po.cwru.edu (Paul Jarc) writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
>> Suppose I've got an nnimap group for a mailing list and compose a
>> message to the list.  The message has a Gcc header pointing to that
>> group (via gcc-self).
>
> I assume the gcc-self is there to catch non-wide replies.  (If not,
> what is it for?)  In that case, you could replace the gcc-self with a
> Gcc posting style, where the value is a function that detects whether
> the reply is wide, and returns the appropriate string.

What about comparing Message-ID headers of incoming messages to
existing messages, similar to the way nnmail-split-fancy-with-parent
works?  I don't mind duplicate messages so much if they end up in the
same folder, but I don't want to have to set up mailing lists for
everything.  Especially since I don't necessarily group messages by
mailing list.  For instance, my "ding" folder contains messages
forwarded from the newsgroup, mailing list messages, and personal
discussions about bugs.  So for me, the "mailing list == folder"
assumption doesn't work too well.

Maybe there could be an explicit comparison of messages with identical
message IDs.  If the message body is a duplicate (plus or minus some
user-defined variable fodder that some mailing lists inject) then the
user could choose to delete that message.

Thanks
Ted




  reply	other threads:[~2001-11-09 17:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-09 16:50 Kai Großjohann
2001-11-09 17:02 ` Paul Jarc
2001-11-09 17:31   ` Ted Zlatanov [this message]
2001-11-09 17:52     ` Paul Jarc
2001-11-09 18:21       ` Ted Zlatanov
2001-11-09 18:38         ` Paul Jarc
2001-11-09 19:16       ` Matt Armstrong
2001-11-09 19:25         ` Paul Jarc
2001-11-09 19:58           ` Ted Zlatanov
2001-11-09 21:51   ` Kai Großjohann
2001-11-10  6:40     ` Matt Armstrong
2001-11-09 18:50 ` Amos Gouaux
2001-11-09 19:14   ` Matt Armstrong
2001-11-09 19:18     ` Paul Jarc
2001-12-29  6:42       ` Dynamic stuff (was: Mailing list and Gcc header in nnimap groups) Lars Magne Ingebrigtsen
2001-11-09 21:53   ` Mailing list and Gcc header in nnimap groups Kai Großjohann
2001-11-10  2:56     ` Amos Gouaux
2001-11-10 17:11       ` Kai Großjohann
2001-11-11  3:05     ` Paul Jarc
2001-11-11  7:15       ` Amos Gouaux

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=m3668jluka.fsf@onyx.nimbus.northernlight.com \
    --to=tzz@northernlight.com \
    /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;
as well as URLs for NNTP newsgroup(s).