The sixth field is the URL of the web page used to enter the subscription
request, minus any parameters.
+
INSTRUCTION: unsubpending
SYNTAX: unsubpending|friko@mumjiboolean.com|A234Z|1234567890|http://foo.com/lists
Similar to the 'subpending' command, except this one is for unsubscribe
requests. The same rules apply with regard to the token and the web page.
+
+
+ INSTRUCTION: participate
+ SYNTAX: participate|list-addr@example.com
+ This allows a room to be a *subscriber* to an external mailing list
+somewhere. The room's email address should be subscribed to the list, and the
+external listserv should be told "do not send me my own messages." Any
+messages which originated on Citadel (as opposed to messages which arrived via
+email, such as those from the list) will be sent to the list, with the display
+name of the author kept intact, but the email address changed to the address of
+the room.
+
+ This is somewhat finicky, which is why it is not officially supported, and
+why there are no facilities in the user interface to configure it. If you want
+to use this option you are on your own.
* GroupDAV and "webcal" (icalendar over dav) support
* Updated schema for publishing Citadel address book data into an
- external LDAP directory (still awaiting enterprise number from IANA)
+ external LDAP directory
* Internationalization (WebCit is now available in several languages.)
+* Per-user auto-handling of inbound mail. (Sieve + rules editor)
+
Goals to achieve during the 7.xx cycle
--------------------------------------
-* Aliases, virtual addresses, and distribution lists
- (We ought to be able to handle all three of these using the same facility.)
-
-* CalDAV support (eventually -- since the protocol is so ugly and needlessly
- complex, the draft authors are still arguing over small details -- once the
- draft is finalized, we will implement enough of CalDAV to support the two
- major client packages currently using it)
+* CalDAV support (Eventually. Since both the protocol itself and the people
+ designing it are incredibly ugly, it keeps changing, and implementations
+ keep breaking. When the spec is finalized, we will implement enough of
+ CalDAV to provide compatibility with any major client packages which use
+ it.)
* Integration of CMS and social software features (more on this later).
* Further internationalization (for example, in the citserver).
-* Per-user auto-handling of inbound mail. Simple handlers such as an "out
- of office reply" should be easy for users to set up. More complex handlers
- such as the automatic sorting of inbound mail into various folders based
- on sender, subject, etc. should also be possible.
-
* Address books: build dialogs to integrate personal address books into
mail recipient boxes, auto-completion, etc. Use AJAX for this.
to other users, if they share it to others. it should do something like username/room
where username should be a floor.
-* webcit should be made more resistant to html injections, especialy the chat window.
\ No newline at end of file
+* webcit should be made more resistant to html injections, especialy the chat window.