From: Robert Pluim <rpluim@gmail.com>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: ding@gnus.org
Subject: Re: Space in Gcc name taken as list?
Date: Sat, 13 Nov 2021 10:31:15 +0100 [thread overview]
Message-ID: <87k0hccsgs.fsf@gmail.com> (raw)
In-Reply-To: <87v90wd9i5.fsf@emailmessageidheader.nil> (Bob Newell's message of "Fri, 12 Nov 2021 17:23:14 -1000")
>>>>> On Fri, 12 Nov 2021 17:23:14 -1000, Bob Newell <bobnewell@bobnewell.net> said:
Bob> Aloha,
Bob> I have my gnus archive group set to
Bob> "nnimap+imap.gmail.com:[Gmail]/Sent Mail"
Bob> and that works fine.
Bob> However in gnus-alias-identity-alist I have the following
Bob> entry.
Bob> ("jean"
Bob> nil
Bob> "Jean de LaFontaine <jeandelafontaine@bobnewell.net>"
Bob> "Avi Gobbler Publishing" ;; organization header
Bob> (("BCC" . "bobnewell@bobnewell.net")
Bob> ("GCC" . "nnimap+imap.gmail.com:[Gmail]/Sent Mail"))
Bob> nil ;; not \n
Bob> "~/data/elisp/.signaturejean"
Bob> )
Bob> Through msmtp, the "jean" identity uses a different smtp
Bob> account than most of the rest of my mail, so I want the GCC to
Bob> get a copy back to my gmail Sent Mail folder.
Bob> However what actually happens is that "Sent Mail" gets split
Bob> into "Sent" and "Mail" and those groups ("labels" in gmail
Bob> terms) get created on my gmail account, and copies of the
Bob> message put in both of those groups instead of the intended
Bob> "Sent Mail" group.
Bob> I tried to find this in the gnus code but admittedly got
Bob> pretty lost.
In gnus-inews-do-gcc:
(setq groups (message-unquote-tokens
(message-tokenize-header gcc " ,\n\t")))
I think thatʼs a bug. The separator in mail headers is ',' (but Iʼd
allow '\n' here just for convenience).
gnus-summary-resend-message-insert-gcc splits on " ,", but then
inserts with ',' as a separator. I think I rest my case 😁.
Robert
--
next prev parent reply other threads:[~2021-11-13 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 3:23 Bob Newell
2021-11-13 9:31 ` Robert Pluim [this message]
2021-11-13 16:54 ` Bob Newell
2021-11-14 1:22 ` Lars Ingebrigtsen
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=87k0hccsgs.fsf@gmail.com \
--to=rpluim@gmail.com \
--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).