Displaying 20 results from an estimated 2000 matches similar to: "namespaces and behaviour of LIST and SELECT with leading ~"
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:
2011 Aug 01
1
Clients can't retrieve new emails
In a formerly working environment suddenly clients aren't notified of
new emails and can't retrieve new emails. Server is Ubuntu 11.04 dovecot
1.2.15. Clients which fail are a Pre2 webOS 2.1 and TouchPad webOS 3.0
(those are OS versions, I don't know which particular flavor/version the
IMAP clients are); there is also a Thunderbird 3.1.11 client on the same
system as the server which
2014 Jan 06
1
Dovecot quoting problem?
Hello Timo,
I think the following commit makes problems:
http://hg.dovecot.org/dovecot-2.2/rev/68a8b650578e
# Doesn't work
A01 LIST "" ~/Mail/Gesendet
# OK with quoted mailbox
A02 LIST "" "~/Mail/Gesendet"
Details:
imap
* PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID
ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS
2004 Jul 20
3
1.0.0-test28 Problem with INDEX
Hi
Using this line in dovecot.conf (ignore linewrap)
default_mail_env =
mbox:%h/IMAP/:INBOX=%h/.email:INDEX=/var/cache/dovecot/%n
The INBOX indexes are being built correctly in /var/cache/dovecot, but
all other indexes for folders are still being built in the user's home
directory.
I had it working once - but it seems fragile - almost as if the config
parser is sensitive to context???
2004 Jul 12
1
dovecot-1.0-test27 crash on FETCH
Hello,
I've got a crash with -test27 on a FETCH, just after logging in. Attached
are the mailbox (1 message only), logs, sniffed session, testcase and core
dump backtrace. If the dovecot.conf is needed, just ask (it's pretty much
the default configuration).
Maybe this has just been fixed in -test28, in which case you can just
delete this email. :)
Btw, it's rather irrelevant, but
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:
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
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)
2005 Apr 11
0
Namespace prefix not ending with separator
I'm still battling my way through using hidden namespaces to hide the
change from UW-IMAP to Dovecot 1.0-stable from my users.
The latest problem is that some (probably many) users have their IMAP
folder prefix set to "~/mail" rather than "~/mail/".
I have hidden namespaces with prefixes "~/mail/", "~%u/mail/" and
"mail/".
LIST
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
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
2006 Dec 08
1
Telnet Listing of IMAP mailboxes
Hello all,
I am trying to figure out why I am can't seem to access any of my mailboxes
that I moved from my OS X machine using UW-IMAP and I followed the
directions on the wiki (http://wiki.dovecot.org/MissingMailboxes) to try and
figure this out. I believe based on what I saw that my client seems to be
the problem, but my question is. Can anyone tell me what the difference
between
2008 Jul 23
1
\HasNoChildren versus \Noinferiors in ACL plugin and no CREATE permission
Hi,
using ACL plugin with dovecot 1.1.1 I expected that a Maildir was listed as
* LIST (\NoInferiors) "/" "Foldername"
if "create" (k) permission is not set in ACLs and there doesn't exists any
subfolders. But to my surprise, dovecot gives the following output:
* LIST (\HasNoChildren) "/" "Foldername"
Therefore the client (here:
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
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
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
2004 Nov 12
0
bug with LIST IMAP command
I am in mbox configuration, and I am getting INBOX listed 3 times.
I suppose the first is /var/mail/login
and the others are $HOME/Mail but they appear twice.
However, it seems this is a bug.
<<
$ telnet localhost 143
Trying 127.0.0.1...
Connected to utopia.priv.
Escape character is '^]'.
* OK dovecot ready.
01 LOGIN login password
01 OK Logged in.
02 LIST ""
2011 Sep 23
1
Strange behavior from shared namespaces and INBOX, probably a bug
Hi,
we have experienced some erratic behavior from Dovecot 2.0.15 if a user's INBOX
is shared.
Some folders of user1, including the INBOX, have been shared using these IMAP commands:
. login user1 XXXXXX
. setacl INBOX user2 lrwstiekx
. setacl box-a user2 lrwstiekx
Now if we use telnet to log in as user2 and select "shared/user1", it will contain the same
mails as
2008 Aug 22
1
Option to evaluate IMAP prefixes relative to $HOME, rather than the IMAP root?
Greetings,
Is there a mechanism (or relatively small source-code change) which would cause
Dovecot to evaluate IMAP prefixes relative to $HOME rather than the configured
IMAP root?
* * *
Background:
We're currently migrating from a WU-IMAP mailserver configuration which stores
user mail in a global NFS-exported $HOME, and we've run into well-known issues
handling client-specified IMAP