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_offers
63 ---------------
64
65 Default: (none)
66 Alternative: (see below)
67
68 Define the period for which free/busy offers are extended by participants
69 supporting this setting when counter-proposals are made during event
70 scheduling.
71
72 This setting requires a value of one of the following forms:
73
74 <number of seconds>
75 <number of days>d
76
77 For example:
78
79 600 extend scheduling offers for 10 minutes
80 1d extend offers for 1 day
81
82 freebusy_sharing
83 ----------------
84
85 Default: no
86 Alternative: share
87
88 Share free/busy details generally:
89
90 * bundling in e-mail messages if bundling is configured
91 * responding to free/busy requests via e-mail
92 * publishing as Web resources if a static Web resource is configured
93
94 incoming
95 --------
96
97 Default: summary-wraps-message
98 Alternatives: (see below)
99
100 Define how incoming event messages are delivered to recipients:
101
102 message-only deliver only the incoming message as it was received
103
104 message-then-summary deliver the message first followed by a summary
105 message
106
107 summary-then-message deliver a summary first followed by the message
108
109 summary-only deliver only a summary of the message
110
111 summary-wraps-message deliver a summary that includes the original message
112 as an attachment
113
114 organiser_replacement
115 ---------------------
116
117 Default: attendee
118 Alternatives: (see below)
119
120 Indicate whether the organiser of an event can be replaced and the nature of
121 any replacement:
122
123 any any identity, regardless of whether it is already
124 present or even previously unknown, may become the
125 organiser
126
127 attendee any new organiser must be a previously-recognised
128 attendee
129
130 never forbid the replacement of an event's organiser
131
132 participating
133 -------------
134
135 Default: participate
136 Alternative: no
137
138 Indicate whether a recipient participates in the calendar system. Note that
139 participation by default occurs because the handler programs will be defined
140 in the mail system for recipients fulfilling certain criteria; other
141 recipients will be handled in other ways. Thus, initial non-participation must
142 be defined by initialising this setting to "no" for all eligible users, if
143 this is the general policy on initial calendar system participation.
144
145 permitted_times
146 ---------------
147
148 Default: (none)
149 Alternatives: (see below)
150
151 Define the time values at which events can be scheduled. In its simplest form,
152 this indicates the resolution of a calendar for a participant supporting this
153 setting, with the given minute values being those allowed for the start and
154 end of an event. This setting requires a value of one of the following forms:
155
156 <minute values>
157 <hour values>:<minute values>
158 <hour values>:<minute values>:<second values>
159
160 Each list of values is a comma-separated collection of permissible values for
161 the unit of time being constrained. Any unspecified list is taken to permit
162 all normally permissible values for that unit of time. For example:
163
164 0,15,30,45 every 15 minutes from the start of each hour
165 10,12,14,16:0,20,40 every 20 minutes from 10:00 until 16:40 inclusive
166 12::0,30 every 30 seconds from the start of each minute during
167 the period from 12:00:00 until 12:59:30 inclusive
168
169 The purpose of this setting is not necessarily to impose availability
170 constraints but instead to impose a "grid" to which event start and end points
171 shall be "locked".
172
173 The values are interpreted in the local time of the participant. Thus, a time
174 represented in UTC may have apparently inappropriate hour (and for some zones)
175 minute values that correspond to permitted values in this participant's own
176 time zone.