similar to: Help - I keep getting LSUB permission denied

Displaying 20 results from an estimated 1000 matches similar to: "Help - I keep getting LSUB permission denied"

2013 May 10
1
Dovecot 2.2.1 subscribtion status in LIST
Hi there, I am using Evolution to connect to dovecot imap server. Today the server was upgraded to 2.2.1 from 2.1.9, and there is problem with evolution being unable to subscribe to INBOX. This is from dovecot 2.1.9: a002 list "" "*" return (subscribed) * LIST (\Subscribed) "." "Sent Items" * LIST (\Subscribed) "." "Junk E-mail" * LIST
2011 Nov 06
3
2.1: virtual plugin and lsub
Hi Timo, I'm using the virtual plugin and have 2 mailboxes configured in the "virtual" namespace (dovecot -n attached). Using lsub with dovecot 2.0.15 leads to the following result: 1 lsub "" "virtual/*" * LSUB () "/" "virtual/Lists" * LSUB () "/" "virtual/unread" 1 OK Lsub completed. However with dovecot 2.1 (latest hg
2011 Dec 22
2
LSUB and subscribed folders
I have a strange behavior on a customer's server and I don't understand that: User "bar" has some folders and one shared folder from "foo" if I use the "LIST"-command, which should list AFAIK *all* folders: # telnet localhost 143 a login bar xxxx a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES
2011 Sep 15
1
unexpected LSUB / LIST (SUBSCRIBED) output Re: Panic: file mailbox-list-subscriptions.c: line 66 (mailbox_list_subscription_fill_one): assertion failed: (ns!= NULL && (ns->flags & NAMESPACE_FLAG_AUTOCREATED) != 0)
On Thu, 15 Sep 2011, Timo Sirainen wrote: > On Wed, 2011-09-14 at 12:10 +0200, Lutz Pre?ler wrote: > > imap(2717, testuser): Panic: file mailbox-list-subscriptions.c: line > > 66 (mailbox_list_subscription_fill_one): assertion failed: (ns!= NULL > > && (ns->flags & NAMESPACE_FLAG_AUTOCREATED) != 0) > > > Fixed:
2007 Apr 24
1
LSUB "" "" vs LIST "" "" (hacked Apple Mail problem)
The LSUB command does not act like LIST when provided with an empty mask argument. LIST responds with the hierarchy delimiter: * LIST (\Noselect) "." "" OK List completed. whereas LSUB doesn't return anything useful: OK Lsub completed. RFC 3501 doesn't specify what LSUB should do in this case, but Courier IMAP has LSUB act like LIST. The attached patch
2009 Oct 02
1
Problem with LSUB and public namespace
Hi, I'd like to know if the following is normal. I've a setup with 2 namespace (private/public) where each user can use subscriptions. This problem is triggered by claws-mail, which uses LSUB to get subscribed mailboxes: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN] Dovecot ready. . login user password . namespace * NAMESPACE (("INBOX."
2006 Oct 28
2
LSUB and namespaces - how to get rid of multible prefixes
I'm using dovecot 1.0.rc7 and Squirrelmain 1.4.8 using IMAP on a Debian 3.1 Testing system, and I'm having a problem. When Squirrelmail (or other IMAP clients) submits an LSUB "" "*%", dovecot responds with: Request: A004 LSUB "" "*%" Response: * LSUB () "/" "INBOX.Sent" * LSUB () "/" "INBOX.Trash" *
2010 Jan 09
1
Problem in LSUB?
Hi guys, I'm not 100% sure about the dovecot version in the server because I don't have access to it, just an account, but I think it's 1.1-rc4 I'm an email client developer and I have a doubt about the behaviour of LSUB that I think it's buggy. See this chat with the server 40 LIST "" INBOX * LIST (\HasChildren) "." "INBOX" 40 OK List
2005 Apr 11
1
LSUB matches prefix bug?
I think I've found a minor bug in the LSUB command: . LSUB "" "*" gives ... * LIST (\Noselect) "/" "#maildir" ^^^^ * LSUB () "/" "#maildir/test4" where I have a namespace with prefix "#maildir/". Here's a patch to make it not list the namespace prefix in an LSUB command (or should it list it as 'LSUB
2008 May 06
1
A previously unreported lsub/list discrepancy in 1.1rc5 and earlier
Not sure about 1.0, I don't run it anymore :) But a few users discovered for a small issue that only affects a very small portion of my userbase where instructional correction will suffice. I guess I am reporting it in the interest of getting it out there, and I can live with it if not fixed but it might be an issue for some people. I'm running through my list of issues. Basically,
2010 Jan 31
2
LSUB output format != LIST output format
Hi, I have a problem with my hanging claws-mail. I first subscribed to their bug tracker, described the problem and before I pressed on submit in their bugtracker, I realized it might be a problem with dovecot. I'm using dovecot for internal purposes only (catching all my external boxes and storing locally): # 1.2.8: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-RELEASE-p5 i386 listen: *,
2007 Jun 18
2
LSUB/SUBSCRIBE under namespaces
Hi folks. Here's our situation: Migrating from UW-IMAP. Have lots (as in, tens of thousands) of clients set up using '~/mail' as the IMAP root, and using subscriptions. Dovecot mail_location is using '~' for mbox storage. We've disabled full filesystem access in Dovecot in order to use ACLs for shared folders. Hence we have a hidden namespace for backwards
2010 Nov 22
1
"list" ACL privilege ignored for LSUB command?
Hello, I am new to this list, so feel free to correct me if I do something wrong. I don't have a problem, just a question. The RFC which covers IMAP ACLs [1] states that one of the standard rights is: l - lookup (mailbox is visible to LIST/LSUB commands, SUBSCRIBE mailbox) If I have a shared or public namespace and have a mailbox for which I do not have lookup rights, Dovecot
2007 Jan 23
2
rc18 dies with Query: LSUB "" "*" failed on Squirrelmail
Just upgraded, and then had to downgrade straight away. Couldn't get our Squirrelmail page up. Logged in fine etc. but got: Query: LSUB "" "*" failed, refer to server logs etc. Nothing in logs that shows error with mail_debug=yes What should I be looking for? Gavin. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44
2004 Jul 26
1
bug in LSUB command
RFC 2060 section 7.2.2 and 7.2.3 says the "The LIST response occurs as a result of a LIST command." and "The LSUB response occurs as a result of an LSUB command." Dovecot presently returns the LIST response for the LSUB command. -- Geo Carncross <geocar at internetconnection.net> Internet Connection
2008 Aug 16
2
Problem with squirrelmail and dovecot 1.1
Hello! I'm running squirrelmail 1.4.8 (I know this is not the latest version) and know I'm having troubles with: 1.) Folder list view 2.) Save to sent or Drafts folder. Configuration worked well. I think it has to do with the upgrade from dovecot 1.0 to 1.1 and the LIST command. Thunderbird/alpine work well. Commands from rawlog are: A002 LIST "" "~/Mail/Drafts"
2011 Mar 07
1
Patch proposition to implement a new workaround: tb-lsub-flags
Hi again Timo, As agreed earlier tonight, you'll find as attachments 4 diffs (diff -u) implementing the new workaround "tb-lsub-flags". The 4 impacted files are: ./src/imap/imap-settings.h ./src/imap/imap-settings.c ./src/imap/cmd-list.c ./src/config/all-settings.c Here is the proposed description for the dovecot.conf file: # tb-lsub-flags: # Usually IMAP servers don't
2009 Feb 11
1
v1.2: Can't subscribe to shared user folder
Hi *, I stumbled across a small bug (missing feature?) in the new shared name space stuff: a001 list "" "*" * LIST (\Noselect \HasChildren) "/" "user" * LIST (\Noselect \HasChildren) "/" "user/bob at example.com" * LIST (\HasChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "INBOX/bar" * LIST
2007 Jan 31
1
Query: LSUB "" "*" still on rc19
Hi all, We've downgraded to rc17 for the past week or so, as when we upgraded to rc19, this error did go, but came back again. ERROR: Could not complete request. Query: LSUB "" "*" Reason Given: Internal error occurred. Refer to server log for more information. Looks like it never helped us in rc19. Back on rc17 just now, which we still have to restart a few times a day,
2014 Sep 09
1
My Dsync isn't replicating 'EXPUNGE' IMAP command
Hi! I have two Dovecot-2.2.13 servers with Dsync Replication: server1 and server2. When I execute 'EXPUNGE' on server1 side, the messages with FLAG \Deleted are expunged only on server1. The message is still present in Server2. Could someone give me a hint reason for this ? Thanks in advance! -- Thiago Henrique ======================================================================