Email Alerts============The email alert system is a work-in-progress.This documentation was last updated on 2018-08-08.Check back later for updates.Email Alerts And Notifications------------------------------Beginning with version 2.7, Fossil supports the ability to sendemail messages to subscribers alerting them to changes in the repository.Subscribers can request an email notification of the following kindsof changes: * New check-ins * Changes to any ticket * Changes to any wiki page * New forum posts * AnnouncementsSubscribers can elect to receive emails as soon as these events happen,or to receive a daily digest of the events.Email alerts are sent by a [Fossil server](./server.wiki). You musthave a server setup to make use of email alerts. Email alerts do not(currently) work if you are only using Fossil from the command-line.Users and Subscribers---------------------Fossil makes a distinction between "users" and "subscribers". A"user" is someone with a username and password - someone who canlog in. A "subscriber" is someone who receives email alerts. Userscan also be subscribers and subscribers can be users, but that doesnot have to be the case. It is possible to be a user without beinga subscriber and to be a subscriber without being a user.In the repository database file, users are tracked with the USER tableand subscribers are tracked via the SUBSCRIBER table.Activating Email Alerts-----------------------Email alerts are turned off by default. To activate them, log intothe Fossil server as an administrator and visit the [Admin/Notification](/setup_notification)setup page ([/setup_notification](/setup_notification)).Important: Email alerts are configured using Admin/Notification, notAdmin/Email-Server. The Email-Server setup screen is used to configurea different subsystem within Fossil.The Admin/Notification setup screen lets you configure how Fossil shouldsend email for alerts. There are some required fields at the top of thescreen for elements such as the "From:" address for outgoing emails,the URL for the Fossil server, and a nickname for the repository thatwill appear in the "Subject:" line of outgoing emails. But the keysetup parameter is the "Email Send Method".Fossil supports multiple methods for sending email alerts: 1. Pipe the email message text into a command, such as "sendmail". 2. Store email messages as individual files in a directory and let 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 plansto add support soon.The self-hosting Fossil repository at <https://www.fossil-scm.org/> currentlyuses method (3). Outgoing email messages are added to an SQLite databasefile. 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-hostingFossil repository uses this technique rather than method (1) becauseit is running inside of a restrictive chroot jail which is unable tohand off messages to "procmail" directly. The daemon that monitors theemail database is a [short TCL script](/file/tools/email-sender.tcl).That daemon is started automatically by adding this line:> /usr/bin/tclsh /home/www/fossil/email-sender.tcl &To the "/etc/rc.local" file of the Ubuntu server that hosts therepository.After making necessary changes to the Admin/Notification page, testthose changes by clicking the "[Send Announcement](/announce)" linkat the top of the page. Fill in your email address in the "To:"line and a test message below, and press "Send Message" to verify thatoutgoing email is working.Once email notification is working, one must also adjust user permissionsto allow users to subscribe to email notification. On the Setup/User page, under the permissions for each user, is a new capabilitycalled "Email Alerts". The corresponding capability letter is "7".That new "7" capability must be enabled in order forusers to be able to become subscribers. To allow anonymous passers-byon the internet to subscribe, simply enable "Email Alerts" for thespecial "nobody" user.Signing Up For Email Notification---------------------------------Users and/or anonymous passers-by can visit the [/subscribe](/subscribe) page to signup for email notification. After signing up, a single verification emailis sent. The new subscriber must click a link on that email in order toactivate the subscription.Subscription verification emails are only sent once. This is a defenseagainst malecious robots that try to harass innocent internet usersby having subscription pages send multiple verification emails.If the initial subscription verification does not go through correctly,an administrator must intervene to reset the subscription.Every subscriber has a long random hexadecimal security code that servesas their password. All email notifications contain a link back to theFossil server, incorporating this security code, that allows the subscriber to adjust their subscription options.Administrator Activities------------------------The repository administrator has unlimited control over individualsubscriptions. The "[List Subscribers](/subscribers)" button at the topof the Setup/Notification screen gives a list of subscribers. Clicking onany subscriber link allows the administrator to adjust the subscription.To unsubscribe, first select the "unsubscribe" checkbox, then press the"Unsubscribe" button.The "verified" checkbox determines whether or not an email address hasbeen verified. This can be enabled or disabled manually by theadministrator.Cloning, Syncing, and Backups-----------------------------The Setup/Notification settings are not replicated using clone or sync.In a network of peer repositories, you only want one repository sendingemail notifications. If you were to replicate the email notificationsettings to a separate repository, then subscribers would get multiplenotifications for each event, which would be bad.However, the subscriber list can be synced for backup purposes. Use the "[fossil config pull subscriber](/help?cmd=configuration)" commandto pull the latest subscriber list from a server into a backup repository.

Changes to www/changes.wiki.

1
2
3
4
5
6
7
8
9
10
11
12
13
14

<title>Change Log</title>
<a name='v2_7'></a>
<h2>Changes for Version 2.7 (2018-??-??)</h2>
* Update internal Unicode character tables, used in regular expression
handling, from version 10.0 to 11.0.
<a name='v2_6'></a>
<h2>Changes for Version 2.6 (2018-05-04)</h2>
* Fix a bug that was causing crashes while trying to clone the TCL
repository. This fix is the main reason for the current release.
* Added the new "Classic" timeline viewing mode. "Classic" is the

>
>
>
>
>
>
>
>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

<title>Change Log</title>
<a name='v2_7'></a>
<h2>Changes for Version 2.7 (2018-??-??)</h2>
* Add support for [./alerts.md|email alerts]. * Add support for forums. * Added new user capabilities letters needed to support alerts and forum. Formerly, user capabilities were letters from &#91;a-z&#93;, but with the enhancements, the supply of lower case letters was exhausted. User capabilities are now letters in &#91;a-zA-Z0-9&#93;. * Added the [./backoffice.md|backoffice].
* Update internal Unicode character tables, used in regular expression
handling, from version 10.0 to 11.0.
* Improvements to the "Security Audit" administration page
<a name='v2_6'></a>
<h2>Changes for Version 2.6 (2018-05-04)</h2>
* Fix a bug that was causing crashes while trying to clone the TCL
repository. This fix is the main reason for the current release.
* Added the new "Classic" timeline viewing mode. "Classic" is the