From: "Philipp Überbacher" <hollunder@lavabit.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] mailinglists in CC
Date: Thu, 19 Aug 2010 21:19:39 +0200 [thread overview]
Message-ID: <1282244722-sup-8361@eris> (raw)
In-Reply-To: <1282241633-sup-6722@tilus.net>
Excerpts from Tero Tilus's message of 2010-08-19 20:24:18 +0200:
> Philipp Überbacher, 2010-08-19 17:26:
> >> You can enumerate mailing lists to mutt and have it consider mails
> >> to/cc a such address as list mails regardless of the precence of list
> >> headers.
> >
> > I don't know anything about mutt and don't consider using it. I'm fairly
> > happy with sup :)
>
> I wasn't suggesting you to go mutt yourself. ;) I was just wondering
> how other mailclients have resolved this problem of duplicate replies
> (one list and one off-list) from ill-behaving mailclients.
My guess is that some client use primitive means like the subject, but
maybe there's some more header information that's useful, like
reference or in-reply-to. Again, I don't know much about headers.
> Possible solution would be to maintain list of known mailinglist
> addresses (say mailinglists.txt, just like we now have labels.txt) and
> consider all mails targeted to a list address as list mail even if
> they wouldn't have list headers.
>
> Any considerations on the implications that would have?
So it would compare TO and CC with the list, and if it finds it, treats
it as list mail. Well, I guess for some of the 'treat as list mail'
things it might need some headers, but I really don't know.
--
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu
und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-08-19 19:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 10:52 Philipp
2010-08-19 11:58 ` Israel Herraiz
2010-08-19 12:27 ` Erin Sheldon
2010-08-19 12:40 ` Philipp Überbacher
2010-08-19 13:07 ` Tero Tilus
2010-08-19 13:21 ` Helge Titlestad
2010-08-19 18:31 ` Tero Tilus
2010-08-19 14:26 ` Philipp Überbacher
2010-08-19 18:24 ` Tero Tilus
2010-08-19 19:19 ` Philipp Überbacher [this message]
2010-08-19 20:11 ` wagnerdm
2010-08-19 12:29 ` Philipp Überbacher
2010-08-19 12:49 ` Tero Tilus
2010-08-19 13:39 ` Israel Herraiz
2010-08-19 12:33 ` Tero Tilus
2010-08-19 12:58 ` Philipp Überbacher
2010-08-19 13:41 ` Israel Herraiz
2010-08-19 14:10 ` Philipp Überbacher
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=1282244722-sup-8361@eris \
--to=hollunder@lavabit.com \
--cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox