From: Glyn Millington <glyn.millington@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: lamer... how to send group email efficiently
Date: Mon, 24 Jun 2013 21:36:24 +0100 [thread overview]
Message-ID: <87bo6vdz5j.fsf@nowhere.org> (raw)
In-Reply-To: <87mwqfxp12.fsf@newsguy.com>
Harry Putnam <reader@newsguy.com> writes:
> Its a lamer question for 10+ yr gnus user but I've never had occasion
> to send group emails. Just not something I do.
>
> Now I have need of a nice efficient way to send emails to a couple
> dozen recipients... and looks as if I will be doing this every couple
> of weeks.
>
> The list of recipients will change over time but only by a few
> deletions or additions... so it would be nice to be able to just add
> or subtract email address' to/from something and gnus/emacs will do
> the rest.
>
> There must be a number of folks here who have developed nifty ways to
> do this... please anyone share your technique.
Hi Harry,
From the Manual
| 2.10 Mail Aliases |
| |
| The message-mail-alias-type variable controls what type of mail alias |
| expansion to use. Currently two forms are supported: mailabbrev and |
| ecomplete. If this variable is nil, no mail alias expansion will be |
| performed. |
| |
| mailabbrev works by parsing the `/etc/mailrc' and `~/.mailrc' |
| files. These files look like: |
| |
| |
| |
| alias lmi "Lars Magne Ingebrigtsen <larsi@ifi.uio.no>" |
| alias ding "ding@ifi.uio.no (ding mailing list)" |
| |
| After adding lines like this to your `~/.mailrc' file, you should be able |
| to just write `lmi' in the To or Cc (and so on) headers and press SPC to |
| expand the alias. |
| |
| No expansion will be performed upon sending of the message--all |
| expansions have to be done explicitly. |
| |
| If you're using ecomplete, all addresses from To and Cc headers will |
| automatically be put into the `~/.ecompleterc' file. When you enter text |
| in the To and Cc headers, ecomplete will check out the values stored |
| there and "electrically" say what completions are possible. To choose one |
| of these completions, use the M-n command to move down to the list. Use |
| M-n and M-p to move down and up the list, and RET to choose a completion. |
\===========================================================================/
Of course, bbdb has it's own way of dealing with mail aliases.
hth
Glyn
next prev parent reply other threads:[~2013-06-24 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 19:54 Harry Putnam
2013-06-24 20:36 ` Glyn Millington [this message]
[not found] <mailman.2330.1372103802.22516.info-gnus-english@gnu.org>
2013-06-25 20:37 ` Emanuel Berg
2013-06-25 20:43 ` Emanuel Berg
2013-06-28 0:23 ` Harry Putnam
[not found] ` <mailman.2642.1372379088.22516.info-gnus-english@gnu.org>
2013-07-16 1:15 ` 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=87bo6vdz5j.fsf@nowhere.org \
--to=glyn.millington@gmail.com \
--cc=info-gnus-english@gnu.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).