Excerpts from Tero Tilus's message of 2010-08-19 15:07:37 +0200:
> Philipp Überbacher, 2010-08-19 15:40:
> > I'd like it the other way around, always reply to list and simply
> > change to 'sender' in the (at least for me) rare cases where it's
> > not supposed to go to the list.
>
> It is reasonable that replying to list mail defaults to "Mailing list"
> as reply mode.
>
> Sup does pretty good job being list aware. I think the problem here
> is sup failing to detect a list mail and treating it as "ordinary"
> mail. There are at least two cases when sup could (afaik) miss a list mail.
Yep, sup is definitely doing a good job, it seems to be sane in almost
any case.
> 1) A mail which is sent to/cc/bcc a list member and the list so that
> list member gets two copies of the mail. Sup "sees" only the first
> one to arrive, which most probably is the non-list duplicate.
>
> 2) A similar mail than previous but the copy via list is not delivered
> at all. Maybe the list performs delivery magic ("whoa, cc-header
> shows that this list member already got the mail) or whatelse.
I just checked my most active lists and they all were set to 'avoid
duplicates if your address is in CC or TO'. I changed that and will see
what happens. Maybe sup is clever enough to discard the non-list message.
> 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 :)
--
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
