|
Hello, Sorry, I haven't been following this thread, so forgive me if this has already been discussed. > I started a reply to discuss MIME, but it gets messy fast for me. I > can't think of any thing better than (1) read RFC 1521 a few times and > (2) download something that does it for you. I see that Tom recommends RFC1521... that's an obsolete document. Instead you should read RFCs 2045,2046,2047,2048 and 2049. http://www.faqs.org/rfcs/rfc2045.html http://www.faqs.org/rfcs/rfc2046.html http://www.faqs.org/rfcs/rfc2047.html http://www.faqs.org/rfcs/rfc2048.html http://www.faqs.org/rfcs/rfc2049.html > For you, it might be easy because you might never be interested in > sending anything but plain text attachments. In that case, the headers > that mark the beginning and end of each section will be pretty much the > same in every e-mail. You won't even need to do any encoding/decoding; > it's already printable text. Yeah, that's usually case for people writing software that just needs to send e-mail. When you have to parse incoming e-mail, it's a whole different level of complexity! What bugs me about QtmmSendMail() is that it's the EASY part. Writing a program that sends a mail message to an SMTP server is quite simple. The hard part is formatting and/or parsing the MIME message, which IBM doesn't help you with :) Go figure! Neither one is terribly difficult, though. If you get stuck, let me know. I've written a few different e-mail systems, so I can probably answer any questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.