mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-22 02:48:08 +01:00
test: Fix malformed multipart message
Previously, there was only one CRLF between the terminating boundary of the embedded multipart/alternative and the boundary of the containing multipart. However, according the RFC 1341, 7.2.1: The boundary must be followed immediately either by another CRLF and the header fields for the next part, or by two CRLFs, in which case there are no header fields for the next part and The CRLF preceding the encapsulation line is considered part of the boundary so that it is possible to have a part that does not end with a CRLF (line break). Thus, there must be *two* CRLFs between these boundaries: one that ends the terminating boundary and one that begins the enclosing boundary. While GMime accepted the message we had before, it could not produce such a message.
This commit is contained in:
parent
d2e96a35a5
commit
046ab77b10
1 changed files with 1 additions and 0 deletions
|
@ -46,6 +46,7 @@ Content-Disposition: inline
|
|||
EOF
|
||||
cat embedded_message >> ${MAIL_DIR}/multipart
|
||||
cat <<EOF >> ${MAIL_DIR}/multipart
|
||||
|
||||
--=-=-=
|
||||
Content-Disposition: attachment; filename=attachment
|
||||
|
||||
|
|
Loading…
Reference in a new issue