mailio
mailio copied to clipboard
mailio is a cross platform C++ library for MIME format and SMTP, POP3 and IMAP protocols. It is based on standard C++ 17 and Boost library.
Hi, I am getting errors compiling a sample file, using some of the code in the examples. I am using https://github.com/karastojko/mailio/blob/master/examples/smtps_simple_msg.cpp as a test, using my own mail server. -...
Hi! First of all, thanks for this great library. Working with it, I've noticed that while the code works fine for most emails, trying to receive some messages will always...
Hi! I get an error while fetching a Multipartmail: "No boundary for multipart message." In the mail are a lot of headers, including: ``` Content-Type: multipart/mixed; boundary="_002_499fd0aeb4974acea221e63dda5e9ed8Exchange33adwortmannde_" MIME-Version: 1.0 --_002_499fd0aeb4974acea221e63dda5e9ed8Exchange33adwortmannde_...
rfc822 says that email should be ASCII/Latin1 - but in reality, I see from gmail cp1255 - andprobably other 8ibt encodings. Which are compatible with latin1... so, this happens on...
Hi, long time user Geoffrey here. How much work would it be to upload your library to vcpkg? That package manager is great at reducing the complexity of deploying things...
I am using master (a7ba9c2) and I have this header which is not being parsed: ``` Received: from tango.tkos.co.il (tango.tkos.co.il [62.219.50.35])by mx.google.com with ESMTP id 8si5141689fxm.107.2009.03.01.10.19.34;Sun, 01 Mar 2009 10:19:35...
In https://github.com/karastojko/mailio/issues/89#issuecomment-1057342052 you mentioned problems with this encoded string: `=?utf-8?Q?=D7=93=D7=99=D7=90=D7=92=D7=95_=D7=99=D7=A1?=` - which decodes (partly) to my name in Hebrew. Yes, its an RTL but it is something that you should...
`message::attach` takes an `istream` and reads the content into a stringstream. This unfortunately only reads till the first whitespace character. This adds a new method to pass the content directly...
Hello. Exceptions in `mailio` often don't seem to be very informative, e.g.: `throw message_error("Parsing failure of the message ID.");` or `throw pop3_error("Parser failure.");` which unfortunately don't say much about the...
I think it should be utf-8 encoding by default, and the corresponding encoding can be generated after setting the default encoding. Now all the parsing codes have not changed, causing...