[sieve][pigeonhole] Can't catch stdout for pipe script after upgrade Dovecot 2.2 -> 2.3

[Stephan Bosch]

Op 3/28/2018 om 6:01 AM schreef Konstantin Shalygin:
>
> Hi.
>
>
> I use custom script:
>
>> require [ "vnd.dovecot.pipe", "variables" ];
>>
>> if address :is :all "from" "snip at snap"
>> {
>>   pipe "sieve_to_owncloud";
>> }
>
>
> sieve_to_owncloud:
>
>> DATE=`date +%Y-%m-%d_%H-%M-%S`
>> PYTHONIOENCODING=utf8 python /opt/sieve-pipe/python-imap-to-owncloud.py \
>>   --owncloud-host https://<snip-snap> \
>>   --owncloud-user user \
>>   --owncloud-password secret \
>>   --owncloud-path /path/to/here &>/tmp/sieve_logger_py_${DATE}
>
>
> On dovecot 2.2 after script execution I will get plaintext log files
> on /tmp. After upgrade - don't.
>
> I also changed transport to lmtp when upgrade. Any ideas where is my
> stdout?
>

The most common cause would be that systemd is configured with
PrivateTmp for the Dovecot service, which means that the created log
files are not visible from another (shell) process. Try another location
outside /tmp.

Regards,

Stephan.