On 22 May 2017, at 10.07, Christoph Pleger wrote:
>
> Hello,
>
I am using sieve with notification of the original recipient in the case
that an email has been identified to contain a virus. After upgrading
dovecot from 2.2.21 to 2.2.29.1, I now detected that in these
notifica
Op 22-5-2017 om 9:07 schreef Christoph Pleger:
Hello,
I am using sieve with notification of the original recipient in the
case
that an email has been identified to contain a virus. After upgrading
dovecot from 2.2.21 to 2.2.29.1, I now detected that in these
notifications, their sender addre
Hello,
I am using sieve with notification of the original recipient in the
case
that an email has been identified to contain a virus. After upgrading
dovecot from 2.2.21 to 2.2.29.1, I now detected that in these
notifications, their sender address is now , instead of
, like it was before.
Is i
Op 5/19/2017 om 8:33 AM schreef Christoph Pleger:
> Hello,
>
> On 2017-05-14 21:29, I wrote:
>
>> I am using sieve with notification of the original recipient in the case
>> that an email has been identified to contain a virus. After upgrading
>> dovecot from 2.2.21 to 2.2.29.1, I now detected that
Hello,
On 2017-05-14 21:29, I wrote:
I am using sieve with notification of the original recipient in the
case
that an email has been identified to contain a virus. After upgrading
dovecot from 2.2.21 to 2.2.29.1, I now detected that in these
notifications, their sender address is now , instead
Hello,
I am using sieve with notification of the original recipient in the case
that an email has been identified to contain a virus. After upgrading
dovecot from 2.2.21 to 2.2.29.1, I now detected that in these
notifications, their sender address is now , instead of
, like it was before.
Is it p
