similar to: Maildir++ implementation issues.

Hi, Am seeing an odd problem on an old FreeBSD 4.11 box that I'm trying to get courier off, and dovecot on. At the same time, I'm trying to put some fairly simple quota support on, but getting very odd results. I think it might be better described with the log below, but, the gist of it is this: I have set a 1GB quota, and I was getting intermittent reports on the quota usage -

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 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,

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

> 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

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

Does this Maildir++ implementation have an "unlimited" quota? It looks like all of the other Maildir++ software uses "0" for this ... it doesn't seem to work on Dovecot. Steve

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

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

Running RC2 with maildrop and MDA: dovecot writes a positive quota count, then the negative quota count on messages delivered with maildrop. For example, message #1 arrives via maildrop: 4488236 1 message is deleted via dovecot: 4488236 1 -4488236 -1 This does not happen when the user accesses the message, only when it is deleted. The user never gets credit for deleting

Hello all, We are using Horde/IMP and we are having problems deleting messages from accounts where the user is very close to going over quota. My test environment includes: Horde 3 IMP 4.1.2 dovecot 1.0rc2 postfix maildrop I created a user and set the quota at 13MB. I then sent a 10MB file to the user - which was received. However, when I attempt to move the message from the INBOX to

Hello just to have up2date records: Is the current dovecot release capable of the maildirsizefile as described in http://www.exim.org/exim-html-4.63/doc/html/spec_html/ch26.html#id2643923 ? Regards Marten

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.

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

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

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

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

Greetings. Im about to move from mbox to Maildir++ and change the deliver method from procmail. I have less than 100 accounts, but there's a lot of mail (around 16GB) Apart from the documentation on Dovecot's site, anyone has good recommendations, and, if you have experience doing this migration any tips? Thanks for any info, and wishing you all a nice week --

On Sun, 23 Aug 2015, Hadmut Danisch wrote: > astonished to see, what problems come with Maildir++ and how complicated > dovecot tries to deal with them. .. [fast fwd to "solution"] > INBOX -> ~/mail/inbox > abc -> ~/mail/abc > abc/def -> ~/mail/abc.dir/def or ~/mail/___abc___/def This would not work. For example, how would you handle a folder