From: Kirk Strauser <kirk@strauser.com>
Subject: Re: IMAP splitting problems with Exchange server
Date: Tue, 06 Jan 2004 16:14:54 -0600 [thread overview]
Message-ID: <87wu84rag1.fsf@strauser.com> (raw)
In-Reply-To: <87k744225d.fsf@emptyhost.emptydomain.de> (Kai Grossjohann's message of "Tue, 06 Jan 2004 22:33:18 +0100")
[-- Attachment #1: Type: text/plain, Size: 2047 bytes --]
At 2004-01-06T21:33:18Z, Kai Grossjohann <kai@emptydomain.de> writes:
> Kirk Strauser <kirk@strauser.com> writes:
>
>> My "test" group was originally named "Mailing lists/Zope", but I thought
>> that the "/" might be causing the problem, so I created the new "zope.user"
>> group and moved all of the "Mailing lists/Zope" messages into it.
> Hm. It could be the space that's causing trouble, actually. Does the
> new group have a space in it?
No. I created it from Gnus, and it's whole "specification" is
"nnimap+lan:zope.user".
> Are you sure the new group is named zope.user and not INBOX.zope.user?
Yes.
> What does RET on the server in the server buffer say about it?
It lists all of the expected groups on the server, including "zope.user".
> Maybe you don't have permissions on the group? G l tells you about it.
Response:
gnus-group-nnimap-edit-acl: Server does not support ACL's
I have a lot of strangely-named groups because this mailbox was first
accessed with Outlook, then KMail, then Evolution, then Thunderbird, then
Gnus (I *always* come back - I don't know why I even bother to look around
:) ). However, the two groups in question are "INBOX" and "zope.user"; no
spaces, slashes, or any other strange characters. I tried renaming the
recipient folder to just "zope" with no perceived difference in behavior.
Furthermore, although I can't use 'B r' to respool, I *can* use 'B m' to
move mail into the folder:
Moving to nnimap+lan:zope: (1508)...
Expiring articles in nnimap+lan:INBOX
gnus-agent-expire: Loading overview... Done
gnus-agent-expire: Sorting entries... Done
gnus-agent-expire: Merging entries... Done
gnus-agent-expire: nnimap+lan:INBOX:1508: Removed read article number from article alist, NOV entry removed
Expiry recovered 1 NOV entries, deleted 0 files, and freed 371.000000 B.
nnimap: Setting marks in zope...done
nnimap: Updating info for nnimap+lan:zope...done
Auto-saving...done
--
Kirk Strauser
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2004-01-06 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 20:01 Kirk Strauser
2004-01-06 21:33 ` Kai Grossjohann
2004-01-06 22:14 ` Kirk Strauser [this message]
2004-01-07 8:31 ` Kai Grossjohann
2004-01-07 15:21 ` Kirk Strauser
2004-01-07 8:54 ` Yair Friedman
2004-01-07 15:30 ` Kirk Strauser
2004-01-07 19:20 ` Simon Josefsson
2004-01-07 22:00 ` David S Goldberg
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=87wu84rag1.fsf@strauser.com \
--to=kirk@strauser.com \
/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).