From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Sieve-Manage question: how to debug?
Date: Sat, 25 Jan 2003 21:08:25 +0100 [thread overview]
Message-ID: <iluiswd56x2.fsf@latte.josefsson.org> (raw)
In-Reply-To: <84iswegyzb.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Fri, 24 Jan 2003 19:54:32 +0100")
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> I invoke sieve-manage, then hit RET on my script. It ends with
> "keep;". I replace this line with "eep;" and hit C-c C-l. The
> message I get is:
>
> Sieve upload failed: {38}
>
> So, where do I go from here? 38 is not the line number with the
> error, I think. Is there any way to debug the problem?
The protocol dump probably looked like:
PUTSCRIPT ".sieve" {22202+}
script content....
eep;
NO {38}
script errors:
line 749: parse error
The parser didn't handle literal strings as error messages. It should
now.
next prev parent reply other threads:[~2003-01-25 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 18:54 Kai Großjohann
2003-01-25 20:08 ` Simon Josefsson [this message]
2003-01-25 21:30 ` Kai Großjohann
2003-01-25 21:33 ` Kai Großjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=iluiswd56x2.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).