error message from sieve

hi, community!

right now i'v got this from the postmater:
-----------------------------------------------------
From: postmastersigmatrans.ru
Subject: Sieve script run error
To: zulsigmatrans.ru
X-DBMail-PhysMessage-ID: 40908083
Message-Id: <1164753930l.21688l.0l(none)>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Your Sieve script [zul] failed to run correctly.
Messages will be delivered to your INBOX for now.
The error message is:
syntax error, unexpected '<', expecting '' or '.'
-----------------------------------------------------
what is it? it's a standard error message, Aaron? if it is,
can it
provide more information (like line number) and would you
please set
"date" in the header?=)
sysinfo: libsieve2.2.1, dbmail-smtp version $Revision: 2065,
mysql,
deban etch with 2.6.17-2-amd64.

alexander
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

On Wed, 2006-11-29 at 01:42 +0300, Alexander Benaguev wrote:
> hi, community!
> 
> right now i'v got this from the postmater:
> -----------------------------------------------------
> From: postmastersigmatrans.ru
> Subject: Sieve script run error
> To: zulsigmatrans.ru
> X-DBMail-PhysMessage-ID: 40908083
> Message-Id: <1164753930l.21688l.0l(none)>
> MIME-Version: 1.0
> Content-Type: text/plain
> Content-Transfer-Encoding: 7bit
> 
> Your Sieve script [zul] failed to run correctly.
> Messages will be delivered to your INBOX for now.
> The error message is:
> syntax error, unexpected '<', expecting '' or '.'

libSieve parses its own addresses, and doesn't like this
one.

I am not sure if the problem is with the script or the
message. Please
post the script so that we can see if the error is in the
script. If it
is, I'll try to improve the error reporting by adding
context about
where the bad address was found in the script.

It's also possible that the bad address was found in the
message. In
that case, the error is very confusing, since it says to the
user that
something is their fault, when in fact it's probably
malformed spam.

I have confirmed that bad *messages* will generate these
errors. How
should we change this to be less confusing? I suppose that
we should
simply not throw errors when a message has bad syntax.

> -----------------------------------------------------
> what is it? it's a standard error message, Aaron? if it
is, can it
> provide more information (like line number) and would
you please set
> "date" in the header?=)

Yes, this is the message that DBMail generates when libSieve
reports an
error. Thanks for the feedback about the message itself,
I'll work on
improving it.

Aaron

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail