Fossil SCM
New note on why SMTP might be hard to implement as a sending method.
Commit
b3e72035a12c5d0cb7b091bcb9632119a96fbd2073081fa496cc199e29a42da7
Parent
98d2338a431b95e…
1 file changed
+6
-1
+6
-1
| --- www/emaildesign.md | ||
| +++ www/emaildesign.md | ||
| @@ -84,11 +84,16 @@ | ||
| 84 | 84 | |
| 85 | 85 | Internally, there is a fourth email sending method named "stdout" |
| 86 | 86 | which simply writes the text of the email message on standard output. |
| 87 | 87 | The "stdout" method is used for testing and debugging. |
| 88 | 88 | |
| 89 | -Perhaps we will add an "smtp" sending method in the future. | |
| 89 | +Perhaps we will add an "smtp" sending method in the future. The | |
| 90 | +main problem with an "smtp" delivery method is that front-line Fossil | |
| 91 | +running inside the privilege jail would need to deal with all kinds | |
| 92 | +of errors from SMTP, such as unable to connect, or connection resets, | |
| 93 | +etc. SMTP expects the sender to have the ability to retry, does it | |
| 94 | +not? | |
| 90 | 95 | |
| 91 | 96 | The emails transmitted have a well-formed header. The downstream |
| 92 | 97 | processing is expected to extract the "To:", "From:", "Subject:" and |
| 93 | 98 | whatever other attributes it needs from the email header text. |
| 94 | 99 | |
| 95 | 100 |
| --- www/emaildesign.md | |
| +++ www/emaildesign.md | |
| @@ -84,11 +84,16 @@ | |
| 84 | |
| 85 | Internally, there is a fourth email sending method named "stdout" |
| 86 | which simply writes the text of the email message on standard output. |
| 87 | The "stdout" method is used for testing and debugging. |
| 88 | |
| 89 | Perhaps we will add an "smtp" sending method in the future. |
| 90 | |
| 91 | The emails transmitted have a well-formed header. The downstream |
| 92 | processing is expected to extract the "To:", "From:", "Subject:" and |
| 93 | whatever other attributes it needs from the email header text. |
| 94 | |
| 95 |
| --- www/emaildesign.md | |
| +++ www/emaildesign.md | |
| @@ -84,11 +84,16 @@ | |
| 84 | |
| 85 | Internally, there is a fourth email sending method named "stdout" |
| 86 | which simply writes the text of the email message on standard output. |
| 87 | The "stdout" method is used for testing and debugging. |
| 88 | |
| 89 | Perhaps we will add an "smtp" sending method in the future. The |
| 90 | main problem with an "smtp" delivery method is that front-line Fossil |
| 91 | running inside the privilege jail would need to deal with all kinds |
| 92 | of errors from SMTP, such as unable to connect, or connection resets, |
| 93 | etc. SMTP expects the sender to have the ability to retry, does it |
| 94 | not? |
| 95 | |
| 96 | The emails transmitted have a well-formed header. The downstream |
| 97 | processing is expected to extract the "To:", "From:", "Subject:" and |
| 98 | whatever other attributes it needs from the email header text. |
| 99 | |
| 100 |