Hello,
is there a way to write a logfile during sieve-actions?
At least, I have trouble in reading sieve-scripts with tools from kmail ("connection refused) or thunderbird (timed out: server does not answer). There is no problem with the mailbox itself in reading or writing in it.
The config for Sieve:
dovecot.conf: ## ## LDA specific settings ##
protocol lda { # Address to use when sending rejection mails. postmaster_address = christoph@localhost
# Hostname to use in various parts of sent mails, eg. in Message-Id. # Default is the system's real hostname. #hostname =
# Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load.
# Binary to use for sending mails. #sendmail_path = /usr/lib/sendmail
# UNIX socket path to master authentication server to find users. #auth_socket_path = /var/run/dovecot/auth-master
debug = yes log_path = /var/log/dovecot/dovecot-deliver-errors.log info_log_path = /var/log/dovecot/dovecot-deliver.log
# Enabling Sieve plugin for server-side mail filtering mail_plugins = cmusieve
}
plugin { # Here you can give some extra environment variables to mail processes. # This is mostly meant for passing parameters to plugins. %variable # expansion is done for all values.
#sieve = /var/sieve-scripts/%u/sieve sieve=~/.dovecot.sieve
# Quota plugin. Multiple backends are supported: # dirsize: Find and sum all the files found from mail directory. # Extremely SLOW with Maildir. It'll eat your CPU and disk I/O. # dict: Keep quota stored in dictionary (eg. SQL) # maildir: Maildir++ quota # fs: Read-only support for filesystem quota #quota = maildir
# ACL plugin. vfile backend reads ACLs from "dovecot-acl" file from maildir # directory. You can also optionally give a global ACL directory path where # ACLs are applied to all users' mailboxes. The global ACL directory contains # one file for each mailbox, eg. INBOX or sub.mailbox. #acl = vfile:/etc/dovecot-acls
# Convert plugin. If set, specifies the source storage path which is # converted to destination storage (mail_location) when the user logs in. # The existing mail directory is renamed to <dir>-converted. #convert_mail = mbox:%h/mail # Skip mailboxes which we can't open successfully instead of aborting. #convert_skip_broken_mailboxes = no
# Trash plugin. When saving a message would make user go over quota, this # plugin automatically deletes the oldest mails from configured mailboxes # until the message can be saved within quota limits. The configuration file # is a text file where each line is in format: <priority> <mailbox name> # Mails are first deleted in lowest -> highest priority number order #trash = /etc/dovecot-trash.conf
# Lazy expunge plugin. Currently works only with maildirs. When a user # expunges mails, the mails are moved to a mailbox in another namespace # (1st). When a mailbox is deleted, the mailbox is moved to another namespace # (2nd) as well. Also if the deleted mailbox had any expunged messages, # they're moved to a 3rd namespace. The mails won't be counted in quota, # and they're not deleted automatically (use a cronjob or something). #lazy_expunge = .EXPUNGED/ .DELETED/ .DELETED/.EXPUNGED/ }
and postfix as LDA: ... mailbox_command = /usr/lib/dovecot/deliver ...
There are much logentrys about dovecot, devivering and mail, but no sieve- entrys in any log.
Hope you can help me,
Greets, Christoph
PS the system: fritz!box (mipsel-cpu) debian etch (and backports; lenny + dovecot does not run with this environment) dovecot and postfix from etch-backports
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
On 10/18/2010 8:03 AM, cool.chris65@web.de wrote:
Hello,
is there a way to write a logfile during sieve-actions?
At least, I have trouble in reading sieve-scripts with tools from kmail ("connection refused) or thunderbird (timed out: server does not answer). There is no problem with the mailbox itself in reading or writing in it.
Are you running the ManageSieve service?
http://wiki.dovecot.org/ManageSieve
Regards,
Stephan.
Am Montag 18 Oktober 2010, um 08:24:19 schrieb Stephan Bosch:
On 10/18/2010 8:03 AM, cool.chris65@web.de wrote:
Hello,
is there a way to write a logfile during sieve-actions?
At least, I have trouble in reading sieve-scripts with tools from kmail ("connection refused) or thunderbird (timed out: server does not answer). There is no problem with the mailbox itself in reading or writing in it.
Are you running the ManageSieve service?
http://wiki.dovecot.org/ManageSieve
Regards,
Stephan.
Hello,
no, because it's dovecot < 1.2, there is only cmusieve avaiable ...
Greetz, Christoph
GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261
Op 18-10-2010 20:50, cool.chris65@web.de schreef:
Am Montag 18 Oktober 2010, um 08:24:19 schrieb Stephan Bosch:
On 10/18/2010 8:03 AM, cool.chris65@web.de wrote:
Hello,
is there a way to write a logfile during sieve-actions?
At least, I have trouble in reading sieve-scripts with tools from kmail ("connection refused) or thunderbird (timed out: server does not answer). There is no problem with the mailbox itself in reading or writing in it. Are you running the ManageSieve service?
http://wiki.dovecot.org/ManageSieve
Regards,
Stephan. Hello,
no, because it's dovecot< 1.2, there is only cmusieve avaiable ...
Greetz, Christoph
ManageSieve for Dovecot v1.0/v1.1 can also work with CMUSieve.
http://pigeonhole.dovecot.org/download.html
Regards,
Stephan.
participants (2)
-
cool.chris65@web.de
-
Stephan Bosch