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

Use of separate storage for mail delivery

Hi I am facing one issue which is mostly about concepts. I have to be clear on that to move forward. I have tried finding solutions about it but couldn't find anything which talks about it. We have a setup which includes postfix and dovecot. We are using lmtp and delivery of mail is happening th

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: 2.3.1 Replication is throwing scary errors

Hi, -- Message: 2 Date: Mon, 2 Apr 2018 22:06:07 +0200 From: Michael Grimm To: Dovecot Mailing List Subject: 2.3.1 Replication is throwing scary errors Message-ID: <29998016-d62f-4348-93d1-613b13da9...@ellael.org> Content-Type: text/plain; charset=utf-8 Hi

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

Re: 2.3.1 Replication is throwing scary errors

Michael Grimm wrote: > [This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at > distinct servers.] > > I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by error > messages at server1 (and vice versa at server2) as follows: > > | Apr 2 17:12:18 server1.l

Re: dovecot auth error: Illegal seek

Thanks Aki for the answer. I did some tests and found a solution. I write down my experience It could be useful to someone. First I putted  "passwd-file" passdb (only)  before "pam" passdb, as Aki suggested, but "illegal seek error" persisted. Then I putted both "passwd-file" passdb and "st