Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Cannot write to write-only IMAP mailbox
Date: Tue, 14 Apr 2009 16:03:20 -0500	[thread overview]
Message-ID: <86iql7lzhj.fsf@lifelogs.com> (raw)
In-Reply-To: <87tz5dyo5m.fsf@nokile.rath.org>

On Sat, 28 Mar 2009 23:59:49 -0400 Nikolaus Rath <Nikolaus@rath.org> wrote: 

NR> I reported this bug a while ago and there has been no reply at all. I
NR> just wanted to bring the issue up again in case someone has some time
NR> available now that he might be willing to spend on this:

NR> On my IMAP server I have a group called "unrecognized-ham" that cannot
NR> be read by anyone, but can be looked up and inserted to by anyone. As
NR> the name suggests, mail in this folder is automatically analyzed to
NR> correct mistakes made by a bayesian spam classifier.

NR> Unfortunately it is not possible to access this group with gnus. When
NR> I am in a different IMAP mailbox and try to copy a message with B c,
NR> gnus complains that the group does not exist. Any attempt to create it
NR> fails of course. Also I cannot see the group when using group apropos
NR> and I cannot subscribe to it with U.

NR> In Thunderbird, there is no problem at all. The group is visible and I
NR> can copy messages into it.

It seems the problem is here:

> 49 EXAMINE "Shared.unrecognized-ham"
> 49 NO Permission denied

So nnimap tried to look at the contents of the group before writing to
it.  This can probably be avoided for this special case, and is most
likely happening in imap-mailbox-select.  Could you provide the nnimap
logs (obtained similarly to the imap logs)?

Thanks
Ted




  reply	other threads:[~2009-04-14 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29  3:59 Nikolaus Rath
2009-04-14 21:03 ` Ted Zlatanov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-10 22:56 Nikolaus Rath
2008-09-11 12:59 ` Ted Zlatanov
2008-09-11 16:31   ` Ted Zlatanov

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=86iql7lzhj.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).