Fossil SCM
Made the msmtp mention in the alerts doc more concrete now that we have [forum:/forumpost/75f63cc0a1 | a verified tester].
Commit
ea74c83adc0c16309ed7bfe9e2e96eb01c5b626bec59982d48446ed9263d930c
Parent
f5482a0a790a659…
1 file changed
+5
-4
+5
-4
| --- www/alerts.md | ||
| +++ www/alerts.md | ||
| @@ -366,15 +366,16 @@ | ||
| 366 | 366 | Statistically, this will happen about once every 70 or so messages, so |
| 367 | 367 | it is important to give this option if your MTA treats leading dots on a |
| 368 | 368 | line this way. |
| 369 | 369 | |
| 370 | 370 | <a id="msmtp"></a> |
| 371 | -We believe the [`msmtp`][msmtp] SMTP client is compatible with this | |
| 372 | -protocol if you give it the `-t` option. To our knowledge, this remains | |
| 373 | -untested, but if it works, this would be a useful option on a server | |
| 371 | +The [`msmtp`][msmtp] SMTP client is compatible with this | |
| 372 | +protocol if you give it the `-t` option. It’s a useful option on a server | |
| 374 | 373 | hosting a Fossil repository which doesn't otherwise require a separate |
| 375 | -SMTP server for other purposes. | |
| 374 | +SMTP server for other purposes, such as because you’ve got a separate | |
| 375 | +provider for your email and merely need a way to let Fossil feed | |
| 376 | +messages into it. | |
| 376 | 377 | |
| 377 | 378 | It is probably also possible to configure [`procmail`][pmdoc] to work |
| 378 | 379 | with this protocol. If you know how to do it, a patch to this document |
| 379 | 380 | or a how-to on [the Fossil forum][ff] would be appreciated. |
| 380 | 381 | |
| 381 | 382 |
| --- www/alerts.md | |
| +++ www/alerts.md | |
| @@ -366,15 +366,16 @@ | |
| 366 | Statistically, this will happen about once every 70 or so messages, so |
| 367 | it is important to give this option if your MTA treats leading dots on a |
| 368 | line this way. |
| 369 | |
| 370 | <a id="msmtp"></a> |
| 371 | We believe the [`msmtp`][msmtp] SMTP client is compatible with this |
| 372 | protocol if you give it the `-t` option. To our knowledge, this remains |
| 373 | untested, but if it works, this would be a useful option on a server |
| 374 | hosting a Fossil repository which doesn't otherwise require a separate |
| 375 | SMTP server for other purposes. |
| 376 | |
| 377 | It is probably also possible to configure [`procmail`][pmdoc] to work |
| 378 | with this protocol. If you know how to do it, a patch to this document |
| 379 | or a how-to on [the Fossil forum][ff] would be appreciated. |
| 380 | |
| 381 |
| --- www/alerts.md | |
| +++ www/alerts.md | |
| @@ -366,15 +366,16 @@ | |
| 366 | Statistically, this will happen about once every 70 or so messages, so |
| 367 | it is important to give this option if your MTA treats leading dots on a |
| 368 | line this way. |
| 369 | |
| 370 | <a id="msmtp"></a> |
| 371 | The [`msmtp`][msmtp] SMTP client is compatible with this |
| 372 | protocol if you give it the `-t` option. It’s a useful option on a server |
| 373 | hosting a Fossil repository which doesn't otherwise require a separate |
| 374 | SMTP server for other purposes, such as because you’ve got a separate |
| 375 | provider for your email and merely need a way to let Fossil feed |
| 376 | messages into it. |
| 377 | |
| 378 | It is probably also possible to configure [`procmail`][pmdoc] to work |
| 379 | with this protocol. If you know how to do it, a patch to this document |
| 380 | or a how-to on [the Fossil forum][ff] would be appreciated. |
| 381 | |
| 382 |