# the base URL of the SyncML server:
# - Sync4j 2.3
#syncURL = http://localhost:8080/sync4j/sync
# - Funambol >= 3.0
#syncURL = http://localhost:8080/funambol/ds
# - myFUNAMBOL
syncURL = http://my.funambol.com/sync
# - sync.scheduleworld.com
#syncURL = http://sync.scheduleworld.com/funambol/ds

# the SyncML server gets this string and will use it to keep track of
# changes that still need to be synchronized with this particular
# client; it must be set to something unique if SyncEvolution is used
# to synchronize data between different computers
deviceId = sc-api-nat

# authorization for the SyncML server
username = your SyncML server account name
password = your SyncML server password

# set to T to enable an HTTP proxy
useProxy = F
# proxy URL (http://<host>:<port>)
proxyHost = 
# user agent string used for HTTP
userAgent = SyncEvolution

# full path to directory where automatic backups and logs
# are stored for all synchronizations; if empty, the temporary
# directory "$TMPDIR/SyncEvolution-<username>-<server>" will
# be used to keep the data of just the latest synchronization run;
# if "none", then no backups of the databases are made and any
# output is printed directly instead of writing it into a log
#
# When writing into a log nothing will be shown during the
# synchronization. Instead the important messages are extracted
# automatically from the log at the end.
logdir =

# level of detail for log messages:
# - 0 (or unset) = INFO messages without log file, DEBUG with log file
# - 1 = only ERROR messages
# - 2 = also INFO messages
# - 3 = also DEBUG messages
loglevel = 0

# Unless this option is set, SyncEvolution will never delete
# anything in the "logdir". If set, the oldest directories and
# all their content will be removed after a successful sync
# to prevent the number of log directories from growing beyond
# the given limit.
maxlogdirs =

# Support for large objects and limiting the message size was added in
# SyncEvolution 0.5, but still disabled in the example configurations
# of that version. Some servers had problems with that configuration,
# so now both features are enabled by default and it is recommended
# to update existing configurations.
#
# The maximum size of each message can be set (maxMsgSize) and the
# server can be told to never sent items larger than a certain
# threshold (maxObjSize). Presumably the server has to truncate or
# skip larger items. Finally the client and server may be given the
# permission to transmit large items in multiple messages (loSupport =
# large object support).
maxMsgSize = 8192
maxObjSize = 500000
loSupport = 1

# used by the SyncML library internally; do not modify
begin =
end =
firstTimeSyncMode = 0
