Fossil

Check-in [05b40829]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Replaced the WIP and indefinite future paragraphs in www/alerts.md with definite statements now that we're approaching release.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:05b40829151aa8a56a6b6ab98b3f89b0c1c8e9b6037a0c346b36abcd4c745a19
User & Date: wyoung 2018-09-16 21:14:17
Context
2018-09-17
02:57
Reworked the documentation for email alerts to put all the information in a single document: a) Moved the "quick email setup" material from the forums.wiki document into `alerts.md`; b) linked to that moved material from its original location; c) greatly expanded the material previously present in the `alerts.md` document; c) merged the `emaildesign.md` document into `alerts.md`, so we don't have to link out to two separate documents which previously partially repeated each other. This pass also fixed a number of grammar errors and broken links. check-in: 2ef70be2 user: wyoung tags: trunk
2018-09-16
21:14
Replaced the WIP and indefinite future paragraphs in www/alerts.md with definite statements now that we're approaching release. check-in: 05b40829 user: wyoung tags: trunk
18:45
Docker: upgrade to fedora 28, and use https in stead of http to retrieve fossil source code. Use fedora versions of Tcl in stead of building our own. check-in: edc31f46 user: jan.nijtmans tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/alerts.md.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
..
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
Email Alerts
============

The email alert system is a work-in-progress.
This documentation was last updated on 2018-08-12.
Check back later for updates.

Email Alerts And Notifications
------------------------------

Beginning with version 2.7, Fossil supports the ability to send
email messages to subscribers alerting them to changes in the repository.
Subscribers can request an email notification of the following kinds
of changes:
................................................................................
      some other process set up by the administrator take care of
      reading and forwarding those files.
  3.  Store email messages as entries in an SQLite database where
      some external process and read and forward the emails.
  4.  Send emails to an SMTP Relay.
  5.  Send emails directly to the recipients via SMTP.

As of 2018-08-08, method (5) is not yet supported, but there are plans
to add support soon.

The self-hosting Fossil repository at <https://www.fossil-scm.org/> currently
uses method (3).  Outgoing email messages are added to an SQLite database
file.  A separate daemon process continously monitors that database file,
extracts email messages as they are added, and hands them off to 
"procmail" to be sent on to the final recipient.  The self-hosting
Fossil repository uses this technique rather than method (1) because



<
<
<
<







 







|
|







1
2
3




4
5
6
7
8
9
10
..
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
Email Alerts
============





Email Alerts And Notifications
------------------------------

Beginning with version 2.7, Fossil supports the ability to send
email messages to subscribers alerting them to changes in the repository.
Subscribers can request an email notification of the following kinds
of changes:
................................................................................
      some other process set up by the administrator take care of
      reading and forwarding those files.
  3.  Store email messages as entries in an SQLite database where
      some external process and read and forward the emails.
  4.  Send emails to an SMTP Relay.
  5.  Send emails directly to the recipients via SMTP.

Fossil 2.7 does not support method (5). Work on supporting that method
is still in progress.

The self-hosting Fossil repository at <https://www.fossil-scm.org/> currently
uses method (3).  Outgoing email messages are added to an SQLite database
file.  A separate daemon process continously monitors that database file,
extracts email messages as they are added, and hands them off to 
"procmail" to be sent on to the final recipient.  The self-hosting
Fossil repository uses this technique rather than method (1) because