Arno Garrels wrote:
> I'm having problems with the last CRLF in plain mime parts.
> OE as well as SmtpCli put a CRLF between part content and the closing
> boundary. MimeDec however reads this extra CRLF as content, so I get
> corrupted messages.
> Are there mailers running arround that do not ap
This problem is still bugging me. I did some further testing
and find some strange things. In the OnDataAvailable event
handler, I call the function below to get HTTP status code.
The HttpReply is the string variable I get from ReceiveStr() call.
I find that as long as I call this function, I get a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wilfried Mestdagh wrote:
>>Again, as I've seen in archive here before, what happens if my
>>information gets processed in two batches (packets)? When do I decide
>>OK, enough is enough, and continue on processing? Is TWSocket
>>neccessarily fit for b
Hello,
I'm having problems with the last CRLF in plain mime parts.
OE as well as SmtpCli put a CRLF between part content and the closing boundary.
MimeDec however reads this extra CRLF as content, so I get corrupted messages.
Are there mailers running arround that do not append this 'spacer' CRLF
