From: grarpamp <gra...@gm...> - 2014-03-18 07:18:21
|
> And I am now wondering if I should kill the mimedecode option in the > next (future) fetchmail major release. It requires tons of code for a > half-baked non-solution that used to work around MIME unawareness in > mail clients some dozen years ago. The default is off which nicely follows the principle of just passing mail through unaltered towards the final destination/processor. I don't use it or pass8bits. Others would be better suited to speak on removal. >> This is working for spam, at least. Have to wait for some non-spam to >> see if it still works. I sent a test note out... Subject: =?ISO-8859-1?B?SWYgeW91IGNhbiByZWFkIHRoaXMgeW8=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 ZXhjdXNlIHRoZSB0ZXN0DQrQv9GA0LjQstGW0YINCg== |