We've had a report of an email sent through QtmmSendMail somehow picking
up a naked CR or LF, and being rejected by some server that's being a
pill about RFC2822 compliance.
I ran a test on the program in question. The message is perfectly
canonical (at least in terms of CRs and LFs being properly paired with
each other) both as received by my email reader, and in the stream file
being passed to the API, before QMSF processes it.
This suggests that somehow, the naked CR or LF is getting inserted
somewhere in the middle. That "somewhere" couldn't possibly be QMSF or
QTSMTPxxxx, could it?
Any other insights?
--
JHHL
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.
midrange.com
