issue with sieve forwarding after upgrade to 0.5.1

[Stephan Bosch]

Op 4/3/2018 om 10:34 PM schreef Christos Chatzaras:
> Here are some logs:
>
> Apr  3 23:25:35 server1 dovecot: lmtp(chris at coderz.gr
> <mailto:chris at coderz.gr>)<47735><AUI6Aj/jw1p3ugAAPz4RRA>: program
> `/usr/sbin/sendmail' terminated with non-zero exit code 75
> Apr  3 23:25:35 server1 dovecot: lmtp(chris at coderz.gr
> <mailto:chris at coderz.gr>)<47735><AUI6Aj/jw1p3ugAAPz4RRA>: Error:
> sieve: msgid=<DE90EB45-9B58-4679-9BCE-E2698773519E at cretaforce.gr
> <mailto:DE90EB45-9B58-4679-9BCE-E2698773519E at cretaforce.gr>>: failed
> to redirect message to <chris at cretaforce.gr
> <mailto:chris at cretaforce.gr>>: Sendmail program returned error
> (temporary failure)
>
> In my postfix main.cf I have this:
>
> authorized_submit_users = root, filter
>
> When I change it to:
>
> authorized_submit_users = root, filter, myUserName
>
> where myUserName is the username that owns the mailbox it works.
>
> So I guess that something changed to dovecot between 2.2.35 and 2.3.1
> and is not related to pigeonhole.

Yeah, this is likely due to the fact that sendmail is now invoked using
the program-client (same as Sieve extprograms), which takes great care
to drop any unwanted (seteuid) root privileges.

Regards,

Stephan.

>
>
>> On 3 Apr 2018, at 23:25, Christos Chatzaras <chris at cretaforce.gr
>> <mailto:chris at cretaforce.gr>> wrote:
>>
>> 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
>> <http://server1.myserver.com/>[private/dovecot-lmtp] said: 451 4.2.0
>> <chris at mydomain.com <mailto:chris at mydomain.com>> Execution of Sieve
>> filters was aborted due to temporary failure (in reply to end of DATA
>> command))
>>
>> And in sieve log I see: failed to redirect message to
>> <chris at mydomain.com <mailto:chris at mydomain.com>>: Sendmail program
>> returned error (temporary failure).
>>
>> Any idea what is wrong?
>>
>> Kind regards,
>> Christos Chatzaras
>