+ <itemizedlist>
+ <listitem>
+ <para>
+ Start with a user who does not have a <filename class="directory"
+ >~/.sylpheed-claws</filename> directory, ideally a new user.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Start Sylpheed-Claws and go through the wizard. The values you fill in
+ will be of no use for the future deployment, so you can click
+ next-next-next.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Once the wizard is finished and you have Sylpheed-Claws' main window
+ opened, configure the various defaults you want to have in the master.
+ You can load plugins, add people or LDAP servers in the addressbook,
+ create filtering rules, and so on.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If needed, and if the deployed Sylpheed-Claws will use MH folders, you
+ can create subdirectories in the mailbox.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Next, quit Sylpheed-Claws.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Now, edit the newly created wizard template file,
+ <filename>~/.sylpheed-claws/accountrc.tmpl</filename>. In this file,
+ you will see different variables, corresponding to the wizard's fields.
+ You can leave some commented, in which case the usual default will be
+ used, or specify values or variables. Not all fields can contain
+ variables; for example, <literal>smtpauth</literal>,
+ <literal>smtpssl</literal> and <literal>recvssl</literal> are booleans,
+ either 0 or 1, and <literal>recvtype</literal> is an integer value. The
+ other fields, like <literal>name</literal>, <literal>email</literal>,
+ or <literal>recvuser</literal>, are parsed by the wizard and the
+ variables they contain are replaced by values. This allows you to
+ specify everything as needed for your site, even if you have strange
+ server names or server logins.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Save this file, and delete both
+ <filename>~/.sylpheed-claws/accountrc</filename>, (which contains your
+ dummy account) and
+ <filename>~/.sylpheed-claws/folderlist.xml</filename>, (so that the
+ folder tree will be correctly parsed for new users). Recursively copy
+ <filename class="directory">.sylpheed-claws</filename> to
+ <filename class="directory">/etc/skel/</filename>; if the deployed
+ Sylpheed-Claws will use MH folders, also copy the created
+ <filename class="directory">Mail</filename> directory. chown all of
+ <filename class="directory">/etc/skel/.sylpheed-claws</filename>
+ and <filename class="directory">/etc/skel/Mail</filename> to
+ <literal>root:root</literal> for security reasons.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Test! Create a new user, login as that user, run Sylpheed-Claws. If you
+ filled everything as you wanted, this user will just have to fill in
+ his passwords.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Now, if you're creating a master for a site-wide deployment, you can
+ continue with this process. If you were just doing it for one machine,
+ you're done!
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Here are the different variables of the <filename>accountrc.tmpl</filename>
+ file:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><literal>domain</literal></term>
+ <listitem>
+ <para>
+ Your domain name (example.com). If not set, it'll be extracted from the
+ hostname.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>name</literal></term>
+ <listitem>
+ <para>
+ The user's name. If not set, it'll be extracted from Unix login
+ information, which is usually ok.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>email</literal></term>
+ <listitem>
+ <para>
+ The user's email. If not set, it'll be extracted from
+ <literal>$name</literal> and <literal>$domain</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>organization</literal></term>
+ <listitem>
+ <para>
+ Your organization. If not set, it'll be empty.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>smtpserver</literal></term>
+ <listitem>
+ <para>
+ The SMTP server to use. If not set, it'll be
+ <literal>smtp.$domain</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>smtpauth</literal></term>
+ <listitem>
+ <para>
+ 0 or 1. Whether to authenticate on the SMTP server. If not set, it'll
+ be 0.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>smtpuser</literal></term>
+ <listitem>
+ <para>
+ The login on the SMTP server. If not set, it'll be empty (same login as
+ for reception will be used).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>smtppass</literal></term>
+ <listitem>
+ <para>
+ The password on the SMTP server. If not set, it'll be empty (if
+ <literal>smtppass</literal> is empty but <literal>smtpuser</literal> is
+ not, the user will be asked for the password).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>recvtype</literal></term>
+ <listitem>
+ <para>
+ The type of server to receive from. 0 for POP3, 3 for IMAP4, 5 for a
+ local MBOX file. If not set, it'll be 0 (POP3).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>recvserver</literal></term>
+ <listitem>
+ <para>
+ The reception server. If not set, it'll be
+ <literal>(pop|imap).$domain</literal>, depending on
+ <literal>$recvtype</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>recvuser</literal></term>
+ <listitem>
+ <para>
+ The login on the reception server. If not set, it'll be extracted from
+ the Unix login information.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>recvpass</literal></term>
+ <listitem>
+ <para>
+ The password on the reception server. If not set, it'll be empty (the
+ user will be asked for it once per session).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>imapdir</literal></term>
+ <listitem>
+ <para>
+ The IMAP subdirectory. If not set, it'll be empty, which is often
+ sufficient.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>mboxfile</literal></term>
+ <listitem>
+ <para>
+ The MBOX file to receive from if <literal>$recvtype</literal> is 5.
+ If not set, <literal>/var/mail/$LOGIN</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>mailbox</literal></term>
+ <listitem>
+ <para>
+ The MH mailbox to store mail in (for <literal>$recvtype</literal> 0 or
+ 5). If not set, it'll be <quote>Mail</quote>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>respect_flowed_format</literal></term>
+ <listitem>
+ <para>
+ 0 or 1. Respect format=flowed on text/plain message parts. This
+ will cause some mails to have long lines, but will fix some URLs
+ that would otherwise be wrapped. Default is 0, turned off.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>smtpssl</literal></term>
+ <listitem>
+ <para>
+ 0 or 1. Whether to use SSL for sending mail. If not set, it'll be 0.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>recvssl</literal></term>
+ <listitem>
+ <para>
+ 0 or 1. Whether to use SSL for receiving mail. If not set, it'll be 0.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ Here are the different variables you can use in the
+ <literal>domain</literal>, <literal>name</literal>,
+ <literal>email</literal>, <literal>organization</literal>,
+ <literal>smtpserver</literal>, <literal>smtpuser</literal>,
+ <literal>smtppass</literal>, <literal>recvserver</literal>,
+ <literal>recvuser</literal>, <literal>recvpass</literal>,
+ <literal>imapdir</literal>, <literal>mboxfile</literal> and
+ <literal>mailbox</literal> fields:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><literal>$DEFAULTDOMAIN</literal></term>
+ <listitem>
+ <para>
+ The domain name as extracted from Unix hostname information.
+ Often wrong.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>$DOMAIN</literal></term>
+ <listitem>
+ <para>
+ The domain name as set in the domain variable, the first of the
+ template file.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>$USERNAME</literal></term>
+ <listitem>
+ <para>The user's real name.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>$LOGIN</literal></term>
+ <listitem>
+ <para>The user's Unix login.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>$NAME_MAIL</literal></term>
+ <listitem>
+ <para>
+ The user's real name as set in the name variable of the template field,
+ in lowercase and with spaces replaced by dots.
+ <quote>Colin Leroy</quote> becomes <quote>colin.leroy</quote>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>$EMAIL</literal></term>
+ <listitem>
+ <para>
+ The email address as set in the email variable of the template field.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>