make response code parse failure of untagged OK/NO/BYE/BAD non-fatal
as such, it does not disrupt the data stream
This commit is contained in:
parent
d2e13f147c
commit
121ce76e46
|
@ -1018,8 +1018,7 @@ get_cmd_result( imap_store_t *ctx, struct imap_cmd *tcmd )
|
||||||
ctx->ns_shared = parse_list( &cmd );
|
ctx->ns_shared = parse_list( &cmd );
|
||||||
} else if (!strcmp( "OK", arg ) || !strcmp( "BAD", arg ) ||
|
} else if (!strcmp( "OK", arg ) || !strcmp( "BAD", arg ) ||
|
||||||
!strcmp( "NO", arg ) || !strcmp( "BYE", arg )) {
|
!strcmp( "NO", arg ) || !strcmp( "BYE", arg )) {
|
||||||
if ((resp = parse_response_code( ctx, 0, cmd )) != RESP_OK)
|
parse_response_code( ctx, 0, cmd );
|
||||||
return resp;
|
|
||||||
} else if (!strcmp( "CAPABILITY", arg ))
|
} else if (!strcmp( "CAPABILITY", arg ))
|
||||||
parse_capability( ctx, cmd );
|
parse_capability( ctx, cmd );
|
||||||
else if (!strcmp( "LIST", arg ))
|
else if (!strcmp( "LIST", arg ))
|
||||||
|
|
Loading…
Reference in New Issue
Block a user