similar to: Possible bug in Maildir++ quota?

Displaying 20 results from an estimated 100 matches similar to: "Possible bug in Maildir++ quota?"

2009 Feb 04
1
location of temporary files in deliver
deliver has the following: -- -- -- /* After buffer grows larger than this, create a temporary file to /tmp where to read the mail. */ #define MAIL_MAX_MEMORY_BUFFER (1024*128) ... static struct istream *create_raw_stream(int fd, time_t *mtime_r) ... input = i_stream_create_seekable(input_list, MAIL_MAX_MEMORY_BUFFER,
2009 Jan 14
2
Maildir++ quota: When is it recalculated?
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
2013 Jun 05
2
dovecot and time
I found something interesting via strace. lda is writing a timestamp with utime before doign the fsync, but I'm really not a C guy, so I have no idea why that's going on via procmail and not via commandline. I assume it's related to the choice of pread64 vs read. when called from commandline (working): read(0, "July 14-20, 2013\n10 courses. Bon"..., 4096) = 4096
2018 Apr 17
2
Postfix sendmail cannot be called from Sieve redirect
Sending (in my case: forwarding) messages from Sieve via sendmail does not work with version 2.3.1. I have narrowed it down to this simple test case: # dovecot -n # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # OS: Linux 4.4.0-119-generic x86_64 Ubuntu 16.04.4 LTS # Hostname: tuxi.topfen.net first_valid_gid = 200 first_valid_uid = 200 mail_location = mbox:~/mail passdb { args =
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
2005 Apr 21
0
minimial maildir++ quota for dovecot-0.99
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
2006 Apr 20
0
Maildir++ Unlimited Quota.
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
2006 Apr 17
1
Beta 7 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
2006 May 02
1
"0" quota and Maildir++
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
2006 Jun 12
1
Maildir++ implementation issues.
Hi Timo and crew! I'm doing more testing with Dovecot and Maildrop today and have run across some strangeness. It appears as if Maildrop stores updates to the maildirquota file in a way that causes Dovecot to ignore them. In my test scenario, Dovecot just rebuilt my maildirsize file to the following: 0S 86213796 108 After delivering a few messages through Postfix -> Maildrop and have
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
2006 Jul 13
1
maildir++ quota bug...
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
2006 Jul 18
1
Maildir++ quota - how to handle a full mailbox
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
2006 Oct 26
1
Maildir++?
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
2006 Nov 07
2
dovecot lda works with maildir++ but does not enforce the quota?
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.
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
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
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
2011 Apr 12
1
Best practices to migrate from mbox to Maildir++ and also changing the deliver method
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 --
2014 Oct 28
0
maildir++ quota support on dovecot
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