Re: Mail-Followup-To header (was: Order priority issues for special 3type sub-section)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Lennart,

On Thu, Mar 07, 2024 at 09:37:43AM +0000, Lennart Jablonka wrote:
> Quoth Alejandro Colomar:
> > I've found now why my MUAs don't include you in the reply.  I've seen
> > the following header in your message.  I don't know if this is something
> > you configured your MUA to send, or if it's an accident.  Please have a
> > look.
> > 
> > Mail-Followup-To: Alejandro Colomar <alx@xxxxxxxxxx>,
> >        Guillem Jover <guillem@xxxxxxxxxxx>, linux-man@xxxxxxxxxxxxxxx
> 
> The Mail-Followup-To header field is good and useful.  And Mutt, for
> example, sends it by default, if you’re properly using `lists` and
> `subscribe`.  “I’m subscribed to this list anyway, so you need not send
> followups to me separately as well.”

Hmm, it's interesting.  It messes with what's To and what's Cc, but it's
better than just replying to the list, which I hate because you never
know who's subscribed to it (e.g., most people in the groff@ mailing
list don't send me a copy of their responses, and I'm not subscribed to
the list; or in other lists, even if I'm subscribed to the list, I won't
read most stuff unless either the subject looks interesting or I'm To or
Cc).

> More people should use and honor it.

While I'll keep not using it, I'll honor it, now I understand it.  :)

> /me unignores mail-followup-to

Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux