1 Preferences and Settings
2 ========================
3
4 LANG
5 ----
6
7 Default: en (English)
8 Alternatives: (any recognised and supported locale)
9
10 The language for messages and user interface text.
11
12 TZID
13 ----
14
15 Default: system timezone (see /etc/timezone)
16 Alternatives: (any recognised Olson time zone identifier)
17
18 The default time zone/regime for calendars, new events and local times.
19
20 add_method_response
21 -------------------
22
23 Default: refresh
24 Alternatives (see below)
25
26 Indicate how ADD methods shall be responded to when received by a recipient:
27
28 add apply them to events as received
29
30 ignore ignore attempts to add event occurrences
31
32 refresh respond with a REFRESH message to obtain a proper
33 request will all event details
34
35 event_refreshing
36 ----------------
37
38 Default: never
39 Alternative: always
40
41 Indicate whether messages requesting a refresh of event details shall be
42 handled automatically. If not, such messages will be passed on to the
43 recipient for their mail program to handle.
44
45 freebusy_bundling
46 -----------------
47
48 Default: never
49 Alternative: always
50
51 Indicate whether to bundle free/busy details with other payloads such as
52 event and free/busy objects.
53
54 freebusy_messages
55 -----------------
56
57 Default: none
58 Alternative: notify
59
60 Indicate whether recipients are notified about received free/busy payloads.
61
62 freebusy_sharing
63 ----------------
64
65 Default: no
66 Alternative: share
67
68 Share free/busy details generally:
69
70 * bundling in e-mail messages if bundling is configured
71 * responding to free/busy requests via e-mail
72 * publishing as Web resources if a static Web resource is configured
73
74 incoming
75 --------
76
77 Default: summary-wraps-message
78 Alternatives: (see below)
79
80 Define how incoming event messages are delivered to recipients:
81
82 message-only deliver only the incoming message as it was received
83
84 message-then-summary deliver the message first followed by a summary
85 message
86
87 summary-then-message deliver a summary first followed by the message
88
89 summary-only deliver only a summary of the message
90
91 summary-wraps-message deliver a summary that includes the original message
92 as an attachment
93
94 organiser_replacement
95 ---------------------
96
97 Default: attendee
98 Alternatives: (see below)
99
100 Indicate whether the organiser of an event can be replaced and the nature of
101 any replacement:
102
103 any any identity, regardless of whether it is already
104 present or even previously unknown, may become the
105 organiser
106
107 attendee any new organiser must be a previously-recognised
108 attendee
109
110 never forbid the replacement of an event's organiser
111
112 participating
113 -------------
114
115 Default: participate
116 Alternative: no
117
118 Indicate whether a recipient participates in the calendar system. Note that
119 participation by default occurs because the handler programs will be defined
120 in the mail system for recipients fulfilling certain criteria; other
121 recipients will be handled in other ways. Thus, initial non-participation must
122 be defined by initialising this setting to "no" for all eligible users, if
123 this is the general policy on initial calendar system participation.
124
125 permitted_times
126 ---------------
127
128 Default: (none)
129 Alternatives: (see below)
130
131 Define the time values at which events can be scheduled. In its simplest form,
132 this indicates the resolution of a calendar for a participant supporting this
133 setting, with the given minute values being those allowed for the start and
134 end of an event. This setting requires a value of one of the following forms:
135
136 <minute values>
137 <hour values>:<minute values>
138 <hour values>:<minute values>:<second values>
139
140 Each list of values is a comma-separated collection of permissible values for
141 the unit of time being constrained. Any unspecified list is taken to permit
142 all normally permissible values for that unit of time. For example:
143
144 0,15,30,45 every 15 minutes from the start of each hour
145 10,12,14,16:0,20,40 every 20 minutes from 10:00 until 16:40 inclusive
146 12::0,30 every 30 seconds from the start of each minute during
147 the period from 12:00:00 until 12:59:30 inclusive
148
149 The purpose of this setting is not necessarily to impose availability
150 constraints but instead to impose a "grid" to which event start and end points
151 shall be "locked".
152
153 The values are interpreted in the local time of the participant. Thus, a time
154 represented in UTC may have apparently inappropriate hour (and for some zones)
155 minute values that correspond to permitted values in this participant's own
156 time zone.