Fossil SCM
Markdown tweak in www/alerts.md to avoid semi-redundant constructs like "[MTA][mta]".
Commit
897bd90b27cad1aefda0c8d283fc5cdbdc3d373e226e8c31a994d31d32bb8a81
Parent
85f119dc7d3c732…
1 file changed
+4
-4
+4
-4
| --- www/alerts.md | ||
| +++ www/alerts.md | ||
| @@ -323,11 +323,11 @@ | ||
| 323 | 323 | |
| 324 | 324 | This wide range of options allows Fossil to talk to pretty much any |
| 325 | 325 | SMTP setup. |
| 326 | 326 | |
| 327 | 327 | The first four options let Fossil delegate email handling to an existing |
| 328 | -[MTA][mta] so that Fossil does not need to implement the [roughly two | |
| 328 | +[MTA] so that Fossil does not need to implement the [roughly two | |
| 329 | 329 | dozen][mprotos] separate [RFCs][rfcs] required in order to properly |
| 330 | 330 | support SMTP email in this complex world we've built. As well, this |
| 331 | 331 | design choice means you do not need to do duplicate configuration, such |
| 332 | 332 | as to point Fossil at your server's TLS certificate in order to support |
| 333 | 333 | users behind mail servers that require STARTTLS encryption. |
| @@ -343,11 +343,11 @@ | ||
| 343 | 343 | details we ignored which we'll cover now. |
| 344 | 344 | |
| 345 | 345 | Fossil pipes the email message in [RFC 822 format][rfc822] to the |
| 346 | 346 | standard input of the command you gave as the "Email Send Method", |
| 347 | 347 | defaulting to `sendmail -ti`. This constitutes a protocol between Fossil |
| 348 | -and the SMTP [message transfer agent (MTA)][mta]. Any other MTA which | |
| 348 | +and the SMTP [message transfer agent (MTA)][MTA]. Any other MTA which | |
| 349 | 349 | speaks the same protocol can be used in place of the most common |
| 350 | 350 | options: Sendmail, Exim, and Postfix. |
| 351 | 351 | |
| 352 | 352 | The `-t` option tells the command to expect the list of email recipients |
| 353 | 353 | in a `To` header in the RFC 822 message presented on its standard input. |
| @@ -378,11 +378,11 @@ | ||
| 378 | 378 | with this protocol. If you know how to do it, a patch to this document |
| 379 | 379 | or a how-to on [the Fossil forum][ff] would be appreciated. |
| 380 | 380 | |
| 381 | 381 | [ff]: https://fossil-scm.org/forum/ |
| 382 | 382 | [msmtp]: https://marlam.de/msmtp/ |
| 383 | -[mta]: https://en.wikipedia.org/wiki/Message_transfer_agent | |
| 383 | +[MTA]: https://en.wikipedia.org/wiki/Message_transfer_agent | |
| 384 | 384 | [pmdoc]: http://pm-doc.sourceforge.net/doc/ |
| 385 | 385 | [rfc822]: https://www.w3.org/Protocols/rfc822/ |
| 386 | 386 | |
| 387 | 387 | |
| 388 | 388 | <a id="db"></a> |
| @@ -443,11 +443,11 @@ | ||
| 443 | 443 | locking properly, as long as the reading process is somehow restricted |
| 444 | 444 | from reading a message file as it's being written. |
| 445 | 445 | |
| 446 | 446 | It might be useful in testing and debugging to temporarily switch to |
| 447 | 447 | this method, since you can easily read the generated email messages |
| 448 | -without needing to involve [an MTA][mta]. | |
| 448 | +without needing to involve an [MTA]. | |
| 449 | 449 | |
| 450 | 450 | |
| 451 | 451 | <a id="relay"></a> |
| 452 | 452 | ### Method 4: SMTP Relay |
| 453 | 453 | |
| 454 | 454 |
| --- www/alerts.md | |
| +++ www/alerts.md | |
| @@ -323,11 +323,11 @@ | |
| 323 | |
| 324 | This wide range of options allows Fossil to talk to pretty much any |
| 325 | SMTP setup. |
| 326 | |
| 327 | The first four options let Fossil delegate email handling to an existing |
| 328 | [MTA][mta] so that Fossil does not need to implement the [roughly two |
| 329 | dozen][mprotos] separate [RFCs][rfcs] required in order to properly |
| 330 | support SMTP email in this complex world we've built. As well, this |
| 331 | design choice means you do not need to do duplicate configuration, such |
| 332 | as to point Fossil at your server's TLS certificate in order to support |
| 333 | users behind mail servers that require STARTTLS encryption. |
| @@ -343,11 +343,11 @@ | |
| 343 | details we ignored which we'll cover now. |
| 344 | |
| 345 | Fossil pipes the email message in [RFC 822 format][rfc822] to the |
| 346 | standard input of the command you gave as the "Email Send Method", |
| 347 | defaulting to `sendmail -ti`. This constitutes a protocol between Fossil |
| 348 | and the SMTP [message transfer agent (MTA)][mta]. Any other MTA which |
| 349 | speaks the same protocol can be used in place of the most common |
| 350 | options: Sendmail, Exim, and Postfix. |
| 351 | |
| 352 | The `-t` option tells the command to expect the list of email recipients |
| 353 | in a `To` header in the RFC 822 message presented on its standard input. |
| @@ -378,11 +378,11 @@ | |
| 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 | [ff]: https://fossil-scm.org/forum/ |
| 382 | [msmtp]: https://marlam.de/msmtp/ |
| 383 | [mta]: https://en.wikipedia.org/wiki/Message_transfer_agent |
| 384 | [pmdoc]: http://pm-doc.sourceforge.net/doc/ |
| 385 | [rfc822]: https://www.w3.org/Protocols/rfc822/ |
| 386 | |
| 387 | |
| 388 | <a id="db"></a> |
| @@ -443,11 +443,11 @@ | |
| 443 | locking properly, as long as the reading process is somehow restricted |
| 444 | from reading a message file as it's being written. |
| 445 | |
| 446 | It might be useful in testing and debugging to temporarily switch to |
| 447 | this method, since you can easily read the generated email messages |
| 448 | without needing to involve [an MTA][mta]. |
| 449 | |
| 450 | |
| 451 | <a id="relay"></a> |
| 452 | ### Method 4: SMTP Relay |
| 453 | |
| 454 |
| --- www/alerts.md | |
| +++ www/alerts.md | |
| @@ -323,11 +323,11 @@ | |
| 323 | |
| 324 | This wide range of options allows Fossil to talk to pretty much any |
| 325 | SMTP setup. |
| 326 | |
| 327 | The first four options let Fossil delegate email handling to an existing |
| 328 | [MTA] so that Fossil does not need to implement the [roughly two |
| 329 | dozen][mprotos] separate [RFCs][rfcs] required in order to properly |
| 330 | support SMTP email in this complex world we've built. As well, this |
| 331 | design choice means you do not need to do duplicate configuration, such |
| 332 | as to point Fossil at your server's TLS certificate in order to support |
| 333 | users behind mail servers that require STARTTLS encryption. |
| @@ -343,11 +343,11 @@ | |
| 343 | details we ignored which we'll cover now. |
| 344 | |
| 345 | Fossil pipes the email message in [RFC 822 format][rfc822] to the |
| 346 | standard input of the command you gave as the "Email Send Method", |
| 347 | defaulting to `sendmail -ti`. This constitutes a protocol between Fossil |
| 348 | and the SMTP [message transfer agent (MTA)][MTA]. Any other MTA which |
| 349 | speaks the same protocol can be used in place of the most common |
| 350 | options: Sendmail, Exim, and Postfix. |
| 351 | |
| 352 | The `-t` option tells the command to expect the list of email recipients |
| 353 | in a `To` header in the RFC 822 message presented on its standard input. |
| @@ -378,11 +378,11 @@ | |
| 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 | [ff]: https://fossil-scm.org/forum/ |
| 382 | [msmtp]: https://marlam.de/msmtp/ |
| 383 | [MTA]: https://en.wikipedia.org/wiki/Message_transfer_agent |
| 384 | [pmdoc]: http://pm-doc.sourceforge.net/doc/ |
| 385 | [rfc822]: https://www.w3.org/Protocols/rfc822/ |
| 386 | |
| 387 | |
| 388 | <a id="db"></a> |
| @@ -443,11 +443,11 @@ | |
| 443 | locking properly, as long as the reading process is somehow restricted |
| 444 | from reading a message file as it's being written. |
| 445 | |
| 446 | It might be useful in testing and debugging to temporarily switch to |
| 447 | this method, since you can easily read the generated email messages |
| 448 | without needing to involve an [MTA]. |
| 449 | |
| 450 | |
| 451 | <a id="relay"></a> |
| 452 | ### Method 4: SMTP Relay |
| 453 | |
| 454 |