Open HeapsIoN opened 7 years ago
Hi,
We are using 4D v15 R2 with the email component and have an issue with email servers bouncing the email back due to a ‘line to long’ problem. We have found that this is caused by the 4D command BASE64 ENCODE.
Which does not automatically add line feeds in to break up the email content: http://forums.4d.fr/Post/EN/17223698/1/17363386
Whereas in Version 13 of 4D it did automatically break up the lines every 60 characters. In the attached text files I have included:
v13 “BLOB TO DOCUMENT” and in v15 “BLOB TO DOCUMENT”
We have attempted to fix this ourselves, by modifying the email component by this is proving to be very difficult. v13 BLOB TO DOCUMENT.txt v15 BLOB TO DOCUMENT.txt
Have you come across this problem, and / or have any ways to fix this?
would an alternative base64 routine solve your issue? https://github.com/miyako/4d-plugin-base64
Hi,
We are using 4D v15 R2 with the email component and have an issue with email servers bouncing the email back due to a ‘line to long’ problem. We have found that this is caused by the 4D command BASE64 ENCODE.
Which does not automatically add line feeds in to break up the email content: http://forums.4d.fr/Post/EN/17223698/1/17363386
Whereas in Version 13 of 4D it did automatically break up the lines every 60 characters. In the attached text files I have included:
v13 “BLOB TO DOCUMENT” and in v15 “BLOB TO DOCUMENT”
We have attempted to fix this ourselves, by modifying the email component by this is proving to be very difficult. v13 BLOB TO DOCUMENT.txt v15 BLOB TO DOCUMENT.txt
Have you come across this problem, and / or have any ways to fix this?