Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: ding@gnus.org
Subject: Re: Define groups of recipients
Date: Sun, 17 Mar 2019 13:42:48 +0100	[thread overview]
Message-ID: <87tvg17juf.fsf@web.de> (raw)
In-Reply-To: <s6j4l82babk.fsf@bobnewell.net> (Bob Newell's message of "Sat, 16 Mar 2019 14:42:39 -1000")

Bob Newell <bobnewell@bobnewell.net> writes:

> > Ok, thanks.  Do I get it right that this approach involves to add an
> > individual contact for any person that should be part of the group?
> > Is there any way to avoid this?
>
> As others have pointed out, there are workarounds that I think
> in the end are not as good as using BBDB as designed. At
> first, adding a mail-alias for each user in a group may seem
> like a bit of a pain, and it is, but ultimately it is much
> easier to maintain when members enter and leave a group. It is
> very simple to call up a BBDB record and add or remove an
> alias.
>
> It would be possible to do some coding to accept a list of
> email addresses and add an alias for each one, but unless you
> have dozens of members on the list that would likely take
> longer (although it would be reusable).
>
> On the other hand, I recently had a list of 50 to create and
> it took me around five minutes. I didn't think that was
> excessive.

Ok, thanks for your opinion.  Maybe I'll just do what you suggest.  BTW,
one problem is that I only have a list of addresses, I don't even know
the names of these people.  It feels a bit strange to add a record for
them.


Michael.



  reply	other threads:[~2019-03-17 12:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 13:45 Michael Heerdegen
2019-03-15 14:50 ` Enrico Schumann
2019-03-15 15:44   ` Michael Heerdegen
2019-03-15 15:58     ` Eric Abrahamsen
2019-03-15 19:37       ` Michael Heerdegen
2019-03-15 21:41         ` Eric Abrahamsen
2019-03-15 22:25           ` Michael Heerdegen
2019-03-16  0:41             ` Eric Abrahamsen
2019-03-17  0:42     ` Bob Newell
2019-03-17 12:42       ` Michael Heerdegen [this message]
2019-03-17 12:59         ` Dan Christensen
2019-03-18 15:16           ` Emanuel Berg
2019-03-18 16:31           ` Michael Heerdegen
2019-03-18 16:54           ` Michael Heerdegen
2019-03-18 17:15             ` Eric Abrahamsen
2019-03-18 22:59               ` Emanuel Berg
2019-03-19 15:34                 ` Eric Abrahamsen
2019-03-19 16:53                   ` Emanuel Berg
2019-03-16  0:17 ` Emanuel Berg

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=87tvg17juf.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=bobnewell@bobnewell.net \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).