maildir very dirty sync option
Hello , I have an active passive dovecot setup with glusterfs as a mail storage and using maildirs, we used to have a problem when users with large mailboxes sync their folders. This caused the load average to increase in the server , after a while we have enabled the very_dirty_sync option in dovecot , things got better and the problem disappeared but we need to know if there is any thing else that we need to do or know about the very_dirty_sync option that may cause future problems . Thanks in advance
Re: maildir very dirty sync option
On 2019-08-20 17:05, Yousif Alkhateeb via dovecot wrote: Hello , I have an active passive dovecot setup with glusterfs as a mail storage and using maildirs, we used to have a problem when users with large mailboxes sync their folders. This caused the load average to increase in the server , after a while we have enabled the very_dirty_sync option in dovecot , things got better and the problem disappeared but we need to know if there is any thing else that we need to do or know about the very_dirty_sync option that may cause future problems . Last time I tested Glusterfs as mail storage (stock RHEL 6 kernel, think 6-7 years ago?) the performance on large maildirs was abysmal. We've ended up with DRBD & NFS (TCP, with UDP it'd freeze in less than half an hour under stress testing) and haven't looked back since. I know this isn't the answer you're looking for and I don't know how your deployment looks like, nor the scale, but I'm just chipping in. Tuning various Dovecot may be just kicking the can down the road, looking into alternate storage backends could be an option you should perhaps consider. Cheers, -- Adi Pircalabu
Re: Dovecot and Oauth
Am Tue, 20 Aug 2019 11:07:13 +1200 schrieb Michael Hallager via dovecot : > Hi all, > > I am considering expanding a mail server to support Oauth with > Google. I have read through the following: > https://wiki.dovecot.org/PasswordDatabase/oauth2 > however, it doesn't work and appears to me to be missing important > information, the least of which is API authorisation. Searching with > Google, I can't find any more information beyond what amounts to > C&P'ing of the above link. > > Has anyone successfully deployed Oauth with Google and could they > please send me their config files? > > Thanks, > > Michael Hi, you should try the ## HTTP request raw log directory # rawlog_dir = /tmp/oauth2 option. this dumps the http requests in this dir and you can see the requests and the response from the server. maybe its the missing scope= option as mentioned in this thread [[ Dovecot - Microsoft Azure AD ]] if its the case try building dovecot from master branch. Greetz Matze
Re: maildir very dirty sync option
On Tue, Aug 20, 2019 at 10:05:59AM +0300, Yousif Alkhateeb via dovecot wrote: > Hello , > > I have an active passive dovecot setup with glusterfs as a mail storage and > using maildirs, we used to have a problem when users with large mailboxes > sync their folders. This caused the load average to increase in the server > , after a while we have enabled the very_dirty_sync option in dovecot , > things got better and the problem disappeared but we need to know if there > is any thing else that we need to do or know about the very_dirty_sync > option that may cause future problems . What's the scale of this problem? I.e., how large are the troublesome "large mailboxes"? A gigabyte? A terabyte? a few megabytes? -- hendrik
imapsieve suddenly not working anymore
Hello one and all. Dovecot version 2.3.7.1 I've configured imapsieve like https://wiki.dovecot.org/HowTo/AntispamWithSieve a while a go and it worked for years now. Suddenly i noticed moving mails to the spamfolder does not trigger the report-spam.sieve script anymore. sieve-test gives: ~/.maildir/.Spam/cur $ sieve-test /usr/share/dovecot/sieve/report-spam.sieve 1542388745.M99384P16720.meine-oma.de\,S\=8173\,W\=8373\:2\,S -D sieve-test(himbeere): Debug: sieve: Pigeonhole version 0.5.7.1 (db5c74be) initializing sieve-test(himbeere): Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. sieve-test(himbeere): Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.5.7.1 (db5c74be) loaded sieve-test(himbeere): Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.5.7.1 (db5c74be) loaded debug: file storage: Using Sieve script path: /usr/share/dovecot/sieve/report-spam.sieve. debug: file script: Opened script `report-spam' from `/usr/share/dovecot/sieve/report-spam.sieve'. debug: Script binary /usr/share/dovecot/sieve/report-spam.svbin successfully loaded. debug: binary save: not saving binary /usr/share/dovecot/sieve/report-spam.svbin, because it is already stored. report-spam: error: the imapsieve extension cannot be used outside IMAP. sieve-test(himbeere): Info: final result: failed; resolved with successful implicit keep ~/.maildir/.Spam/cur $ I'm not sure the "the imapsieve extension cannot be used outside IMAP" is the error already or thats only because the sieve-test script. Any ideas on that? cheers, t.
