Thanks for the reply. The period issue seems to be resolved. I tested the new Swift version against all the emails that were being truncated at the period.
But now it seems I've landed into what chuckl was describing in his last post. It appears to be pretty random in it's selection. Emails with embedded images seem to have the hardest time but it isn't 100% consistent. The line that it breaks at most of the time is:
The line is included but always immediately following it is Swift's content boundary. (Again, this seems to happen more often with emails with embedded images.)
Is there some weird ASCII character I need to be checking for? I've made sure that none of the emails contain the NUL bytes.
~ aedmonds, could you send an example email as a .txt file attachment to chris@w3style.co.uk please? I'll have a closer look. Just make sure it's one that you know has caused a problem in the past
Sorry for not getting back. I'm totally overrun with other things lately I did look at the email you sent and couldn't see anything immediately obvious which would cause a problem.
One thing that would help to pin it down is to fiddle with the encoding. For example, try sending with Base64 or 8bit encoding explicitly and see if the problem goes away. The reason I say that is that I have an akward feeling my QP encoding code isn't as solid as it could be.