similar to: maildirsize not correct

Thanks, but this is most probably different issue. My maildirsize is computed incorrectly even if I delete it completely and let dovead recompute it so expunging is not in the game. Is there any way how to track/debug the recomputation algorithm in dovecot? On Wed, Aug 24, 2016 at 12:02 AM, WJCarpenter <bill-dovecot at carpenter.org> wrote: > A long shot, but here's how I

On Thursday, February 9, 2017 2:02 PM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > how do you measure the difference? header of maildirsize and output of doveadm quota get -u user at domain.tld Here's another occurence that happened a couple weeks ago on 25-01-2017 (retrieved from a mail I sent to the user and to teammates): in some unit in % of quota

I am using dovecot lmtp root at messagerie[10.10.10.19] ~ # grep virtual_transport /etc/postfix/main.cf # transport_maps = hash:/var/lib/mailman/data/transport-mailman, proxy:mysql:/etc/postfix/mysql-virtual_transports.cf # virtual_transport = maildrop virtual_transport = lmtp:unix:private/dovecot-lmtp root at messagerie[10.10.10.19] ~ # On Thursday, February 9, 2017 7:54 PM, WJCarpenter

Who delievers incoming mail, dovecot LDA or something else? This is what caused a similar problem for me: https://dovecot.org/list/dovecot/2016-April/104091.html

Now this is interesting : du, doveadm quota get and maildirsize have three different values for this particular user : Max Quota is : 1G du : 883M (86%) maildirsize : 1048M (102%) doveadm : 34402? (32%) Trace ----- root at messagerie[10.10.10.19] ~ # cd /var/vmail/domain.tld/m.stefan/ root at messagerie[10.10.10.19] ~ # alias dush alias

I have spent some time this morning trying to add an Astribank to our current Asterisk, but it failed, so I just removed the hardware, restore the config files to the original setup and started asterisk.; I could see that no Zap channels are started so I did load chan_zap.so: pbx*CLI> module load chan_zap.so [Feb 26 10:32:18] WARNING[3809]: pbx.c:2968 ast_register_application: Already have an

Hi, since today some users can not login to my member fileserver. in logs i got this error: [2016/10/10 11:31:28.920022, 10, pid=3809, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth_sam.c:75(auth_samstrict_auth) Check auth for: [oliver.werner] [2016/10/10 11:31:28.920051, 6, pid=3809, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth_sam.c:88(auth_samstrict_auth)

https://bugzilla.samba.org/show_bug.cgi?id=3809 Summary: Feature Request: Individual log file per module Product: rsync Version: 2.6.8 Platform: Other OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

Hello, I'm using mdbox to store messages and maildirsize to store quotas I have the following in my dovecot.conf mail_plugins = quota trash zlib fts fts_squat imap_quota imap_zlib antispam quota = maildir:User quota quota_rule = ?:storage=1G quota_rule2 = Trash:storage=+10%% I noticed that the quotas were wrong, so I sent myself some emails in hope of seeing the ratio change to the correct

Hello all, Recently I have received a few complaints from users that their quota was being reported wrong. This seems to have started when I switched to quota=maildir and ignore=Trash (did both at the same time). The main reported problem is that maildirsize is not correctly updated when they delete messages. My personal hypothesis is something like this: - User moves to Trash - Trash

Hello, Are there plans to implement Maildir++ quotas (maildirsize) in dovecot in the near future? Also - how do things work if you have multiple dovecot frontends accessing an NFS mailstore? If you keep the index files on local disk, and clients connect alternately to different machines, are the stale indexes noticed and corrected? Thanks, Brian.

Hello, I have a problem about updating Maildirsize file. It seems that the Maildirsize file is not updated after user does POP mail from his maildir. I do not want to use any quota limitation in Dovecot. I only want Dovevot to update the Maildirsize file after user retrieves his mail. The Maildirsize file is created by Postfix. Would it be possible to do like this? How can I configure it?

Using maildir++ with LDA and POP/IMAP we have been seeing intermittant maildirsize corruption. Where an operation will be prepended by a handful of ASCI null characters ^@^@. Eg: # cat maildirsize 5120000S -46895 -1 93359 1 60576 1 2858 1 49547 1 -206340 -4 94603 1 84785 1 54463 1 82486 1 97104 1 ^@^@^@^@^@^@^@^@40488 1 73397 1 83662 1 24668 1 42673 1 12081 1 -713606 -12 The instances of this

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. I'm interested to help you with maildirsize virtual quota support. Is there any documented dovecot api? Best regards, - -- Branko F. Gracnar Noviforum Ltd. Software & Media http://www.noviforum.si http://www.najdi.si -----BEGIN PGP SIGNATURE----- iD8DBQFArhbWfiC/E+t8hPcRAtX7AJ9A5ZtSN+6hGQVNLvEjdwV+h2AMBQCfVNem

When using maildir++ quotas, if you delete an IMAP folder, the maildirsize file should get updated so that it subtracts the size of the messages that were contained in the deleted IMAP folder. However Dovecot is not doing this, resulting in Dovecot showing an incorrect quota value until the next time the maildirsize file is rebuilt. Bill

According to [1], Trash is a reserverd folder name. When moving a message to it, maildirsize should be update with a negative byte count. If I move a message from any folder to Trash, maildirsize gets two lines, one positive and one negative. The problem is that a user can't move messages to Trash while being overquota because the positive entry goes before the negative. I'm using

Hello... I'm experimenting with controlling users quota by manipulation the maildirsize files in virtual users (LDAP) homedirs (Is this OK?). This works with IMAP, but deliver via postfix delivers mail to users even if they are over quota. I would like to reject new mails in this case. Any ideas? Thanks, Tobias

Hi all, We're testing Dovecot 1.1rc3, but have run into a snag with IMAP Quota's and the way Trash and Junk folders can be handled. Our MTA (Exim) quota configuration uses this option: maildir_quota_directory_regex = ^(?:cur|new|\.(?!Junk$)(?!Trash$).*)$ This completely excludes "Junk" and "Trash" from the "maildirsize" file and quota calculations.

Dear Timo, I've noticed that since the Courier to Dovecot migration have had few problems with the %usage of email accounts as they do not reflect the real use, to fix this I have to manually delete the file maildirsize and run the command vuserinfo user at domain.com, depending on your experience may be the cause of this problem? thanks Jose Luis

Dears Sirs, I've noticed that since the Courier to Dovecot migration have had few problems with the %usage of email accounts as they do not reflect the real use, to fix this I have to manually delete the file maildirsize and run the command vuserinfo user at domain.com, depending on your experience may be the cause of this problem? thanks Jose Luis