Hi Stephen,
I finally had a chance to re-test this and confirm that v4.1 of the plugin
does fix the problem.
Thanks for your assistance.
Regards,
Anand
On 25 July 2013 17:11, Stephan Bosch wrote:
> On 7/25/2013 8:06 AM, Anand Kumria wrote:
>
> Hi Stephan,
>
> I'm not sure, I'm using Dovecot
On 7/25/2013 8:06 AM, Anand Kumria wrote:
Hi Stephan,
I'm not sure, I'm using Dovecot-managesieved 0.4.0-14, which I believe
is commit
1771:b41f5cf04b8f, which is actually *before* the commit you mentioned.
I'm not clear because you already have a release (v4.1) which does
contain that pat
Hi Stephan,
I'm not sure, I'm using Dovecot-managesieved 0.4.0-14, which I believe is
commit
1771:b41f5cf04b8f, which is actually *before* the commit you mentioned.
I'm not clear because you already have a release (v4.1) which does contain
that patch; are you suggesting that an upgrade to that
Op 7/24/2013 3:30 PM, Stephan Bosch schreef:
Op 7/24/2013 1:04 PM, Anand Kumria schreef:
As I said, my suspicions are on 'mail_crlf_save = yes', since that
*is* specifically modifying the headers associated with the message.
This setting has no effect on Sieve redirect since the message is
Op 7/24/2013 1:04 PM, Anand Kumria schreef:
As I said, my suspicions are on 'mail_crlf_save = yes', since that
*is* specifically modifying the headers associated with the message.
This setting has no effect on Sieve redirect since the message is not
saved. However, redirect does use Doveco
Hi Stephan,
On 24 July 2013 11:52, Stephan Bosch wrote:
> Op 7/24/2013 12:32 PM, Anand Kumria schreef:
>
> Hi Stephan,
>>
>> Attached is the configuration and both the original message as received
>> (sieve redirect test.eml) and what it was like at the location where the
>> redirect was receiv
Op 7/24/2013 12:32 PM, Anand Kumria schreef:
Hi Stephan,
Attached is the configuration and both the original message as
received (sieve redirect test.eml) and what it was like at the
location where the redirect was received
(1373811315.24616_23.niflheim:2,S)
Let me know if you need anything
Hi Stephan,
Attached is the configuration and both the original message as received
(sieve redirect test.eml) and what it was like at the location where the
redirect was received (1373811315.24616_23.niflheim:2,S)
Let me know if you need anything else to diagnose the problem.
Thanks,
Anand
On 2
On 7/24/2013 3:55 AM, Anand Kumria wrote:
I've noticed that the redirect sieve extension is placing an extra space
before the headers of email when the 'redirect' command is used.
Unfortunately this break gmail, yahoo, and most other email programs.
I am using pigeonhole 0.4.0-14 with Dovecot 2
Hi,
I've noticed that the redirect sieve extension is placing an extra space
before the headers of email when the 'redirect' command is used.
Unfortunately this break gmail, yahoo, and most other email programs.
I am using pigeonhole 0.4.0-14 with Dovecot 2.2.4.3; I see change
1781:e439789e3211
10 matches
Mail list logo