From: "Matt Armstrong" <matt+dated+1007925409.d21349@lickey.com>
Subject: Re: Mailing list and Gcc header in nnimap groups
Date: Fri, 09 Nov 2001 12:16:48 -0700 [thread overview]
Message-ID: <878zdf69gf.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <m38zdf96hc.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Fri, 09 Nov 2001 12:52:25 -0500")
prj@po.cwru.edu (Paul Jarc) writes:
> Ted Zlatanov <tzz@northernlight.com> wrote:
>> What about comparing Message-ID headers of incoming messages to
>> existing messages, similar to the way nnmail-split-fancy-with-parent
>> works?
>
> Do you mean duplicate suppression? (See the manual node of that
> name.)
>
>> 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.
>
> Well, Kai's previous suggestion of using the MFT stuff should work
> then. Have a hook function called during sending that checks for
> subscribed list addresses in To+Cc, and set Gcc accordingly. Is there
> any send-time hook that gets called before Gcc is processed?
>
> Maybe the checking of addresses could be done only once, and then a
> buffer-local variable could be set to record the result.
>
> For Gcc, it'd be nice to also check Bcc for subscribed addresses.
> But MFT should not look at Bcc. So maybe they shouldn't be combined
> much after all.
I know from tracing through it that the Gcc: header is gone by the
time message.el sees it -- which makes some sense since message.el
wouldn't know what to do with it.
The MFT code could be re-factored such that it is easier for Gnus to
use it for this purpose though.
--
matt
next prev parent reply other threads:[~2001-11-09 19:16 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
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 [this message]
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=878zdf69gf.fsf@squeaker.lickey.com \
--to=matt+dated+1007925409.d21349@lickey.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).