similar to: Maildir++ Unlimited Quota.

Hi. It looks like Beta 7 is treating a zero quota in maildirsize as a literal quota value. The maildir++ specification says a zero quota means unlimited. Steve

Hi Timo. I saw the "0" quota should be interpreted as unlimited in the ChangeLog from yesterday's snapshot. I just tested and it's still seeing zero as zero. I am unable to append any messages. Can you double-check this feature? Thanks! Steve

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

Some information about maildir++ that I have read: http://www.inter7.com/courierimap/README.maildirquota.html http://wiki2.dovecot.org/Quota/Maildir When I have to deliver a message with an MDA I can use dovecot-lda. If I have enabled "quota = maildir:User quota" I am pretty sure that in the mailbox on file system I find a file named "maildirsize" maildirsize on top contain

Hi there, I'm using postgres as a userdb for dovecot. I'm am trying to get the quota plugin to work. I have a column in my table that returns the quota in KB. I am using the postgres expression "('maildir:storage=' || mailstore_control.mailbox.quota) AS quota" as recommended in the manuals. This expression is NULL to start with, which I take to mean unlimited

Hello, I'm using dovecot-0.99.14, and I wonder if anyone has created patch for *minimal* Maildir++ support. By minimal Maildir++ support, I mean the following: (1) New messages created by dovecot will include the ,S=nnnnn string in the unique identifier so that Maildir++ clients don't have to stat the file to know the size. (2) Dovecot will append to the maildirsize file when a message

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

Hello, I?m using Dovecot 2.0.1 with quota support (quota and imap_quota) which works perfect. However, I?d like to give some mailboxes unlimited quota. What quota setting (in the backend (SLQ)) is needed to tell Dovecot as LDA that the mailbox has unlimited quota? 0 or NULL or -1 or something else? Regards Patrick

We are configuring 'Count quota' with 'Quota Clone Plugin' Everything is working perfectly when we set limit in quota_rule(quota_rule = *:bytes=500M). In case of unlimited quota(quota_rule = *:bytes=0) - Count quota is updating values * - Quota Clone plugin is not updating values in redis.* We have configured dovecot as mail_plugins = $mail_plugins quota quota_clone mail_log

While researching a possible bug in our custom-made Maildir++ expiration script, I found the following in src/plugins/quota/quota-maildir.c. | static const char * | maildir_list_next(struct maildir_list_context *ctx, time_t *mtime_r) | { | [...] | *mtime_r = st.st_size; | return str_c(ctx->path); | } As far as I unterstand, this seems incorrect, because the value in mtime_r is

We use Maildir++ quota, with the rules taken from our LDAP backend. We also have an old expunge script that's not quota-aware; it removes old messages from the maildir by simply deleting the files. Sometimes, a mailbox is over quota before the script runs, but well under quota after the old messages are deleted. This change does not seem to be picked up, however: When I try to deliver a new

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

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,

Hi all, I use Dovecot lda. Is there the possibility that dovecot lda works with maildir++ but does not enforce the quota? I have dovecot 1.0rc12, postfix, RedHat Enterprise Linux ES 4.0 Update 4. IMAP client Thunderbird 1.5.0.7 Only namespace: namespace private { separator = / inbox = yes prefix = location = maildir:~/Maildir/ } Thanks a lot.

Hi, I've been bitten by an issue running Squirrelmail on top of Dovecot using Maildir++ quotas. Having configured these quotas in Dovecot, I notice that Dovecot appears not to exclude the 'Trash' folder from its quota calculation (which it should do, according to the Maildir++ spec). Unfortunately this breaks Squirrelmail if I try to delete a message from a close-to-quota

How do I set an unlimited quota for a user in 1.1? Setting it to 0 bytes worked in 1.0, but doesn't seem to work in 1.1 :-( david

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

Hi. I have an strange problem with dovecot's maildir quota and postfix. I've tested quota and it works fine but sometimes there are users that having their Maildir/ empty, they trigger the "quota exceeded" message when someone sends email to them. Some config / version info: ### Versions: ii dovecot-common 1:1.0.10-1ubuntu5.1 ii dovecot-imapd

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

Hi all. I have a problem with one user. His quota is upper of real quota. # cd /var/mail/problemuser/ # find . -name 'dovecot*' -exec rm -f {} \; # find . -name 'maildir*' -exec rm -f {} \; # echo test | mail problemuser -s test # more maildirsize 104857600S 104215602 1439 647 1 # du -h 4,0K ./.Borrador/new 4,0K ./.Borrador/cur 4,0K ./.Borrador/tmp 16K ./.Borrador