anything you like as long as it is a valid directory
name.
<P>Please note: When Sylpheed is executed for the first time, it automatically creates the configuration files under $HOME/.sylpheed/, and asks you the location of mailbox. The default is $HOME/Mail. If some files which are non-MH format already exist on the directory, you will have to specify another location.
-<H2><A NAME="ss2.3">2.3 Q03 How do I set up an account?</A>
+<H2><A NAME="ss2.3">2.3 Q03 Why did the creation of the mailbox fail?</A>
+</H2>
+
+<P>A. Sylpheed reports such an error if it can't create the default
+mailboxes (inbox, outbox, etc ...). This can be because <homedir>/Mail
+already contains files with the same names. This occurs when switching from
+Kmail to Sylpheed, in this case backup and remove the existing Mail
+directory or use another name for the Sylpheed mail directory.
+<H2><A NAME="ss2.4">2.4 Q04 How do I set up an account?</A>
</H2>
<P>A. After loading Sylpheed for the first time, you can
add an e-mail account by clicking the
"Configuration" menu. Select the option "Create new
account" and fill in the appropriate fields.
-<H2><A NAME="ss2.4">2.4 Q04 How many accounts can I set up in Sylpheed?</A>
+<H2><A NAME="ss2.5">2.5 Q05 How many accounts can I set up in Sylpheed?</A>
</H2>
<P>A. The number is unlimited. The limit is reached when
your computer stops responding.
-<H2><A NAME="ss2.5">2.5 Q05 Why does Sylpheed not delete my mails when I press "delete"? I set a filter, and Sylpheed does not filter. I moved a mail to a different mailbox and it did not move.</A>
+<H2><A NAME="ss2.6">2.6 Q06 Why does Sylpheed not delete my mails when I press "delete"? I set a filter, and Sylpheed does not filter. I moved a mail to a different mailbox and it did not move.</A>
</H2>
<P>A. You have to click the "execute" button.
The other solution: in the configuration settings
-(common preferences > interface tab) you have to
+(common preferences -> interface tab) you have to
check the "execute commands immediately" box.
-<H2><A NAME="ss2.6">2.6 Q06 Can I set up special addresses/ports for my mailserver / newsserver?</A>
+<H2><A NAME="ss2.7">2.7 Q07 Can I set up special addresses/ports for my mailserver / newsserver?</A>
</H2>
<P>A. Yes, you can. In the configuration per account you
can specify the exact port addresses you want to use.
-<H2><A NAME="ss2.7">2.7 Q07 Does Sylpheed have options for threading messages?</A>
+<H2><A NAME="ss2.8">2.8 Q08 Does Sylpheed have options for threading messages?</A>
</H2>
<P>A. Yes. You can switch it on and off in the Summary
Menu, just select "Thread View" or press Ctrl+T.
-<H2><A NAME="ss2.8">2.8 Q08 Can I create multiple levels of subfolders to store mail?</A>
+<H2><A NAME="ss2.9">2.9 Q09 Can I create multiple levels of subfolders to store mail?</A>
</H2>
<P>A. Absolutely. This is no problem.
-<H2><A NAME="ss2.9">2.9 Q09 Why isn't Sylpheed sending my mail out?</A>
+<H2><A NAME="ss2.10">2.10 Q10 Why isn't Sylpheed sending my mail out?</A>
</H2>
<P>A. You need to create at least one account in order to
send. (This is a wonderful gotcha on LAN installs
with only a local mailbox feed).
-<H2><A NAME="ss2.10">2.10 Q10 How do I apply a patch after downloading it?</A>
+<H2><A NAME="ss2.11">2.11 Q11 How do I apply a patch after downloading it?</A>
</H2>
<P>A. Copy patch to sylpheed directory
Run <CODE>./configure</CODE> with the appropriate options and
then <CODE>make</CODE>.
(Text as found on the Sylpheed patches page.)
-<H2><A NAME="ss2.11">2.11 Q11 How do I compile in support for compface pictures?</A>
+<H2><A NAME="ss2.12">2.12 Q12 How do I compile in support for compface pictures?</A>
</H2>
<P>A. You have to have a package called <CODE>libcompface</CODE>
installed, so this is available for compiling into
Sylpheed.
-<H2><A NAME="ss2.12">2.12 Q12 How do I make my own compface image?</A>
+<H2><A NAME="ss2.13">2.13 Q13 How do I make my own compface image?</A>
</H2>
<P>A. The faces package contains a program called xbm2ikon script,
which converts a 48x48 xbm to the format suitable for
compface. Thanks to Jeff Dairiki, you can have a complete online course in this. Visit
<A HREF="http://www.dairiki.org/xface/">this page</A> for the details.
-<H2><A NAME="ss2.13">2.13 Q13 How can I tell my browser/newsclient/other program to use Sylpheed as e-mail program?</A>
+<H2><A NAME="ss2.14">2.14 Q14 How can I tell my browser/newsclient/other program to use Sylpheed as e-mail program?</A>
</H2>
<P>A. In the settings part of the program, write
<CODE>sylpheed --compose</CODE>
-<H2><A NAME="ss2.14">2.14 Q14 How do I enable GPG support in Sylpheed?</A>
+<H2><A NAME="ss2.15">2.15 Q15 How do I enable GPG support in Sylpheed?</A>
</H2>
<P>A. When compiling Sylpheed, make sure you add <CODE>--enable-gpgme</CODE> in the ./configure command.
When that completes successfully, there is a "privacy" section in the Common preferences.
-<H2><A NAME="ss2.15">2.15 Q15 Mutt does not recognize Sylpheed's MH structure</A>
+<H2><A NAME="ss2.16">2.16 Q16 Mutt does not recognize Sylpheed's MH structure</A>
</H2>
<P>A. For this to work you need to use the "touch" command in every MH folder. "touch" the file .xmhcache and Mutt should do just fine.
-<H2><A NAME="ss2.16">2.16 Q16 Viewing a GIF file within Sylpheed causes a segmentation fault.</A>
+<H2><A NAME="ss2.17">2.17 Q17 Viewing a GIF file within Sylpheed causes a segmentation fault.</A>
</H2>
<P>A. In case this happens, you can easily fix that by adding the following to /etc/mime.types:
<P><CODE>image/gif gif</CODE>
-<H2><A NAME="ss2.17">2.17 Q17 How can I make Sylpheed notify me when new mail arrives?</A>
+<H2><A NAME="ss2.18">2.18 Q18 How can I make Sylpheed notify me when new mail arrives?</A>
</H2>
<P>A. For this you can do several things:
<P>* Look at the Sylpheed patch page at
-<A HREF="http://www.teledix.net/sylpheed/">Teledix.net</A> for a new mail patch.
+<A HREF="http://www.thewildbeast.co.uk/sylpheed/">http://www.thewildbeast.co.uk/sylpheed/</A> for a new mail patch.
<P>* Download Gkrellm or a similar program that is able to notify you of new incoming mail. Gkrellm is available at
-<A HREF="http://www.gkrellm.net">the Gkrellm page</A><P>
+<A HREF="http://www.gkrellm.net">the Gkrellm page</A><H2><A NAME="ss2.19">2.19 Q19 Can I use a spell checker with Sylpheed?</A>
+</H2>
+
+<P>A. Yes. You can use ispell for this. In Common Preferences, in the spot where you can define an alternative editor (as long as you do not use that, of course), you enter "xterm -e ispell %s". Do not enter the quotes.
+With this set up, you can have spell checked when writing an e-mail by hitting the "Editor" button in the compose window.
+<P>Note that you can enter the xterm type of your choice, so wterm, eterm and aterm should also work, as long as they are installed on your system.
+<H2><A NAME="ss2.20">2.20 Q20 How can I make Sylpheed send my compface image in the mails?</A>
+</H2>
+
+<P>A. In the Configuration menu, Preferences for current account, Send tab, check Add user-defined header and press Edit button. A dialog appears, add a header named "X-Face" and fill the value field with your face data. Note that if you paste the data from a terminal into the field some spurious newlines can be added, and these can mangle your face, be careful.
<HR>
<A HREF="sylpheed-faq-3.html">Next</A>
<A HREF="sylpheed-faq-1.html">Previous</A>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>Sylpheed FAQ: GNU Free Documentation License</TITLE>
+ <LINK HREF="sylpheed-faq-3.html" REL=previous>
+ <LINK HREF="sylpheed-faq.html#toc4" REL=contents>
+</HEAD>
+<BODY>
+Next
+<A HREF="sylpheed-faq-3.html">Previous</A>
+<A HREF="sylpheed-faq.html#toc4">Contents</A>
+<HR>
+<H2><A NAME="s4">4. GNU Free Documentation License</A> </H2>
+
+<P>Version 1.1, March 2000
+<P>Copyright (C) 2000 Free Software Foundation, Inc.
+59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+<H2><A NAME="ss4.1">4.1 PREAMBLE</A>
+ </H2>
+
+<P>The purpose of this License is to make a manual, textbook,
+or other written document "free" in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or
+noncommercially. Secondarily, this License preserves for the
+author and publisher a way to get credit for their work, while not
+being considered responsible for modifications made by
+others.
+<P>This License is a kind of "copyleft", which means that
+derivative works of the document must themselves be free in the
+same sense. It complements the GNU General Public License, which
+is a copyleft license designed for free software.
+<P>We have designed this License in order to use it for manuals
+for free software, because free software needs free documentation:
+a free program should come with manuals providing the same
+freedoms that the software does. But this License is not limited
+to software manuals; it can be used for any textual work,
+regardless of subject matter or whether it is published as a
+printed book. We recommend this License principally for works
+whose purpose is instruction or reference.
+<H2><A NAME="ss4.2">4.2 APPLICABILITY AND DEFINITIONS</A>
+ </H2>
+
+<P>This License applies to any manual or other work that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License. The "Document",
+below, refers to any such manual or work. Any member of the
+public is a licensee, and is addressed as "you".
+<P>A "Modified Version" of the Document means any work
+containing the Document or a portion of it, either copied
+verbatim, or with modifications and/or translated into another
+language.
+<P>A "Secondary Section" is a named appendix or a front-matter
+section of the Document that deals exclusively with the
+relationship of the publishers or authors of the Document to the
+Document's overall subject (or to related matters) and contains
+nothing that could fall directly within that overall subject.
+(For example, if the Document is in part a textbook of
+mathematics, a Secondary Section may not explain any mathematics.)
+The relationship could be a matter of historical connection with
+the subject or with related matters, or of legal, commercial,
+philosophical, ethical or political position regarding
+them.
+<P>The "Invariant Sections" are certain Secondary Sections
+whose titles are designated, as being those of Invariant Sections,
+in the notice that says that the Document is released under this
+License.
+<P>The "Cover Texts" are certain short passages of text that
+are listed, as Front-Cover Texts or Back-Cover Texts, in the
+notice that says that the Document is released under this
+License.
+<P>A "Transparent" copy of the Document means a
+machine-readable copy, represented in a format whose specification
+is available to the general public, whose contents can be viewed
+and edited directly and straightforwardly with generic text
+editors or (for images composed of pixels) generic paint programs
+or (for drawings) some widely available drawing editor, and that
+is suitable for input to text formatters or for automatic
+translation to a variety of formats suitable for input to text
+formatters. A copy made in an otherwise Transparent file format
+whose markup has been designed to thwart or discourage subsequent
+modification by readers is not Transparent. A copy that is not
+"Transparent" is called "Opaque".
+<P>Examples of suitable formats for Transparent copies include
+plain ASCII without markup, Texinfo input format, LaTeX input
+format, SGML or XML using a publicly available DTD, and
+standard-conforming simple HTML designed for human modification.
+Opaque formats include PostScript, PDF, proprietary formats that
+can be read and edited only by proprietary word processors, SGML
+or XML for which the DTD and/or processing tools are not generally
+available, and the machine-generated HTML produced by some word
+processors for output purposes only.
+<P>The "Title Page" means, for a printed book, the title page
+itself, plus such following pages as are needed to hold, legibly,
+the material this License requires to appear in the title page.
+For works in formats which do not have any title page as such,
+"Title Page" means the text near the most prominent appearance of
+the work's title, preceding the beginning of the body of the
+text.
+<H2><A NAME="ss4.3">4.3 VERBATIM COPYING</A>
+ </H2>
+
+<P>You may copy and distribute the Document in any medium,
+either commercially or noncommercially, provided that this
+License, the copyright notices, and the license notice saying this
+License applies to the Document are reproduced in all copies, and
+that you add no other conditions whatsoever to those of this
+License. You may not use technical measures to obstruct or
+control the reading or further copying of the copies you make or
+distribute. However, you may accept compensation in exchange for
+copies. If you distribute a large enough number of copies you
+must also follow the conditions in section 3.
+<P>You may also lend copies, under the same conditions stated
+above, and you may publicly display copies.
+<H2><A NAME="ss4.4">4.4 COPYING IN QUANTITY</A>
+ </H2>
+
+<P>If you publish printed copies of the Document numbering more
+than 100, and the Document's license notice requires Cover Texts,
+you must enclose the copies in covers that carry, clearly and
+legibly, all these Cover Texts: Front-Cover Texts on the front
+cover, and Back-Cover Texts on the back cover. Both covers must
+also clearly and legibly identify you as the publisher of these
+copies. The front cover must present the full title with all
+words of the title equally prominent and visible. You may add
+other material on the covers in addition. Copying with changes
+limited to the covers, as long as they preserve the title of the
+Document and satisfy these conditions, can be treated as verbatim
+copying in other respects.
+<P>If the required texts for either cover are too voluminous to
+fit legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto
+adjacent pages.
+<P>If you publish or distribute Opaque copies of the Document
+numbering more than 100, you must either include a
+machine-readable Transparent copy along with each Opaque copy, or
+state in or with each Opaque copy a publicly-accessible
+computer-network location containing a complete Transparent copy
+of the Document, free of added material, which the general
+network-using public has access to download anonymously at no
+charge using public-standard network protocols. If you use the
+latter option, you must take reasonably prudent steps, when you
+begin distribution of Opaque copies in quantity, to ensure that
+this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you
+distribute an Opaque copy (directly or through your agents or
+retailers) of that edition to the public.
+<P>It is requested, but not required, that you contact the
+authors of the Document well before redistributing any large
+number of copies, to give them a chance to provide you with an
+updated version of the Document.
+<H2><A NAME="ss4.5">4.5 MODIFICATIONS</A>
+ </H2>
+
+<P>You may copy and distribute a Modified Version of the
+Document under the conditions of sections 2 and 3 above, provided
+that you release the Modified Version under precisely this
+License, with the Modified Version filling the role of the
+Document, thus licensing distribution and modification of the
+Modified Version to whoever possesses a copy of it. In addition,
+you must do these things in the Modified Version:
+<P>
+<UL>
+<LI>Use in the Title Page
+(and on the covers, if any) a title distinct from that of the
+Document, and from those of previous versions (which should, if
+there were any, be listed in the History section of the
+Document). You may use the same title as a previous version if
+the original publisher of that version gives permission.</LI>
+<LI>List on the Title Page,
+as authors, one or more persons or entities responsible for
+authorship of the modifications in the Modified Version,
+together with at least five of the principal authors of the
+Document (all of its principal authors, if it has less than
+five).</LI>
+<LI>State on the Title page
+the name of the publisher of the Modified Version, as the
+publisher.</LI>
+<LI>Preserve all the
+copyright notices of the Document.</LI>
+<LI>Add an appropriate
+copyright notice for your modifications adjacent to the other
+copyright notices.</LI>
+<LI>Include, immediately
+after the copyright notices, a license notice giving the public
+permission to use the Modified Version under the terms of this
+License, in the form shown in the Addendum below.</LI>
+<LI>Preserve in that license
+notice the full lists of Invariant Sections and required Cover
+Texts given in the Document's license notice.</LI>
+<LI>Include an unaltered
+copy of this License.</LI>
+<LI>Preserve the section
+entitled "History", and its title, and add to it an item stating
+at least the title, year, new authors, and publisher of the
+Modified Version as given on the Title Page. If there is no
+section entitled "History" in the Document, create one stating
+the title, year, authors, and publisher of the Document as given
+on its Title Page, then add an item describing the Modified
+Version as stated in the previous sentence.</LI>
+<LI>Preserve the network
+location, if any, given in the Document for public access to a
+Transparent copy of the Document, and likewise the network
+locations given in the Document for previous versions it was
+based on. These may be placed in the "History" section. You
+may omit a network location for a work that was published at
+least four years before the Document itself, or if the original
+publisher of the version it refers to gives permission.</LI>
+<LI>In any section entitled
+"Acknowledgements" or "Dedications", preserve the section's
+title, and preserve in the section all the substance and tone of
+each of the contributor acknowledgements and/or dedications
+given therein.</LI>
+<LI>Preserve all the
+Invariant Sections of the Document, unaltered in their text and
+in their titles. Section numbers or the equivalent are not
+considered part of the section titles.</LI>
+<LI>Delete any section
+entitled "Endorsements". Such a section may not be included in
+the Modified Version.</LI>
+<LI>Do not retitle any
+existing section as "Endorsements" or to conflict in title with
+any Invariant Section.</LI>
+</UL>
+<P>
+<P>If the Modified Version includes new front-matter sections
+or appendices that qualify as Secondary Sections and contain no
+material copied from the Document, you may at your option
+designate some or all of these sections as invariant. To do this,
+add their titles to the list of Invariant Sections in the Modified
+Version's license notice. These titles must be distinct from any
+other section titles.
+<P>You may add a section entitled "Endorsements", provided it
+contains nothing but endorsements of your Modified Version by
+various parties--for example, statements of peer review or that
+the text has been approved by an organization as the authoritative
+definition of a standard.
+<P>You may add a passage of up to five words as a Front-Cover
+Text, and a passage of up to 25 words as a Back-Cover Text, to the
+end of the list of Cover Texts in the Modified Version. Only one
+passage of Front-Cover Text and one of Back-Cover Text may be
+added by (or through arrangements made by) any one entity. If the
+Document already includes a cover text for the same cover,
+previously added by you or by arrangement made by the same entity
+you are acting on behalf of, you may not add another; but you may
+replace the old one, on explicit permission from the previous
+publisher that added the old one.
+<P>The author(s) and publisher(s) of the Document do not by
+this License give permission to use their names for publicity for
+or to assert or imply endorsement of any Modified Version.
+<H2><A NAME="ss4.6">4.6 COMBINING DOCUMENTS</A>
+ </H2>
+
+<P>You may combine the Document with other documents released
+under this License, under the terms defined in section 4 above for
+modified versions, provided that you include in the combination
+all of the Invariant Sections of all of the original documents,
+unmodified, and list them all as Invariant Sections of your
+combined work in its license notice.
+<P>The combined work need only contain one copy of this
+License, and multiple identical Invariant Sections may be replaced
+with a single copy. If there are multiple Invariant Sections with
+the same name but different contents, make the title of each such
+section unique by adding at the end of it, in parentheses, the
+name of the original author or publisher of that section if known,
+or else a unique number. Make the same adjustment to the section
+titles in the list of Invariant Sections in the license notice of
+the combined work.
+<P>In the combination, you must combine any sections entitled
+"History" in the various original documents, forming one section
+entitled "History"; likewise combine any sections entitled
+"Acknowledgements", and any sections entitled "Dedications". You
+must delete all sections entitled "Endorsements."
+<H2><A NAME="ss4.7">4.7 COLLECTIONS OF DOCUMENTS</A>
+ </H2>
+
+<P>You may make a collection consisting of the Document and
+other documents released under this License, and replace the
+individual copies of this License in the various documents with a
+single copy that is included in the collection, provided that you
+follow the rules of this License for verbatim copying of each of
+the documents in all other respects.
+<P>You may extract a single document from such a collection,
+and distribute it individually under this License, provided you
+insert a copy of this License into the extracted document, and
+follow this License in all other respects regarding verbatim
+copying of that document.
+<H2><A NAME="ss4.8">4.8 AGGREGATION WITH INDEPENDENT WORKS</A>
+ </H2>
+
+<P>A compilation of the Document or its derivatives with other
+separate and independent documents or works, in or on a volume of
+a storage or distribution medium, does not as a whole count as a
+Modified Version of the Document, provided no compilation
+copyright is claimed for the compilation. Such a compilation is
+called an "aggregate", and this License does not apply to the
+other self-contained works thus compiled with the Document, on
+account of their being thus compiled, if they are not themselves
+derivative works of the Document.
+<P>If the Cover Text requirement of section 3 is applicable to
+these copies of the Document, then if the Document is less than
+one quarter of the entire aggregate, the Document's Cover Texts
+may be placed on covers that surround only the Document within the
+aggregate. Otherwise they must appear on covers around the whole
+aggregate.
+<H2><A NAME="ss4.9">4.9 TRANSLATION</A>
+ </H2>
+
+<P>Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section
+4. Replacing Invariant Sections with translations requires
+special permission from their copyright holders, but you may
+include translations of some or all Invariant Sections in addition
+to the original versions of these Invariant Sections. You may
+include a translation of this License provided that you also
+include the original English version of this License. In case of
+a disagreement between the translation and the original English
+version of this License, the original English version will
+prevail.
+<H2><A NAME="ss4.10">4.10 TERMINATION</A>
+ </H2>
+
+<P>You may not copy, modify, sublicense, or distribute the
+Document except as expressly provided for under this License. Any
+other attempt to copy, modify, sublicense or distribute the
+Document is void, and will automatically terminate your rights
+under this License. However, parties who have received copies, or
+rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full
+compliance.
+<H2><A NAME="ss4.11">4.11 FUTURE REVISIONS OF THIS LICENSE</A>
+ </H2>
+
+<P>The Free Software Foundation may publish new, revised
+versions of the GNU Free Documentation License from time to time.
+Such new versions will be similar in spirit to the present
+version, but may differ in detail to address new problems or
+concerns. See
+<A HREF="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</A>.
+<P>Each version of the License is given a distinguishing
+version number. If the Document specifies that a particular
+numbered version of this License "or any later version" applies to
+it, you have the option of following the terms and conditions
+either of that specified version or of any later version that has
+been published (not as a draft) by the Free Software Foundation.
+If the Document does not specify a version number of this License,
+you may choose any version ever published (not as a draft) by the
+Free Software Foundation.
+<H2><A NAME="ss4.12">4.12 How to use this License for your documents</A>
+ </H2>
+
+<P>To use this License in a document you have written, include
+a copy of the License in the document and put the following
+copyright and license notices just after the title page:
+<P><CODE>Copyright (c) YEAR YOUR NAME.
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.1
+or any later version published by the Free Software Foundation;
+with the Invariant Sections being LIST THEIR TITLES, with the
+Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
+A copy of the license is included in the section entitled "GNU
+Free Documentation License".</CODE>
+<P>If you have no Invariant Sections, write "with no Invariant
+Sections" instead of saying which ones are invariant. If you have
+no Front-Cover Texts, write "no Front-Cover Texts" instead of
+"Front-Cover Texts being LIST"; likewise for Back-Cover
+Texts.
+<P>If your document contains nontrivial examples of program
+code, we recommend releasing these examples in parallel under your
+choice of free software license, such as the GNU General Public
+License, to permit their use in free software.
+<HR>
+Next
+<A HREF="sylpheed-faq-3.html">Previous</A>
+<A HREF="sylpheed-faq.html#toc4">Contents</A>
+</BODY>
+</HTML>
<H2>Paul Kater (paul@nlpagan.net)
and Jens Oberender (j.obi@troja.net)
+ Maintained by François Barrière (barriere.francois@libertysurf.fr)
</H2>
<P><HR>
-<EM> Sylpheed FAQ (for version 0.7.3)
+<EM> Sylpheed FAQ (for version 0.8.0)
</EM>
<HR>
+<P>Copyright (c) 2002 François Barrière.
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.1
+or any later version published by the Free Software Foundation;
+with no Invariant Sections, with no Front-Cover Texts, and no Back-Cover Texts.
+A copy of the license is included in the section entitled "GNU
+Free Documentation License".
<P>This FAQ consists of the following sections:
<P>
<H2><A NAME="toc1">1.</A> <A HREF="sylpheed-faq-1.html">Sylpheed FAQ - General information</A></H2>
<UL>
<LI><A HREF="sylpheed-faq-2.html#ss2.1">2.1 Q01 What does it take to compile Sylpheed?</A>
<LI><A HREF="sylpheed-faq-2.html#ss2.2">2.2 Q02 How do I set up Sylpheed?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.3">2.3 Q03 How do I set up an account?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.4">2.4 Q04 How many accounts can I set up in Sylpheed?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.5">2.5 Q05 Why does Sylpheed not delete my mails when I press "delete"? I set a filter, and Sylpheed does not filter. I moved a mail to a different mailbox and it did not move.</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.6">2.6 Q06 Can I set up special addresses/ports for my mailserver / newsserver?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.7">2.7 Q07 Does Sylpheed have options for threading messages?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.8">2.8 Q08 Can I create multiple levels of subfolders to store mail?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.9">2.9 Q09 Why isn't Sylpheed sending my mail out?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.10">2.10 Q10 How do I apply a patch after downloading it?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.11">2.11 Q11 How do I compile in support for compface pictures?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.12">2.12 Q12 How do I make my own compface image?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.13">2.13 Q13 How can I tell my browser/newsclient/other program to use Sylpheed as e-mail program?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.14">2.14 Q14 How do I enable GPG support in Sylpheed?</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.15">2.15 Q15 Mutt does not recognize Sylpheed's MH structure</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.16">2.16 Q16 Viewing a GIF file within Sylpheed causes a segmentation fault.</A>
-<LI><A HREF="sylpheed-faq-2.html#ss2.17">2.17 Q17 How can I make Sylpheed notify me when new mail arrives?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.3">2.3 Q03 Why did the creation of the mailbox fail?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.4">2.4 Q04 How do I set up an account?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.5">2.5 Q05 How many accounts can I set up in Sylpheed?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.6">2.6 Q06 Why does Sylpheed not delete my mails when I press "delete"? I set a filter, and Sylpheed does not filter. I moved a mail to a different mailbox and it did not move.</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.7">2.7 Q07 Can I set up special addresses/ports for my mailserver / newsserver?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.8">2.8 Q08 Does Sylpheed have options for threading messages?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.9">2.9 Q09 Can I create multiple levels of subfolders to store mail?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.10">2.10 Q10 Why isn't Sylpheed sending my mail out?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.11">2.11 Q11 How do I apply a patch after downloading it?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.12">2.12 Q12 How do I compile in support for compface pictures?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.13">2.13 Q13 How do I make my own compface image?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.14">2.14 Q14 How can I tell my browser/newsclient/other program to use Sylpheed as e-mail program?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.15">2.15 Q15 How do I enable GPG support in Sylpheed?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.16">2.16 Q16 Mutt does not recognize Sylpheed's MH structure</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.17">2.17 Q17 Viewing a GIF file within Sylpheed causes a segmentation fault.</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.18">2.18 Q18 How can I make Sylpheed notify me when new mail arrives?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.19">2.19 Q19 Can I use a spell checker with Sylpheed?</A>
+<LI><A HREF="sylpheed-faq-2.html#ss2.20">2.20 Q20 How can I make Sylpheed send my compface image in the mails?</A>
</UL>
<P>
<H2><A NAME="toc3">3.</A> <A HREF="sylpheed-faq-3.html">Sylpheed FAQ - Interface</A></H2>
<LI><A HREF="sylpheed-faq-3.html#ss3.12">3.12 Q12 Why does the URL Launcher not launch my webbrowser?</A>
<LI><A HREF="sylpheed-faq-3.html#ss3.13">3.13 Q13 Attachments with spaces in the name won't open!</A>
</UL>
+<H2>Appendix</H2>
+<P>
+<H2><A NAME="toc4">4.</A> <A HREF="sylpheed-faq-4.html">GNU Free Documentation License</A></H2>
+
+<UL>
+<LI><A HREF="sylpheed-faq-4.html#ss4.1">4.1 PREAMBLE</A>
+<LI><A HREF="sylpheed-faq-4.html#ss4.2">4.2 APPLICABILITY AND DEFINITIONS</A>
+<LI><A HREF="sylpheed-faq-4.html#ss4.3">4.3 VERBATIM COPYING</A>
+<LI><A HREF="sylpheed-faq-4.html#ss4.4">4.4 COPYING IN QUANTITY</A>
+<LI><A HREF="sylpheed-faq-4.html#ss4.5">4.5 MODIFICATIONS</A>
+<LI><A HREF="sylpheed-faq-4.html#ss4.6">4.6 COMBINING DOCUMENTS</A>
+<LI><A HREF="sylpheed-faq-4.html#ss4.7">4.7 COLLECTIONS OF DOCUMENTS</A>
+<LI><A HREF="sylpheed-faq-4.html#ss4.8">4.8 AGGREGATION WITH INDEPENDENT WORKS</A>
+<LI><A HREF="sylpheed-faq-4.html#ss4.9">4.9 TRANSLATION</A>
+<LI><A HREF="sylpheed-faq-4.html#ss4.10">4.10 TERMINATION</A>
+<LI><A HREF="sylpheed-faq-4.html#ss4.11">4.11 FUTURE REVISIONS OF THIS LICENSE</A>
+<LI><A HREF="sylpheed-faq-4.html#ss4.12">4.12 How to use this License for your documents</A>
+</UL>
<HR>
<A HREF="sylpheed-faq-1.html">Next</A>
Previous