Displaying 20 results from an estimated 10000 matches similar to: "Dovecot - Issue with Maildir++ quotas"
2006 Sep 07
1
quota plugin enhancement request
Hi am having a small issue with the quota plugin
In Squirrelmail when a message is deleted, it seems to be copied to the
Trash folder *before* it is deleted from the current folder. However if
it is a large message being deleted and the mailbox is close to its
quota limit, it means dovecot will deny the copy operation as the quota
will be exceeded if the message is copied
Because of this, I
2006 Mar 09
3
Getting maildir++ quotas working
Can somebody post details for how to get maildir++ quotas working in the
latest CVS?
I have tried but can't get the CAPABILITY string to show "QUOTA"; and the
GETQUOTAROOT command is recognized, but returns nothing...
2 GETQUOTAROOT INBOX
* QUOTAROOT "INBOX" ""
* QUOTA "" ()
2 OK Getquotaroot completed.
These are the settings I have... am I
2006 Aug 31
2
Maildir++ quota inconsistency
I've found what I think is an inconsistency in the Maildir quota
implementation. According to the Maildir++ quota specification at:
http://www.inter7.com/courierimap/README.maildirquota.html
Maildir++ quota can be specified as maximum size, or maximum number of
messages, or even both. The size specification is supposed to be in bytes.
So I could use '10000000S' to set a quota of
2008 Oct 17
2
Dovecot 1.1.4 / Maildir++ quota and move to trash
Hello,
Seems there is some nasty problems with Dovecot 1.1.4...
We use Maildir++ quota, and when moving mail to Trash, Dovecot just
drop the connection... when the maildir is overquota.
Is there any way to avoid that and just move the mail to the trash
allowing user to expunge their mail easily without calling support to
do rm -rf Maildir/cur ?
Thanks,
/Xavier
-------------- next part
2008 Sep 10
2
Question about subfolders
Hi,
I've got an old dovecot installation (0.99.10.5) which
is used as the back-end for a squirrelmail web mailer.
Now I need to decide whether to update it to a newer
version of dovecot or to switch to a different software.
One feature that I really need is to be able to place
messages and subfolders in a folder at the same time.
This is with mbox format files (I can't use maildir).
The
2006 Jul 14
2
maildir++ specification compliance.
Hi folks.
I was doing some testing this morning and realized Dovecot RC2 isn't fully
compliant with the maildir++ specification.
Most notably, it appears that Dovecot isn't creating a "maildirfolder"
file (0 byte length) in folders it creates.
>From http://www.inter7.com/courierimap/README.maildirquota.html
"Within each subdirectory there's an empty file,
2015 Aug 23
3
Shortcomings of Maildir++ layout
Hi,
I am trying to deal with the problem, that under regular mbox format a
path can lead to either a file or a directory, but not both, while under
IMAP, a path is usually both, a message folder containing subfolders.
I found dovecot's approach to this problem, the Maildir++ layout
described under http://wiki2.dovecot.org/MboxChildFolders , and was
astonished to see, what problems come with
2004 Sep 07
1
[Fwd: Maildir++ support]
> In the homepage said that dovecot doesn't yet support maildir++, but in
> http://dovecot.org/doc/mail-storages.txt said 'we support maildir++'.
>
> My question is: does dovecot support maildir++ ?
>
> Regards
> mike
2009 Jun 06
1
LAYOUT=fs vs LAYOUT=maildir++ and quota
Hi everyone.
I'm confused about LAYOUT=fs...
Does using LAYOUT=fs breaks maildir++ quota, if I use this quota scheme?
What are the advantages anyway of using LAYOUT=fs vs LAYOUT=maildir++ ?
(it's not important in my case if users can't create folders with dots '.')
Thanks in advance,
Ezequiel
2019 May 14
2
Userdb userdb_mail=, error Mailbox list driver maildir++: maildir_name not supported by this driver
Yes, I have still inbox mbox format because I have sendmail delivering
there. I trying to migrate/convert
step by step, with least possible impact for users.
-----Original Message-----
From: Aki Tuomi
Sent: dinsdag 14 mei 2019 6:19
To: Marc Roos; Marc Roos via dovecot
Subject: Re: Userdb userdb_mail=, error Mailbox list driver maildir++:
maildir_name not supported by this driver
> On
2007 Mar 01
1
Deleting when Over Quota
Hi All,
I've read a bit about this but don't really see a full solution
anywhere. Has anyone actually got a good fix for this?
Telling a user they are over quota then not allowing them to delete
anything does seem the height of perversion. =)
Question is - is this even a problem for the IMAP server? Or should the
MUA be detecting over quota problems and then issuing the right
2007 Oct 25
2
few questions about 1.1*
Hi!
I'm testing 1.1, and have some questions.
(How) Can I override the default maildir++ quota setting (I mean
quota_rule) in the userdb, so that one won't have quota at all. Right
now I'm setting a very high limit in the userdb with
quota_rule=*:storage=99G in the extra field.
Prior to 1.1 I was using 1.0 and had fs quota. I've had set up dovecot
so that the indexes were
2010 Sep 06
1
LAYOUT=maildir++ under mbox?
Whilst documenting LAYOUT=maildir++ under dbox, that got me thinking:
Can we specify :LAYOUT=maildir++ with mbox?
If I have it right, this should then remove the problem of not being
able to have messages and mail subfolders in the same mail folder.
So for example if we had mail location specified as:
mail_location = mbox:~/mail:LAYOUT=maildir++
we would have files:
~/mail/inbox - file
2008 Oct 06
2
Maildir++ problem
Hi to all,
I am semi-new to the dovecot system, but i like it very much for the
versatility of all the system. I have a problem: i am migrating my
servers from postfix with vda patch + courier imap to dovecot. All works
fine, except for one thing: i use Maildir++ format, but i don't know how
to make the file maildirsize into the home of the users. This file is
needed by me becouse i have a
2019 May 13
2
Userdb userdb_mail=, error Mailbox list driver maildir++: maildir_name not supported by this driver
I have this default configuration [0], when use the userdb_mail to point
to the mdbox location, the inbox subfolders show differently in a
firebird client. So I decided to copy the whole default mail_location
into the userdb_mail configuration [2]. But then I get errors [3].
Should I change the namespace configuration here, how? My default
namespaces are inbox and 4archives
[0]
[@ ]#
2019 May 14
1
Userdb userdb_mail=, error Mailbox list driver maildir++: maildir_name not supported by this driver
With this setting, all folders are empty, I guess understandable,
because the mdbox has its own indexes stored locally with it. Does not
explain though why inbox is empty.
[@ dovecot]# cat special-userdb
test:x:8267:231:Account with special settings for
dovecot:/home/popusers/test:/bin/false:userdb_mail=mdbox:~/mdbox:INBOX=/
var/spool/mail/%u:INDEX=/var/dovecot/%u/index
With this setting
2006 Jun 22
0
maildir++ Quotas - bizarre behavior.
Hi Timo et al.
I've been trying to track down why Dovecot recalculations of maildirsize
are so wildly different (lower) than what Maildrop comes up with.
I think I've found some bizarre behavior in Dovecot -- this is in beta9 as
well as CVS from yesterday.
It appears Dovecot isn't looking at /Maildir/cur ... /Maildir/new and
/Maildir/tmp. It is, however, looking at
2009 Oct 28
3
expire plugin + --exec-mail in 1.2.6 version
Hello list,
After upgrade to dovecot version 1.2.6 I have noticed some quota malfunctions(users become often overquota). Looking at logs closely I have found that quota value resets to general dovecot-config(
quota = maildir:Mailbox quota
quota_rule = *:storage=500M
quota_rule2 = Trash:storage=10%%
), after dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool.sh command. The problem that
2016 Feb 19
2
Maildir++ and fs-layout
Dear All,
can I use Maildir++ Layout for private namespace and fs-layout for public
namespace on the same server, provided that the hierarchy separator is the
same (.)?
Are all parts of dovecot (especially deliver, sieve and lmtp) compatible
with fs-layout? Are there any restrictions I have to obey?
- Chris
2015 Nov 18
2
Shortcomings of Maildir++ layout
> Sounds more like you just introduced a new self-created problem that
would require yet another workaround.. ;-)
Definitely wrong.
Appending .dir to directories and .folder to folder files keeps files
completely distinct and name collissions are not possible.
> But what was not clear from your mail, is what exactly you identified
as "the problems" with standard Maildir++