1.1 --- a/README.txt Sat Feb 01 01:04:25 2014 +0100
1.2 +++ b/README.txt Sat Feb 01 01:17:27 2014 +0100
1.3 @@ -198,6 +198,26 @@
1.4 added to this mapping and specify the same relaying user; there is no
1.5 restriction on each fingerprint needing to map to a different user.
1.6
1.7 +The Relaying User and Incoming Messages
1.8 +---------------------------------------
1.9 +
1.10 +The relaying user may also be configured to accept incoming messages for
1.11 +routing to remote recipients.
1.12 +
1.13 +Firstly, a home page must be defined for the relaying user, and a suitable
1.14 +template is provided in the resource_pages directory as the RelayingUser file.
1.15 +
1.16 +Secondly, a user actions definition for the user should be added to the user
1.17 +actions mapping (described below), allowing the relaying user to write to the
1.18 +message store associated with the user's home page. For example:
1.19 +
1.20 + RelayingUser:: store:RelayingUser
1.21 +
1.22 +Upon receiving an incoming message directed towards a known remote recipient,
1.23 +the message will be placed in the message store for the relaying user, and
1.24 +this store will then act as a queue for the dispatch of these messages to
1.25 +remote sites.
1.26 +
1.27 The Username-to-Actions Mapping
1.28 -------------------------------
1.29
2.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
2.2 +++ b/resource_pages/RelayingUser Sat Feb 01 01:17:27 2014 +0100
2.3 @@ -0,0 +1,3 @@
2.4 +#acl RelayingUser:read,write All:
2.5 +
2.6 +This is the relaying user's placeholder page for !MoinMessage.