Re: Dovecot no logs by sieve user script [SOLVED]

2019-01-07 Thread Christian Wolf 

Dear mailing list,

I have to admit, I was mislead: I thought that some messages should be 
logged anyway. But in fact sieve only logs errors by default.


So I had to introduce a intended error in my sieve script, trigger it by 
sending a mail and voi-là: the log got its error messages.


So this topic can be seen as solved.

Thanks anyways
Christian

Re: Dovecot no logs by sieve user script

2019-01-07 Thread Christian Wolf 

Dear Stephan,

Am 06.01.19 um 19:07 schrieb Stephan Bosch:
Can you enable mail_debug=yes and look at your debug log. Sieve will 
tell you what directories files are being used.


I did this already in the past without insight. Maybe I miss something. 
I put the relevant lines from my system mail logs to 
https://gist.github.com/christianlupus/0dc7007c00551e15130c91a02a42e9b2.


Remember I am looking for a way to allow my users to see their filtering 
results/logs/errors without need to access the system wide logs.

In my "old" setup this worked flawlessly.

Thanks
Christian

Re: Dovecot no logs by sieve user script

2019-01-06 Thread Stephan Bosch 

Op 06/01/2019 om 18:58 schreef Christian Wolf:


Dear mailinglist,

I have the problem that I had to migrate a setup and since then my 
user's sieve script does no longer log anything.


I have sieve_user_log unset and sieve points to a folder (ready for 
ManageSievev service). In the old config I had sieve point to the 
symlink and sieve_dir point to the folder of all scripts. As sieve_dir 
is deprecated I use the sieve directive only (see below).


According to my understanding of 
https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration this should 
result in user logging in ~/.dovecot.sieve.log. This file is never 
generated by dovecot and if I create it manually, it is not filled.


Can you tell me, what I am missing here in order to get the per-user 
logs running?


Can you enable mail_debug=yes and look at your debug log. Sieve will 
tell you what directories files are being used.


Regards,

Stephan.


Thank you very much

Christian

# dovecot --version 2.2.27 (c0f36b0)

# dovecot -n # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # 
Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-8-amd64 x86_64 
Debian 9.6 auth_mechanisms = plain login disable_plaintext_auth = no 
mail_location = maildir:~/Mailbox managesieve_notify_capability = 
mailto managesieve_sieve_capability = fileinto reject envelope 
encoded-character vacation subaddress comparator-i;ascii-numeric 
relational regex imap4flags copy include variables body en otify 
environment mailbox date index ihave duplicate mime foreverypart 
extracttext namespace inbox {  inbox = yes  location =  mailbox Drafts 
{    auto = create    special_use = \Drafts  }  mailbox Junk {    auto 
= subscribe    special_use = \Junk  }  mailbox Sent {    auto = 
subscribe    special_use = \Sent  }  mailbox Trash {    special_use = 
\Trash  }  prefix = } passdb {  driver = pam } passdb {  args = 
scheme=CRYPT username_format=%u /etc/dovecot/users  driver = 
passwd-file } plugin {  sieve = file:~/sieve;active=~/.dovecot.sieve } 
postmaster_address = postmas...@wolf-stuttgart.net protocols = " imap 
sieve sieve" service auth {  unix_listener 
/var/spool/postfix/private/auth {    mode = 0666  } } service 
managesieve-login {  inet_listener sieve {    port = 4190  } } ssl = 
required ssl_cert = =  # hidden, use -P to show it userdb {  driver = passwd } userdb { 
 args = username_format=%u /etc/dovecot/users  driver = passwd-file } 
protocol lda {  mail_plugins = " sieve" }