From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Define groups of recipients
Date: Fri, 15 Mar 2019 08:58:09 -0700 [thread overview]
Message-ID: <87a7hwb04u.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87ef78qh12.fsf@web.de>
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Enrico Schumann <es@enricoschumann.net> writes:
>
>> With BBDB 3.2, I have
>>
>> 'mail-alias: <grp>'
>>
>> fields in the contacts that belong to <grp> in my .bbdb.
>> In my .gnus.el, I have
>>
>> (add-hook 'message-setup-hook 'bbdb-mail-aliases)
>>
>> When composing a message, the mail-alias in "To:", say,
>> expands (with SPC) into the list of emails.
>
> 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?
How would you rather have it work? I think you can also do it manually
by adding lines to a ~/.mailrc file, see the "Mail Aliases" section of
the Message manual. It looks like it's meant for expanding a single
contact address, but I'll bet you can put whatever string you like in
there.
Eric
next prev parent reply other threads:[~2019-03-15 15:58 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 [this message]
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
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=87a7hwb04u.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.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).