Can't SELECT mailbox as admin on frontend (Murder)
Etienne Goyer
etienne.goyer at linuxquebec.com
Wed Dec 17 15:24:17 EST 2003
If you mean a telemetry log on the backend, here it is :
---------- admin Wed Dec 17 15:13:41 2003
<1071692021<C2 Capability
>1071692021>* CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE LOGINDISABLED MUPDATE=mupdate://xxx.xxx.xxx.xxx/
C2 OK Completed
<1071692021<. Select {12+}
user/test123
>1071692021>. NO Mailbox does not exist
<1071692025<L01 LOGOUT
>1071692025>* BYE LOGOUT received
L01 OK Completed
On Wed, Dec 17, 2003 at 03:00:29PM -0500, Ken Murchison wrote:
>
>
> Etienne Goyer wrote:
>
> > Hi,
> >
> > I can't SELECT mailbox on a frontend in a Murder when logged in as an
> > admin account. Example :
> >
> > * OK frontend1 Cyrus IMAP4 Murder v2.1.15 server ready
> > . login admin *******
> > . OK User logged in
> > . select user/test123
> > . NO Mailbox does not exist
> > . logout
> > * BYE LOGOUT received
> > . OK Completed
> >
> > Obviously, I have check user/test123 exist. Actually, when I connect
> > directly to the backend where it reside, I can SELECT it no problem.
> >
> > Also, as user test123, I can't SELECT user/test123 ("NO Mailbox does not
> > exist" too), but I succeed when I SELECT INBOX.
> >
> > Could this be related to altnamespace ? If not, what else could cause
> > this problem ?
>
> I *believe* that these issues have been resolved in 2.2. If you can
> grab a protocol dump of what is being sent to the backend, it might shed
> some light. My guess is that the mailbox name is being sent in the
> internal format, rather than the external one.
>
> --
> Kenneth Murchison Oceana Matrix Ltd.
> Software Engineer 21 Princeton Place
> 716-662-8973 x26 Orchard Park, NY 14127
> --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
--
Etienne Goyer Linux Québec Technologies Inc.
http://www.LinuxQuebec.com etienne.goyer at linuxquebec.com
More information about the Info-cyrus
mailing list