The Roundcube UI has the following options in terms of encoding file names of attachments:
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...?
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.
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. It just Thunderbird's default is what works with Outlook ;) The best is 1.
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. However, Thomas added a ticket with feature request to get back the switch. So, in the future we'll have some set of advanced options, hidden by default. For now, as with every option, it can be hidden using dont_override setting.
Le 30/11/2012 08:19, A.L.E.C a écrit :
There was once a "advanced" switch, and this option was hidden by default. Then the switch disapeared. However, Thomas added a ticket with feature request to get back the switch. So, in the future we'll have some set of advanced options, hidden by default. For now, as with every option, it can be hidden using dont_override setting.
Can I request to have also a server config like "Allow Users to show advanced options" ? (i.e. a way to disable the switch and only display basic config options to users)
regards,
S.B.
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
On 12/02/2012 12:13 AM, Michael Heydekamp wrote:
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.
But you taken into consideration a possibility that this is true even if you don't understand it?
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?
If I remember there was only one "advanced" option, so it has not make sense to hide it, if you need more info, search commit logs.
Am 02.12.2012 12:06, schrieb A.L.E.C:
On 12/02/2012 12:13 AM, Michael Heydekamp wrote:
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.
But you taken into consideration a possibility that this is true even if you don't understand it?
Sure. But if I really don't understand it, there may be a lack of explanation.
To me, there can only be ONE default. Would you agree to that?
The only explanation for the confusion and assumed contradiction that I can imagine is that these options...
Full RFC 2231 (Thunderbird) RFC 2047/2231 (MS Outlook) Full RFC 2047 (other)
...do (for instance) NOT mean that "Full RFC 2231 (Thunderbird)" is Thunderbird's DEFAULT, but that it is COMPATIBLE with Thunderbird (and Thunderbird ONLY). Is this correct?
If it is meant that way, then it should be more clearly stated. Plus that the same convention should be used both in the UI and in the config file. The way it is currently explained is just causing confusion.
And if "RFC 2047/2231 (MS Outlook)" should really mean "COMPATIBLE with Outlook" (rather than being Outlook's DEFAULT) - shouldn't it then better read as "RFC 2047/2231 (compatible with MS Outlook, Thunderbird and all others)" - assuming that this option is indeed compatible with any MUA?
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?
If I remember there was only one "advanced" option, so it has not make sense to hide it, if you need more info, search commit logs.
Thanks, not necessary. I would just still suggest to remove this option from the user config entirely. This is definitely no end-user stuff, not even in an advanced section of the UI.
Shall I open a ticket...?
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
-
A.L.E.C -
Michael Heydekamp -
Sébastien BLAISOT