From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Problem with archiving and nnimap
Date: Tue, 17 Sep 2002 19:08:23 +0200 [thread overview]
Message-ID: <ilulm60bl2w.fsf@latte.josefsson.org> (raw)
In-Reply-To: <vafit14sqbc.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 17 Sep 2002 15:23:19 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Niklas Morberg <niklas.morberg@axis.com> writes:
>
>> Simon Josefsson <jas@extundo.com> writes:
>>
>>> That variable result in a GCC header in the message buffer,
>>> does it not?
>>
>> Sure.
>>
>>> How does that header look like?
>>
>> Gcc: ""nnimap+my.mail.server:Sent Items""
>
> THat's one pair of double quotes too many. Maybe the modification
> adds its own double quotes automatically, so you can remove your
> double quotes from the variable.
Yup, I've improved the NEWS entry. I hope this breach of backwards
compatibility is worth it, opinions?
** Group Carbon Copy (GCC) quoting
To support groups that contains SPC and other weird characters, groups
are quoted before they are placed in the Gcc: header. This means
variables such as `gnus-message-archive-group' should no longer
contain quote characters to make groups containing SPC work. Also, if
you are using the string "nnml:foo, nnml:bar" (indicating Gcc into two
groups) you must change it to return the list ("nnml:foo" "nnml:bar"),
otherwise the Gcc: line will be quoted incorrectly. Note that
returning the string "nnml:foo, nnml:bar" was incorrect earlier, it
just didn't generate any problems since it was inserted directly.
next prev parent reply other threads:[~2002-09-17 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 7:40 Niklas Morberg
2002-09-17 9:00 ` Frank Schmitt
2002-09-17 9:10 ` Niklas Morberg
2002-09-17 10:35 ` Simon Josefsson
2002-09-17 10:58 ` Niklas Morberg
2002-09-17 13:23 ` Kai Großjohann
2002-09-17 14:00 ` Niklas Morberg
2002-09-17 14:18 ` Kai Großjohann
2002-09-17 17:08 ` Simon Josefsson [this message]
2002-09-18 5:55 ` Niklas Morberg
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=ilulm60bl2w.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--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).