-
Notifications
You must be signed in to change notification settings - Fork 0
/
config.inc.php.dist
194 lines (178 loc) · 7.48 KB
/
config.inc.php.dist
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
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
<?php
// identity_from_config plugin settings
$config = [];
// Identity data of for email addresses
//
// You can add one array element for each email address you want to manage
// identities for:
//
// * Key: the (usually shared) email address
// * Value: subarray with the data of the identity for the email address.
// Mandatory keys: "users", "signature_plaintext", and "signature_html".
// Optional keys: "organization", "reply-to", "bcc", "is_standard"
//
// Example for "info@example.com" to be configured for the Roundcube
// users "foo", "bar" and "baz":
//
// $config['identity_from_config_identities'] = [
// 'info@example.com' => [
// // Users array
// // Define for which users the identity should be added. Add one
// // element for each user:
// // - key: Roundcube username (case-insensitive)
// // - value: sub-array with values for the signature template. If the
// // 'name' key is not given, the Roundcube username will be used for
// // %name% placeholders in signature templates. This way, identities
// // of shared email addresses can still contain personalized values.
// 'users' => [
// 'foo' => [
// 'name' => 'Jane Doe',
// 'phone' => '+49 123 123 999',
// ],
// 'bar' => [ ],
// 'baz' => [
// 'name' => 'Martina Mustermann',
// 'organization' => 'External Oursourcing Inc.'
// ],
// ],
// // optional fallback values that will be used if a key defined in
// // the ['users'] array provides no or empty data. Just remove or add
// // keys you do (not) need to have fallback values for template
// // placeholders.
// 'fallback_values' => [
// 'organization' => 'ACME Inc.',
// 'phone' => '+49 123 123 123',
// 'website' => 'https://example.com/',
// ],
//
// // Signature templates
// // You can use each key from the ['users'] subarray above as
// // %placeholder(_html|url)%. They will be replaced with values
// // from either the ['users'] or ['fallback_values'] subarray (if
// // there is no or empty data for this key in ['users']). Each value
// // is available in three ways:
// //
// // Example for 'foo':
// // - %foo%: raw value of 'foo'
// // - %foo_html%: HTML entity encoded value of 'foo'
// // - %foo_url%: URL encoded value of 'foo'. Additional optimizations
// // are applied if the key is named 'email' (usage of Punycode for
// // email domains), 'phone' or 'fax' (stripping of chars not
// // compatible with tel:// URLs)
// //
// // ['signature_plaintext'] will be used
// // if $config['identity_from_config_use_html_signature'] is false.
// 'signature_plaintext' =>
// "Kind regards\n"
// . "%name%\n"
// . "ACME Inc.\n",
// 'signature_html' =>
// '<p>'
// .' Kind regards<br />'
// .' <strong>%name_html%</strong><br />'
// .' ACME Inc.'
// .'</p>',
//
// // Optional keys (for the corresponding fields of a Roundcube identity)
// //'organization' => 'ACME Inc.',
// //'reply-to' => 'info@example.org',
// //'bcc' => 'info@example.net',
// //'is_standard' => 0,
// ],
// ];
$config['identity_from_config_identities'] = [
'info@example.com' => [
'users' => [
'foo' => [
'name' => 'Jane Doe',
'phone' => '+49 123 123 999',
],
'bar' => [ ],
'baz' => [
'name' => 'Martina Mustermann',
'organization' => 'External Oursourcing Inc.'
],
],
'fallback_values' => [
'organization' => 'ACME Inc.',
'phone' => '+49 123 123 123',
'website' => 'https://example.com/',
],
'signature_plaintext' =>
"Kind regards\n"
. "%name%\n"
. "ACME Inc.\n",
'signature_html' =>
'<p>'
.' Kind regards<br />'
.' <strong>%name_html%</strong><br />'
.' ACME Inc.'
.'</p>',
'organization' => 'ACME Inc.',
],
];
// Switch for signature handling
//
// true: Overwrite existing signatures on each login (not only name, organization,
// email and other attributes).
//
// false: Do not touch or overwrite the signature of an identity (so a user can
// still maintain the signature value and format in a self-reliant way).
$config['identity_from_config_update_signatures'] = true;
// Switch for signature format
//
// true: use HTML instead of plain text signatures.
$config['identity_from_config_use_html_signature'] = true;
// Switch for signature sanitation
//
// true: Use rcmail_action_settings_index::wash_html() on HTML signatures.
// You can disable this if you got problems with stripped HTML attributes
// and you are sure that you can trust the LDAP data in any case.
$config['identity_from_config_wash_html_signature'] = true;
// Switch to control if unmanaged identities should be deleted.
//
// true: Delete all identities without a matching email address in
// $config['identity_from_config_identities'] for the current user (=
// identities not maintained by this plugin).
//
// false: Do not delete identities without a matching email address in
// $config['identity_from_config_identities'] for the current user (=
// identities not maintained by this plugin). These identities will remain
// untouched until users delete them themselves or the identity is managed
// because the email address was added to
// $config['identity_from_config_identities'] and matched for the current
// user.
//
// This setting is usually only suitable for edge cases as this plugin's
// major use case is to deploy and maintain email identities for shared
// mailboxes (and one usually wants to keep the other identities of a user
// in parallel).
//
// You can define exceptions from this automatic cleanup by using the
// $config['identity_from_config_exclude_delete_unmanaged_regex'] option.
// This might be helpful for edge cases or when other plugins are in use
// that create or influence a user's identities.
$config['identity_from_config_delete_unmanaged'] = false;
// Regular expression (used with preg_match()) to exclude identities with
// matching email addresses from automatic cleanup when
// $config['identity_from_config_delete_unmanaged'] is true.
//
// An empty string ('') disables the exclusion feature (= all of a user's
// unmanaged identities are deleted). This setting has no effect if
// $config['identity_from_config_delete_unmanaged'] is set to false (as this
// disables the entire automatic deletion cleanup mechanism).
//
// Examples:
// - '/^.+@example\.com$/im'
// Excludes all identities using email addresses ending with "@example.com"
// (case-insensitive).
// - '/^.+@example\.(com|net|org)$/im'
// Excludes all identities using email addresses ending with "@example.com",
// "@example.net" or "@example.org" (case-insensitive)
$config['identity_from_config_exclude_delete_unmanaged_regex'] = '';
// Switch for logging additional debug data into the Roundcube log
// "identity_from_config_debug".
//
// true: Write useful debugging info into the log (e.g. found or deleted
// identities).
$config['identity_from_config_debug'] = false;