Am 18.02.2017 um 17:44 schrieb Ben:
[ ... ]
Actually, after many hours of head-bashing, I discovered the problem.
sieve doesn't work when you're just using telnet port 25 !
I was doing :
ehlo test
mail from:sen...@example.com
rcpt to:re...@example.com
data
Subject: hello world
Hello World
Thank you for this.
Actually, after many hours of head-bashing, I discovered the problem.
sieve doesn't work when you're just using telnet port 25 !
I was doing :
ehlo test
mail from:sen...@example.com
rcpt to:re...@example.com
data
Subject: hello world
Hello World !
.
With the above, sieve
On 2017-02-18, Ben wrote:
>
>> What I did when encountering a similar issue was to take one of the messages
>> from INBOX that should have been moved elsewhere and use sieve-test on it:
>>
>> sieve-test -Tlevel=matching
>>
>> That generates a lot of output as it goes through every line of the s
What I did when encountering a similar issue was to take one of the messages
from INBOX that should have been moved elsewhere and use sieve-test on it:
sieve-test -Tlevel=matching
That generates a lot of output as it goes through every line of the sieve file
and shows the actual values tha
> On 17 February 2017, at 08:24, Ben wrote:
>
> Hi,
>
> I have copied accross a known-good sieve file from a working server and its
> not filtering. Everything just gets chucked into INBOX.
What I did when encountering a similar issue was to take one of the messages
from INBOX that should h
