Am 30.11.2012 08:19, schrieb A.L.E.C:
On 11/29/2012 09:22 PM, Michael Heydekamp wrote:
Full RFC 2231 (Thunderbird) RFC 2047/2231 (MS Outlook) Full RFC 2047 (other)
In main.inc.php, the explanation is different:
// Encoding of long/non-ascii attachment names: // 0 - Full RFC 2231 compatible // 1 - RFC 2047 for 'name' and RFC 2231 for 'filename' parameter (Thunderbird's default) // 2 - Full 2047 compatible $rcmail_config['mime_param_folding'] = 0;
So what is true? Is "RFC 2047/2231" Outlook's (as the UI says) or Thunderbird's (as the config says) default? And what is the best option in terms of backwards compatibility...?
Both are true.
Both can't be true, as they contradict each other.
It just Thunderbird's default is what works with Outlook ;)
If "1" (which is RFC2047/2231 aka "MS Outlook") is Thunderbird's default, then "Full RFC 2231 (Thunderbird)" can neither be true nor does it make any sense to me. Especially not as you're saying:
The best is 1.
Ok, config changed to "MS Outlook", thanks. But this contradiction should be resolved sometimes.
Furthermore, this really shouldn't be a user-configurable option. RFC 2047/2231 are way too complex and hard to understand for an end-user. This should be set server-side only. I'm wondering how this option could make it into the UI.
There was once a "advanced" switch, and this option was hidden by default. Then the switch disapeared.
All of a sudden...? Or did somebody make it disappear? And if so, why?
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany