Re: [PATCH] parsemail: Clarify exit codes

On Tue, 2018-05-01 at 01:44 +1000, Daniel Axtens wrote: > jk reports that the patchwork error codes are really unhelpful for > correct integration with an MDA. In particular they make sorting out > failures into a separate queue very difficult. Make this better and > clearer: only return 1 on a

[PATCH] parsemail: Clarify exit codes

jk reports that the patchwork error codes are really unhelpful for correct integration with an MDA. In particular they make sorting out failures into a separate queue very difficult. Make this better and clearer: only return 1 on a genuinely unexpected case that requires adminstrator intervention.

Re: [PATCH] parsemail: Clarify exit codes

Daniel Axtens writes: > Daniel Axtens writes: > >> jk reports that the patchwork error codes are really unhelpful for >> correct integration with an MDA. In particular they make sorting out >> failures into a separate queue very difficult. Make this better and

Re: [PATCH] parsemail: Clarify exit codes

Daniel Axtens writes: > jk reports that the patchwork error codes are really unhelpful for > correct integration with an MDA. In particular they make sorting out > failures into a separate queue very difficult. Make this better and > clearer. > > Update the comment for

[PATCH] parsemail: Clarify exit codes

jk reports that the patchwork error codes are really unhelpful for correct integration with an MDA. In particular they make sorting out failures into a separate queue very difficult. Make this better and clearer. Update the comment for parse_mail regarding return values and exceptions to line up