df32418df5
The way I read the RFC is that whitespace is not allowed before the boundary marker, only afterwards, so the checks for leading WS are removed, and the missing check for trailing WS is added. See RFC 2046 §5.1.1: """The boundary delimiter line is then defined as a line consisting entirely of two hyphen characters ("-", decimal value 45) followed by the boundary parameter value from the Content-Type header field, optional linear whitespace, and a terminating CRLF.""" |
||
---|---|---|
cmake | ||
contrib | ||
doc/book | ||
examples | ||
src/vmime | ||
tests | ||
.gitignore | ||
.travis.yml | ||
AUTHORS | ||
CMakeLists.txt | ||
COPYING | ||
Doxyfile.in | ||
HACKING | ||
NEWS | ||
README | ||
README.autotools | ||
test-outsourced-build.sh | ||
vmime.pc.in |
VMime is a powerful C++ class library for working with RFC-822 and MIME messages and Internet messaging services like IMAP, POP or SMTP. With VMime you can parse, generate and modify messages, and also connect to store and transport services to receive or send messages over the Internet. The library offers all the features to build a complete mail client. Key Features ------------ * it is free software! GNU GPL license (Commercial licenses available!) * fully RFC-compliant implementation * object-oriented and modular design * very easy-to-use (intuitive design) * well documented code * very high reliability * maximum portability Features Overview ----------------- * RFC-2822 and multipart messages * aggregate documents and embedded objects * 8-bit MIME and encoded word extensions * full support for attachments * POP3, IMAP, SMTP, maildir and sendmail * SSL/TLS security layer and X.509 certificates (using GNU TLS) * SASL authentication (using GNU SASL)