similar to: Namespace prefix not ending with separator

Displaying 20 results from an estimated 2000 matches similar to: "Namespace prefix not ending with separator"

2012 Jun 08
1
how to announce shared folders to clients using non-default mail prefix
We're using dovecot 2.1.3 and I've been doing some testing with 2.1.7. We have shared mail (maildir) folders working along with our default mbox mailboxes. Our problem is trying to get this to work in a reasonable fashion with our iPhone or iPad mail.app clients. It's well known that they don't honor the subscription list; they show all available mail folders and do not
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
2006 Jan 24
1
Fwd: Weird problem opening mbox in beta1/2
Hmm, this is peculiar! This mailbox has been unchanged on my test server since September. I've been using it to test each new version of Dovecot just after I've compiled it. When beta1 was released, I opened this mbox with no problems. However, when I upgraded to beta2, I got "file size unexpectedly shrinked in mbox file /export/mail/a/24/vis99003/INBOX (16895967 vs 16899267)".
2005 Mar 18
2
Pine and prefix - LIST command bug?
I've been having problems with Pine 4.62 talking to Dovecot 1.0 stable. It's fine when the folder collection path is empty, but if I have "~/mail/" or "mail/" it gives access errors (I'm using the "~/mail/", "mail/" etc. hidden namespaces for backwards compatability). It seems to me that Dovecot is not replying correctly to a "LIST"
2007 Feb 08
2
migration question: "imap server directory"
In prepping our IMAP migration to Dovecot, I've hit upon a small issue: the "IMAP server directory" which Thunderbird users have set in the "advanced" prefs. Our old IMAP server seems to set your current directory to ~. This wound up causing users to set their IMAP server directory to "/home/<user>/mail/" so that their mailboxes would be found: --> A104
2008 Feb 29
2
Query about LIST behaviour
I've just switched from UW-IMAP to Dovecot v1.1.beta16, and I'm having a bit of a problem with a difference in the behaviour of the LIST command. What I'm seeing is: * PREAUTH [CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1] Logged in as jp3 a list test/ * * LIST (\Noselect
2007 Dec 03
3
LIST problem with Dovecot1.1beta10
Hi, Certain IMAP folder problems started popping up with Squirrelmail with the 1.1beta10 version of Dovecot (and possibly earlier versions). Looked into it and I am seeing odd behavior with the LIST command. Here is how to reproduce problem, unless I'm missing something obvious: a001 login dean <password> a001 OK Logged in. a002 list "" * * LIST (\NoInferiors \UnMarked)
2015 Jun 09
0
special_use \Archive not working with some foldernames
Hello list, i use dovecot 2.2.18 compiled on my own and want to report an odd behaviour when using a folder for special_use \Archive. In my case it is not working when using some special foldernames (mbox). I compared to version 2.2.15 which i found pre-packaged on launchpad.net, same behaviour. All other special_use Folder work like expected. My situation: We authenticate users using
2010 Dec 15
1
problem with ~/mail/ namespace
We just changed from UW imap last night and one of our bigger problems right now is that the ~/mail/ compatibility namespace doesn't seem to work. dovecot 2.0.8 Dec 15 12:01:52 zen.engr.oregonstate.edu dovecot: [ID 583609 mail.warning] imap(tom2): Warning: Subscriptions file /nfs/rack/u4/t/tom2/mail/.subscriptions: Ignoring invalid entry: ~/mail/foo1/folder1 Dec 15 12:01:52
2005 Jul 14
0
[Fwd: Re: Dovecot and ActiveDirectory]
Oops! Thought I'd CC'd this to the list. Sorry, Oliver! Chris -------- Original Message -------- Date: Wed, 13 Jul 2005 20:09:35 +0100 From: Chris Wakelin <c.d.wakelin at reading.ac.uk> To: Jeroen Scheerder <Jeroen.Scheerder at phil.uu.nl> CC: Chris Wakelin <c.d.wakelin at reading.ac.uk> Subject: Re: [Dovecot] Dovecot and ActiveDirectory Jeroen Scheerder wrote: >
2005 Nov 03
0
FW: How to log POP3 events
Ok, I think I have that figured out. I made the following mods: disable_plaintext_auth = no pop3_uidl_format = %08Xu%08Xv and it seems to work. Now...about those enhanced logging capabilities. As promised, I see the enhanced logging. What does TOP and RETR mean? (I checked the manual first) Cliff -----Original Message----- From: Cliff Hayes [mailto:chayes at afo.net] Sent: Thursday,
2008 Oct 16
2
Problem with namespaces
[1.1.4 with http://hg.dovecot.org/dovecot-1.1/rev/b61424a50786 applied] I'm trying to use namespaces as described here for UW-IMAP compatibility: http://wiki.dovecot.org/Namespaces But I'm getting a problem with the hidden namespaces showing up in the LIST output. Here is a simplified transcript. The ~/Mail folder contains just two folders. The config given to imapd is as follows:
2005 Mar 22
2
Address with whitespace shows as ""@MISSING_DOMAIN
It seems that Dovecot gets confused when presented with a header like: From: someone at somewhere.org i.e. with leading whitespace and no "friendly name" This shows up as ""@MISSING_DOMAIN in clients, such as Pine, that believe what Dovecot tells them rather than parsing the headers themselves (e.g. Thunderbird). Here's a sample IMAP session: xyz FETCH 728 ENVELOPE
2011 May 21
1
Behavior difference in mbox versus Maildir listing
Hi, My MUA (claws-mail) is having a hard time listing directories for a mail account with two namespaces, one of which using mbox and the other one using maildir to store mails. Let's call the namespaces "#mbox." and "#maildir." and have "." as separator. Assume I have the following folder hierarchy: $namespace $namespace folder $namespace folder folder1a
2008 Oct 13
2
Compatibility namespaces containing a leading ~ appear to be broken in 1.1.x
Greetings, I'm building a new 1.1.x-series Dovecot installation, and I have a problem setting up compatibility namespaces intended to handle old client-side settings. (See also: http://wiki.dovecot.org/Namespaces#head-0f3ab5ecab632eb517866c3508021e0605d54d4d) I have produced a slightly cut-down example configuration which demonstrates the problem: # dovecot -n # 1.1.3:
2003 Sep 03
2
pine, INBOX, and dovecot
Hi all, I've been experimenting with Dovecot; tests with Maildir seemed to work fine. However, now I'm trying with mbox folders, and I'm having a problem where I do not get an INBOX listed using pine. Outlook Express and IMP show it fine. I snooped part of the session, which appears to go like this (it is slightly garbled, sorry -- I couldn't get rawlog to work by creating
2006 Jan 14
2
20060114 snapshot compilation warnings
Timo, I've noticed a couple of extra compilation errors in last night's snapshot compared to the snapshot I downloaded on Tuesday, probably due to the int -> bool change :- (gcc 3.3.2 on Solaris 8) mbox-sync.c: In function `mbox_sync': mbox-sync.c:1568: warning: comparison is always false due to limited range of data type index-search.c: In function `search_index_arg':
2005 Mar 17
1
Namespaces and subscriptions
I've got a problem with subscriptions in 1.0-stable when migrating from UW-IMAP. I've modified the SUBSCRIPTION_FILE_NAME entries as suggested in the Wiki http://wiki.dovecot.org/Migration and included the "~/mail/" etc. hidden namespaces. The .mailboxlist files contain entries like "~/mail/somefolder" and the clients have "~/mail/" set as a prefix. In
2005 Sep 21
1
Another address-spec problem
I've had complaints from users about "MISSING_DOMAIN" in header fields and I've tracked it down to having "." in an unquoted display name. By my reading of RFC2822 (especially section 4.1) A N Other <a.n.other at somewhere.org> "A. N. Other" <a.n.other at somewhere.org> are legal, but A. N. Other <a.n.other at somewhere.org> is
2005 Sep 27
2
How safe is mbox_very_dirty_syncs?
I've tried turning on mbox_very_dirty_syncs for myself (and a few other brave souls running 1.0-alpha3 rather than 1.0-stable) again to see what perfomance gain it gives (see thread http://www.dovecot.org/list/dovecot/2005-July/007956.html). Now we aren't running UW-IMAP at all, how safe is mbox_very_dirty_syncs assuming the only other process writing to mailboxes is our MTA (exim) which