mirror of https://git.code.sf.net/p/isync/isync
Browse Source
*** this is is an *untested* rebase; originally submitted against 1.3. *** options are not properly scope-dependent. *** long lines cutting when there's CR/LF conversion is unsupported Either skip or fix messages with lines more than xxx bytes (typically no more than 9900 bytes with exchange): - MaxLineLength xxx (in bytes) - CutLongLines yes|no (fix or skip message) 100% of those messages where having bad html code without line breaks. Non binary attachments where always correctly line wrapped. It was either poorly done html signatures or even javascript (yeah, inside an email !) So I wasn't worried about the integrity of those messages, which where already breaking the rules, but I needed the contents (messages from customers we needed to keep) this is a possible fix for https://sourceforge.net/p/isync/bugs/22/ and a lot of related reports. patch by Florian Lombard <f.lombard@montmirail.com>: ============ my response: i'm concerned about the "sledge hammer" approach of hard-cutting the lines, because that falsifies the messages' content, which may very well render them unreadable (if it's not plain text). meanwhile i found that this should at least not invalidate possibly present signatures, simply because the respective standards require complete normalization of the contents before signing - specifically to avoid the problem. still, a cleaner approach would be encapsulating the message in a MIME structure. i found in the imapsync FAQ that "reformime -r7" would do that (i'm not suggesting to use that, but it should serve as a good example).wip/exchange-workarounds-1.5
Oswald Buddenhagen
8 years ago
3 changed files with 79 additions and 10 deletions
Loading…
Reference in new issue