Something that's annoyed me for a while is the way bounce_message handles multiple addresses inconsistently from forward_message or mail. If I use the f (forward_message) or m (mail) commands, mutt allows me to use either a comma or whitespace to separate multiple addresses. The b (bounce_message) command however does not recognize whitespace as a separator, and I must use a comma to separate addresses.
If, at the "Bounce message to:" prompt, I specify two local addresses separated by a space, e.g. "racl1 racl2", mutt will concatenate the two addresses and attempt to send to "racl1racl2@<local domain>". If I specify two addresses with FQDNs separated by a space, e.g. "[email protected] [email protected]", mutt returns "Error parsing address!". Both of these examples do the correct thing if used with forward_message or mail. If only for consistency's sake, it would be nice if bounce_message behaved like forward_message and mail in this regard. Below is a one line patch that allows bounce_message to work like forward_message and mail, but may not be the "proper" fix since mutt_parse_adrlist() calls rfc822_parse_adrlist() which has already been called a few lines above this code. Opinions? Any chance of getting this added to the official dist? Roger diff -rc Orig/mutt-1.5.23/commands.c mutt-1.5.23/commands.c *** Orig/mutt-1.5.23/commands.c Wed Mar 12 12:03:45 2014 --- mutt-1.5.23/commands.c Fri Jun 20 12:50:53 2014 *************** *** 292,298 **** return; } ! adr = mutt_expand_aliases (adr); if (mutt_addrlist_to_idna (adr, &err) < 0) { --- 292,298 ---- return; } ! adr = mutt_expand_aliases (mutt_parse_adrlist (NULL, buf)); if (mutt_addrlist_to_idna (adr, &err) < 0) {
