Re: Sieve gets in infinite loop

[Simon Josefsson <simon@josefsson.org>]

Jason Rumney <jasonr@gnu.org> writes:

> Simon Josefsson wrote:
>> According to http://tools.ietf.org/html/draft-ietf-sieve-managesieve-09
>> the response line can contain an optional string:
>>
>>     response-nobye        = ("NO" / "BYE") [SP "(" resp-code ")"]
>>                             [SP string] CRLF
>>                             ;; The string contains human readable text
>>                             ;; encoded as UTF-8.
>>
>>   
> I guess you meant to paste the response-ok definition there, but they
> are basically the same.

Ah, right.

>> So how about
>>
>> -  (when (re-search-forward (concat "^OK" sieve-manage-server-eol) nil t)
>> +  (when (re-search-forward (concat "^OK.*" sieve-manage-server-eol) nil t)
>>
>> instead?  Not perfect, but hopefully would solve your problem and still
>> match EOL stuff.
>>   
>
> So the gnus developers are OK about ignoring this statement in section
> 1.3 of the RFC?

It's not an RFC yet.

>   The contents of the string SHOULD be shown to the user and
>   implementations MUST NOT attempt to parse the message for meaning.
>
> Following it would mean parsing the response properly, but I'm not
> sure it is worth it for this case.

Better patches are welcome.

/Simon