[Dovecot] Prevent dovecot.sieve.log logs
Hello,
When an account overquota happens, a log is generated: /var/lib/imap/sieve/username/dovecot.sieve.log
Is there a way to prevent this?
My dovecot -n :
################################################################################
2.0.6 (a7d99b69523a): /etc/dovecot/dovecot.conf
OS: Linux 2.6.35-23-server x86_64 Ubuntu 10.04.1 LTS
auth_master_user_separator = * auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@= auth_worker_max_count = 10 disable_plaintext_auth = no listen = server.com login_greeting = K8 IMAP/POP3 server mail_gid = dovemail mail_plugins = " quota" mail_uid = dovemail managesieve_sieve_capability = fileinto reject envelope vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include imapflags notify mmap_disable = yes passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } plugin { autocreate = SPAM autosubscribe = SPAM quota = dict:User quota::file:/var/lib/imap/user/%2.256RHn/% n/dovecot-quota quota_rule = *:storage=1GB sieve = /var/lib/imap/sieve/%2.256RHn/%n/dovecot.sieve sieve_dir = /var/lib/imap/sieve/%2.256RHn/%n sieve_extensions = comparator-i;ascii-numeric copy envelope fileinto imapflags include notify regex reject relational subaddress vacation sieve_max_script_size = 512KB sieve_quota_max_scripts = 2 } protocols = imap pop3 lmtp sieve service auth-worker { user = $default_internal_user } service auth { process_limit = 1 process_min_avail = 1 } service imap-login { inet_listener imap { address = server.com port = 143 } } service imap { process_limit = 1024 process_min_avail = 10 } service lmtp { inet_listener { address = server.com port = 2003 } process_limit = 256 process_min_avail = 10 } service managesieve-login { inet_listener sieve { address = server.com port = 4190 } inet_listener sieve_deprecated { address = server.com port = 2000 } } service managesieve { process_limit = 20 process_min_avail = 10 } service pop3-login { inet_listener pop3 { address = server.com port = 110 } } service pop3 { process_limit = 256 process_min_avail = 10 } ssl = no userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol imap { imap_idle_notify_interval = 2 mins imap_max_line_length = 64 k mail_max_userip_connections = 50 mail_plugins = " quota imap_quota autocreate" } protocol lmtp { mail_plugins = " sieve quota autocreate" } protocol sieve { mail_plugins = " sieve" managesieve_implementation_string = K8 ManageSieve managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 managesieve_sieve_capability = comparator-i;ascii-numeric copy envelope fileinto imapflags include notify regex reject relational subaddress vacation } protocol pop3 { mail_plugins = " quota autocreate" } ################################################################################
Thanks,
Thiago Henrique
On 10/25/2010 08:05 PM, Thiago Henrique wrote:
Hello,
When an account overquota happens, a log is generated: /var/lib/imap/sieve/username/dovecot.sieve.log
Is there a way to prevent this?
Currently, no. This feature has existed since the early stages of the cmusieve plugin. To my knowledge, you are the first to request this. What's your problem exactly?
Regards,
Stephan.
On 25.10.2010, at 21.02, Stephan Bosch wrote:
When an account overquota happens, a log is generated: /var/lib/imap/sieve/username/dovecot.sieve.log
Is there a way to prevent this?
Currently, no. This feature has existed since the early stages of the cmusieve plugin. To my knowledge, you are the first to request this. What's your problem exactly?
I think the overquota situation should work the same way with Sieve as without Sieve: It logs one line to info log, something like:
deliver(tss): Info: msgid=<foo@bar>: save failed to INBOX: Out of quota
(I guess it already does this in addition to writing the same info to dovecot.sieve.log?)
Or I guess it becomes more problematic with multiple actions. Hmm. What does it log now if you fileinto to two mailboxes and also forward the mail? Maybe each of those actions should do mail_deliver_log(), resulting in:
deliver(tss): Info: msgid=<foo@bar>: saved mail to INBOX deliver(tss): Info: msgid=<foo@bar>: saved mail to backup deliver(tss): Info: msgid=<foo@bar>: forwarded mail to <blah@example.com>
Op 25-10-2010 23:04, Timo Sirainen schreef:
On 25.10.2010, at 21.02, Stephan Bosch wrote:
When an account overquota happens, a log is generated: /var/lib/imap/sieve/username/dovecot.sieve.log
Is there a way to prevent this? Currently, no. This feature has existed since the early stages of the cmusieve plugin. To my knowledge, you are the first to request this. What's your problem exactly? I think the overquota situation should work the same way with Sieve as without Sieve: It logs one line to info log, something like:
deliver(tss): Info: msgid=<foo@bar>: save failed to INBOX: Out of quota
(I guess it already does this in addition to writing the same info to dovecot.sieve.log?)
Or I guess it becomes more problematic with multiple actions. Hmm. What does it log now if you fileinto to two mailboxes and also forward the mail? Maybe each of those actions should do mail_deliver_log(), resulting in:
deliver(tss): Info: msgid=<foo@bar>: saved mail to INBOX deliver(tss): Info: msgid=<foo@bar>: saved mail to backup deliver(tss): Info: msgid=<foo@bar>: forwarded mail to<blah@example.com>
Ah, now I understand the problem. Timo, you pointed something similar out a while back. Will be fixed asap.
Regards,
Stephan.
Hi,
This log is not controlled by Syslog and it is not rotated by Logrotate. I'm afraid that happens overquota in my Sieve filesystem.
Thanks.
Thiago Henrique
Em Seg, 2010-10-25 às 22:02 +0200, Stephan Bosch escreveu:
On 10/25/2010 08:05 PM, Thiago Henrique wrote:
Hello,
When an account overquota happens, a log is generated: /var/lib/imap/sieve/username/dovecot.sieve.log
Is there a way to prevent this?
Currently, no. This feature has existed since the early stages of the cmusieve plugin. To my knowledge, you are the first to request this. What's your problem exactly?
Regards,
Stephan.
Hi Thiago,
Simply let Logrotate handle these logs too. It can compress/move/delete them and this way no overquota at your Sieve filesystem will happen. Do a 'man logrotate' to see how to achieve this.
Rgds Tamsy
Thiago Henrique wrote the following on 26.10.2010 18:44:
Hi,
This log is not controlled by Syslog and it is not rotated by Logrotate. I'm afraid that happens overquota in my Sieve filesystem.
Thanks.
Thiago Henrique
Em Seg, 2010-10-25 às 22:02 +0200, Stephan Bosch escreveu:
On 10/25/2010 08:05 PM, Thiago Henrique wrote:
Hello,
When an account overquota happens, a log is generated: /var/lib/imap/sieve/username/dovecot.sieve.log
Is there a way to prevent this? Currently, no. This feature has existed since the early stages of the cmusieve plugin. To my knowledge, you are the first to request this. What's your problem exactly?
Regards,
Stephan.
Op 26-10-2010 13:44, Thiago Henrique schreef:
Hi,
This log is not controlled by Syslog and it is not rotated by Logrotate. I'm afraid that happens overquota in my Sieve filesystem.
Actually, I'm sure it won't.
From the wiki http://wiki2.dovecot.org/Pigeonhole/Sieve/Usage:
"* A log file is written in the same directory as the user's main private script (as specified by the sieve setting). This log file bears the name of that script file appended with ".log", e.g. .dovecot.sieve.log. If there are errors or warnings in the script, the messages are appended to that log file until it eventually grows too large (>10 kB currently). When that happens, the old log file is moved to a ".log.0" file and an empty log file is started. Informational messages are not written to this log file and the log file is not created until messages are actually logged, i.e. when an error or warning is produced."
Regards,
Stephan.
participants (4)
-
Stephan Bosch
-
Tamsy
-
Thiago Henrique
-
Timo Sirainen