From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: nnimap subfolder problem
Date: Tue, 16 Oct 2001 13:41:50 +0200 [thread overview]
Message-ID: <ilud73nolq9.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <vqoitdf25xs.fsf@ubaye.imag.fr> (Nicolas KOWALSKI's message of "Tue, 16 Oct 2001 13:13:51 +0200")
Nicolas KOWALSKI <Nicolas.Kowalski@imag.fr> writes:
> Hello.
>
> At work, I use the nnimap backend, which "talks" to an UW-imapd
> server. My folders are stored using subfolders, like the following:
>
> [ Misc -- 0 ]
> 0: INBOX
> 0: mail/drafts
> 0: mail/sent
> 0: mail/templates
> [ Personal -- 0 ]
> 0: perso/famille
> 0: perso/misc
> [ VERIMAG -- 0 ]
> 0: verimag/hardware
>
>
> My problem is : when I try to rename (G r) the group "perso/famille"
> to something like "perso/famille/misc", Gnus tells me the group has an
> invalid name...I suspect Gnus to not tolerate '/' characters in group
> names, but that is what I need in my case.
>
> Any idea(s) ?
You need to customize the variable below. Does anyone know why `/'
was forbidden in group names? Maybe we can change the default?
`gnus-invalid-group-regexp'
Regexp to match "invalid" group names when querying user for a
group name. The default value catches some *really* invalid group
names who could possibly mess up Gnus internally (like allowing
`:' in a group name, which is normally used to delimit method and
group).
IMAP users might want to allow `/' in group names though.
> PS : I tried to rename "perso/famille" to "perso.famille", this works;
> but then I can not rename it to use subfolders
> ("perso/famille/misc").
Why not? Creating a file perso.famille.misc should work fine, even if
there is a perso.famille file. Perhaps this approach is the easist.
> PS 2: when I use nnml or nnfolder backends, Gnus stores groups using
> subdirectories for group names like "foo.bar.geez" (gives
> foo/bar/geez). Is it possible to use the same functionnality for
> nnimap backend ?
I don't think so, it would mean making `.' and `/' equivalent, and
that is something the IMAP server should do (if at all).
next prev parent reply other threads:[~2001-10-16 11:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 11:13 Nicolas KOWALSKI
2001-10-16 11:41 ` Simon Josefsson [this message]
2001-10-16 12:02 ` Nicolas KOWALSKI
2001-10-16 12:35 ` Simon Josefsson
2001-10-16 13:04 ` Nicolas KOWALSKI
2001-10-16 13:32 ` Simon Josefsson
2001-10-16 13:46 ` Kai Großjohann
2001-10-16 14:01 ` Nicolas KOWALSKI
2001-10-16 18:12 ` Simon Josefsson
2001-10-17 4:27 ` Amos Gouaux
2001-10-16 13:59 ` Nicolas KOWALSKI
2001-10-16 18:27 ` Steinar Bang
2001-12-04 23:48 Kevin Hilman
2001-12-07 14:26 ` Simon Josefsson
2001-12-07 17:23 ` Kevin Hilman
2001-12-07 19:29 ` Simon Josefsson
2001-12-10 19:48 ` Kevin Hilman
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=ilud73nolq9.fsf@barbar.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).