Newbie Help for multiple signatures

[googly.negotiator862 at aceecat.org]

On Sat, Jul 20, 2024 at 04:09:20PM GMT, Kurt Hackenberg wrote:

> >   https://neomutt.org/guide/configuration.html#lists

> It might not help.  MN Repair earlier said this:

> > I do not have internet access. My email service is a 3rd party
> > private APN. So please exclude links in your answers.

Mea culpa. Here's the section I linked:

  14. Mailing Lists

  Usage:

  lists [ -group name ...] regex [ regex ...]
  unlists { * | regex ... }
  subscribe [ -group name ...] regex [ regex ...]
  unsubscribe { * | regex ... }

  NeoMutt has a few nice features for handling mailing lists. In order
  to take advantage of them, you must specify which addresses belong
  to mailing lists, and which mailing lists you are subscribed
  to. NeoMutt also has limited support for auto-detecting mailing
  lists: it supports parsing mailto: links in the common List-Post:
  header which has the same effect as specifying the list address via
  the lists command (except the group feature). Once you have done
  this, the <list-reply> function will work for all known
  lists. Additionally, when you send a message to a known list and
  $followup_to is set, NeoMutt will add a Mail-Followup-To header. For
  unsubscribed lists, this will include your personal address,
  ensuring you receive a copy of replies. For subscribed mailing
  lists, the header will not, telling other users' mail user agents
  not to send copies of replies to your personal address.

  Note

  The Mail-Followup-To header is a non-standard extension which is not
  supported by all mail user agents. Adding it is not bullet-proof
  against receiving personal CCs of list messages. Also note that the
  generation of the Mail-Followup-To header is controlled by the
  $followup_to configuration variable since it's common practice on
  some mailing lists to send Cc upon replies (which is more a group-
  than a list-reply).

  More precisely, NeoMutt maintains lists of regular expressions for
  the addresses of known and subscribed mailing lists. Every
  subscribed mailing list is known. To mark a mailing list as known,
  use the list command. To mark it as subscribed, use subscribe .

  You can use regular expressions with both commands. To mark all
  messages sent to a specific bug report's address on Debian's bug
  tracking system as list mail, for instance, you could say

  subscribe [0-9]+.*@bugs.debian.org

  as it's often sufficient to just give a portion of the list's e-mail address.

  Specify as much of the address as you need to to remove
  ambiguity. For example, if you've subscribed to the NeoMutt mailing
  list, you will receive mail addressed to
  neomutt-users at neomutt.org. So, to tell NeoMutt that this is a
  mailing list, you could add lists neomutt-users@ to your
  initialization file. To tell NeoMutt that you are subscribed to it,
  add subscribe neomutt-users to your initialization file instead. If
  you also happen to get mail from someone whose address is
  neomutt-users at example.com, you could use lists
  ^neomutt-users at neomutt\\.org$ or subscribe
  ^neomutt-users at neomutt\\.org$ to match only mail from the actual
  list.

  The -group flag adds all of the subsequent regular expressions to
  the named address group in addition to adding to the specified
  address list.

  The “unlists” command is used to remove a token from the list of
  known and subscribed mailing-lists. Use “unlists *” to remove all
  tokens.

  To remove a mailing list from the list of subscribed mailing lists,
  but keep it on the list of known mailing lists, use unsubscribe .

-- 
Ian