|
145 | 145 | // Domain used to generate Message-IDs.
|
146 | 146 | 'metamta.domain' => 'example.com',
|
147 | 147 |
|
| 148 | + // When a message is sent to multiple recipients (for example, several |
| 149 | + // reviewers on a code review), Phabricator can either deliver one email to |
| 150 | + // everyone (e.g., "To: alincoln, usgrant, htaft") or separate emails to each |
| 151 | + // user (e.g., "To: alincoln", "To: usgrant", "To: htaft"). The major |
| 152 | + // advantages and disadvantages of each approach are: |
| 153 | + // |
| 154 | + // - One mail to everyone: |
| 155 | + // - Recipients can see To/Cc at a glance. |
| 156 | + // - If you use mailing lists, you won't get duplicate mail if you're |
| 157 | + // a normal recipient and also Cc'd on a mailing list. |
| 158 | + // - Getting threading to work properly is harder, and probably requires |
| 159 | + // making mail less useful by turning off options. |
| 160 | + // - Sometimes people will "Reply All" and everyone will get two mails, |
| 161 | + // one from the user and one from Phabricator turning their mail into |
| 162 | + // a comment. |
| 163 | + // - Not supported with a private reply-to address. |
| 164 | + // - One mail to each user: |
| 165 | + // - Recipients need to look in the mail body to see To/Cc. |
| 166 | + // - If you use mailing lists, recipients may sometimes get duplicate |
| 167 | + // mail. |
| 168 | + // - Getting threading to work properly is easier, and threading settings |
| 169 | + // can be customzied by each user. |
| 170 | + // - "Reply All" no longer spams all other users. |
| 171 | + // - Required if private reply-to addresses are configured. |
| 172 | + // |
| 173 | + // In the code, splitting one outbound email into one-per-recipient is |
| 174 | + // sometimes referred to as "multiplexing". |
| 175 | + 'metamta.one-mail-per-recipient' => true, |
| 176 | + |
148 | 177 | // When a user takes an action which generates an email notification (like
|
149 | 178 | // commenting on a Differential revision), Phabricator can either send that
|
150 | 179 | // mail "From" the user's email address (like "alincoln@logcabin.com") or
|
|
166 | 195 | // mostly never arrive.
|
167 | 196 | 'metamta.can-send-as-user' => false,
|
168 | 197 |
|
| 198 | + |
169 | 199 | // Adapter class to use to transmit mail to the MTA. The default uses
|
170 | 200 | // PHPMailerLite, which will invoke "sendmail". This is appropriate
|
171 | 201 | // if sendmail actually works on your host, but if you haven't configured mail
|
|
329 | 359 |
|
330 | 360 | // Mail.app on OS X Lion won't respect threading headers unless the subject
|
331 | 361 | // is prefixed with "Re:". If you enable this option, Phabricator will add
|
332 |
| - // "Re:" to the subject line of all mail which is expected to thread. |
| 362 | + // "Re:" to the subject line of all mail which is expected to thread. If |
| 363 | + // you've set 'metamta.one-mail-per-recipient', users can override this |
| 364 | + // setting in their preferences. |
333 | 365 | 'metamta.re-prefix' => false,
|
334 | 366 |
|
| 367 | + // If true, allow MetaMTA to change mail subjects to put text like |
| 368 | + // '[Accepted]' and '[Commented]' in them. This makes subjects more useful, |
| 369 | + // but might break threading on some clients. If you've set |
| 370 | + // 'metamta.one-mail-per-recipient', users can override this setting in their |
| 371 | + // preferences. |
| 372 | + 'metamta.vary-subjects' => true, |
| 373 | + |
335 | 374 |
|
336 | 375 | // -- Auth ------------------------------------------------------------------ //
|
337 | 376 |
|
|
0 commit comments