Menu

#67 DTS 195 / RFC 2046: Section 5.1.1 error report message can be misleading

v1.0_(example)
open
nobody
None
5
2014-08-01
2014-08-01
Phil
No

Matter discussed here https://groups.google.com/forum/#!topic/transport-testing-tool/yv-s3fh0HMw

To recap tho: the message "Any linebreak must be represented as a CRLF" is misleading because the error is not only reported when line breaks other than the form CRLF appear in the attachment.

The existence of extended ASCII characters will also cause this error to be reported and I wouldn't be surprised if the ASCII escape codes would cause the same error to be reported. So that it is clear why the error is being reported it would be ideal to either have a general statement detailing all the disallowed characters / combinations or refer elsewhere that details the document requirements.

As I would imagine this test is simply being performed by checking whether the document contains a particular set of characters / sequences then it would make sense for the error message to either detail which check failed or list of all the disallowed characters and sequences.

Discussion


Log in to post a comment.