issue with sieve forwarding after upgrade to 0.5.1

Finally I found a workaround to not depend on sendmail to forward messages using sieve: In postfix main.cf I have: authorized_submit_users = root, filter (I want only root and filter to use sendmail and block other users to send e-mails from system accounts. Only allow users to send e-mails f

Re: issue with sieve forwarding after upgrade to 0.5.1

On 2018-04-04 03:09, Aki Tuomi wrote: > We are thinking that we remove both this and CapabilityBoundingSet in > next release, so feel free to remove them from the unit file. Thanks for the info. Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprin

Re: issue with sieve forwarding after upgrade to 0.5.1

It's similar issue but not the same. In my postfix main.cf I use: authorized_submit_users = root, filter to block users with shell access to send e-mails. I want only users root and filter to be able to send directly without using SMTP authentication. If I remove "authorized_submit_users = ro

Re: issue with sieve forwarding after upgrade to 0.5.1

On 2018-04-04 11:02, Christos Chatzaras wrote: > Thank you for your reply. I use FreeBSD so no changes on the OS before and > after the dovecot/pigeonhole updates. Oops. I guess I assume everyone uses Linux (and Debian at that.. :) I don't know how dovecot is set-up with FreeBSD. The error you

Re: issue with sieve forwarding after upgrade to 0.5.1

Thank you for your reply. I use FreeBSD so no changes on the OS before and after the dovecot/pigeonhole updates. > On 4 Apr 2018, at 08:54, B. Reino wrote: > > Hello, > > The new systemd service file has NoNewPrivileges set to true. You need to > override that to false and then it should wor

Re: issue with sieve forwarding after upgrade to 0.5.1

ubject: Re: issue with sieve forwarding after upgrade to 0.5.1 On 2018-04-04 01:54, B. Reino wrote: > The new systemd service file has NoNewPrivileges set to true. You need > to override that to false and then it should work again. It seems that the NoNewPrivileges option messes with sev

Re: issue with sieve forwarding after upgrade to 0.5.1

On 2018-04-04 01:54, B. Reino wrote: > The new systemd service file has NoNewPrivileges set to true. You need > to override that to false and then it should work again. It seems that the NoNewPrivileges option messes with several things. PAM authentication stopped working as well besides the fact

Re: issue with sieve forwarding after upgrade to 0.5.1

Hello, The new systemd service file has NoNewPrivileges set to true. You need to override that to false and then it should work again. (if you need help with that ask again.. I'm on the train now so I can't write much comfortably..) Cheers. On April 3, 2018 10:25:22 PM GMT+02:00, Christos Cha

Re: issue with sieve forwarding after upgrade to 0.5.1

Op 4/3/2018 om 10:34 PM schreef Christos Chatzaras: > Here are some logs: > > Apr  3 23:25:35 server1 dovecot: lmtp(ch...@coderz.gr > )<47735>: program > `/usr/sbin/sendmail' terminated with non-zero exit code 75 > Apr  3 23:25:35 server1 dovecot: lmtp(ch...@coderz.gr >

Re: issue with sieve forwarding after upgrade to 0.5.1

Here are some logs: Apr 3 23:25:35 server1 dovecot: lmtp(ch...@coderz.gr)<47735>: program `/usr/sbin/sendmail' terminated with non-zero exit code 75 Apr 3 23:25:35 server1 dovecot: lmtp(ch...@coderz.gr)<47735>: Error: sieve: msgid=: failed to redirect message to : Sendmail program returned

issue with sieve forwarding after upgrade to 0.5.1

Hello, After I upgrade dovecot 2.2.35 to 2.3.1 and pigeonhole 0.4.23 to 0.5.1 when I use sieve to forward a message to other address using "redirect :copy" I get this: (host server1.myserver.com [private/dovecot-lmtp] said: 451 4.2.0 mailto:ch...@mydomain.com>> E