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