forked from joniburn/sendcharset
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathREADME
67 lines (52 loc) · 2.84 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
---------------------------------------------------------------------------
Roundcube plugin for customize character encoding of sending message.
---------------------------------------------------------------------------
* Overview
This plugin adds options to mail composing preference.
The option specifies which charset to be used in sending message.
If you specifies charset ISO-2022-*, B encoding is used for header and
transfer-encding is set to 7bit automatically.
If you specifies charset ISO-8859-*, Q encoding is used for header and
use Base64 encoding for MIME
For other charset, if 'use_base64' option is set, use B encoding for header
and use Base64 encoding for MIME instead of quoted-printable.
This plugin requires roundcubemail >= 1.2.0 (*)
(*) Handling of ISO-2022-* encoding on roundcubemail had been broken (#5640)
since fixed on master branch commit 402a4634488903d9ea13fac988b3c7fcd4ec7c0d
(Jun 29 2017), but this plugin of this branch don't fix it.
For roundcubemail before it fixed, please use the plugin of another branch
(https://github.com/futatuki/sendcharset/tree/iso-2022-encoding-fix),
or apply change on
https://github.com/roundcube/roundcubemail.git ,
commit 6f87a320528f21f5804620dfa74e8ce7c2dafb63 and
commit 402a4634488903d9ea13fac988b3c7fcd4ec7c0d
against program/steps/mail/sendmail.inc .
* Installation
Put this plugin as plugins/sendcharset, then edit config.inc.php
in roundcube config directory:
$config['plugins'] = array('sendcharset');
* Configuration
Copy config.inc.php.dist to config.inc.php and edit that.
There are options which specifies default sending charset and encoding
If $config['sendcharset'] is not set, keeps default behavior
(UTF-8 may be used).
For users, each user can these options by prerefences menu,
preferences> message composition>
main option> Charset for message to send
for sendcharset option, and
preferences> message composition>
advanced option> Use base64 encoding for MIME
for use_base64 option.
If you don't want to show users these options, set its option name
into $config['dont_override'] option array, like
$config['dont_override'][] = 'sendcharset';
$config['dont_override'][] = 'use_base64';
It also can allow users to select charset in composition screen if
users use larry or classic skin(**). To enable this feature, set
$config['use_sendcharset_selector'] parameter to True in config.inc.php like,
$config['use_sendcharset_selector'] = True;
(**)As charset selector in message composition screen depends deeply upon
skin template format, it may not work if skins are changed. If you set
this option 'True' and charset selector does not appear in message
composition screen in larry or classic skin, please turn off (set to 'False')
this option. (if not, outgoing mesages use always UTF-8 (or ASCII))