1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>Sylpheed User's Manual: What is Sylpheed?</TITLE>
<LINK HREF="sylpheed-2.html" REL=next>
<LINK HREF="sylpheed.html#toc1" REL=contents>
</HEAD>
<BODY>
<A HREF="sylpheed-2.html">Next</A>
Previous
<A HREF="sylpheed.html#toc1">Contents</A>
<HR>
<H2><A NAME="s1">1. What is Sylpheed?</A></H2>
<P>
<P>
<P>
<P>
<H2><A NAME="ss1.1">1.1 Introduction to Sylpheed.</A>
</H2>
<P>Sylpheed is a fast e-mail and news client. It will run on just about any Linux or Unix compliant system.
<P>The power of Sylpheed is that it is
<UL>
<LI>light on resources</LI>
<LI>very fast</LI>
<LI>intuitive for most people</LI>
<LI>easy to work with</LI>
<LI>loaded with features</LI>
<LI>graceful and sophisticated in its interface</LI>
</UL>
<H2><A NAME="ss1.2">1.2 Interface</A>
</H2>
<P>The appearance and interface are similar to some popular e-mail clients for
Windows, such as Outlook Express, Becky!, and Datula. The interface is
also designed to emulate the mailers on Emacsen, and almost all commands
are accessible with the keyboard.
<P>The messages are managed by MH format, and you'll be able to use it
together with another mailer based on MH format (like Mew). You can
also utilize fetchmail or/and procmail, and external programs for
receiving (like inc or imget).
<H2><A NAME="ss1.3">1.3 Main features</A>
</H2>
<P>Currently implemented features are:
<UL>
<LI>Unlimited multiple account handling</LI>
<LI>Thread display</LI>
<LI>Filtering </LI>
<LI>MIME (attachments) </LI>
<LI>built-in image view </LI>
<LI>X-Face support </LI>
<LI>External editor support </LI>
<LI>Message queueing </LI>
<LI>Draft message function </LI>
<LI>Template</LI>
<LI>Line-wrapping </LI>
<LI>Clickable URI </LI>
<LI>XML-based addressbook </LI>
<LI>LDAP addressbook </LI>
<LI>Jpilot addressbook (for Palm types handhelds)</LI>
<LI>Newly arrived and unread message management </LI>
<LI>Multiple MH folder support </LI>
<LI>Mew/Wanderlust compatible key bindings </LI>
<LI>News reader function </LI>
<LI>Printing </LI>
<LI>UIDL support </LI>
<LI>APOP authentication </LI>
<LI>SMTP AUTH support</LI>
<LI>IPv6 support </LI>
<LI>GPG encryption and signature</LI>
<LI>Autoconf, automake support </LI>
<LI>Support of i18n of messages by gettext </LI>
<LI>Supports many locales, including UTF-8 (Unicode), when using libjconv </LI>
<LI>IMAP4 compliant</LI>
</UL>
This list is not complete, but this will at least show you the most common features in Sylpheed.
<H2><A NAME="ss1.4">1.4 Methods for managing messages</A>
</H2>
<P>There are several ways to manage messages. The best known is <CODE>not at all.</CODE>
<P>Too many people receive lots of e-mails and just let them end up in the INBOX folder. Which after a while becomes unmanageable. Try to locate that one mail about an important event you got 5 days ago, in a mailbox that has over 5000 messages in it. Even when sorted on date, it might take you a tremendous time to locate it.
<P>For this there are <CODE>mailfolders and mailboxes.</CODE>
<P>When you read on in this manual, you will learn about creating mailboxes and also folders that can contain more mailboxes. What are these good for?
<P>Overview. Simple as that. In different mailboxes you can store different kinds of mails. Suppose you are a member of a kiting club. And you get at least 30 e-mails per day from that club. The smart thing to do now is to create a separate mailbox for these mails. So when an e-mail comes in from the kiting club, you can move it to the kiting club mailbox. That way you know that you have all your kiting e-mails in one place.
<P>Tedious, you say? To move 30 mails a day to that box, when they come in at random moments? You bet that is a tedious job. You can be certain that you will miss that very important one about transport to the kiting ground where you will have the contest of biggest and most beautiful kite!
<P>Well, also for this there is a solution. Those are called <CODE>filters</CODE>.
<P>Filters can automate the process of moving e-mails to new locations. Further on in this manual you will also learn about setting up filters, so you do not have to move these kiting e-mails to the kiting club mailbox.
<P>
<H3>Okay, so what is the difference between a mailbox and a mailfolder?</H3>
<P>This is actually the exact same thing as you do on your harddisk. You create directories in which you can put files and more directories.
<P>In the case of Sylpheed, you can create a mailbox in which you can put more mailboxes that somehow belong together. For example, you could create a mailbox (folder) that contains the mailboxes for all the mailing lists you belong to.
<P>A word of clarification is perhaps in need here. In Sylpheed, a maillbox is nothing more than a directory. And in a directory you can create a new directory. But also files. And Sylpheed stores each e-mail in a separate file on disk.
An example of how a mailbox tree could look is
<P>
<P>
<P>
<P>
<P>As you can see, there is no real limit to the way you can set up your mailboxes. As long as you have diskspace available, you can create mailboxes and mailboxes within mailboxes.
<P>Of course, you should observe some common sense when you start creating mailboxes. To keep all mail in one place is not a good idea, but to create a maze of mailboxes is not a good idea either!
<H2><A NAME="ss1.5">1.5 Features for the future</A>
</H2>
<P>This is a special chapter. As with all open source programs, many features can be requested by you, the user of Sylpheed. The best way to join in on the talks is to join one of the mailing lists on Sylpheed. For this, you can turn to the Information section of this manual and read up on how to join a mailing list.
<HR>
<A HREF="sylpheed-2.html">Next</A>
Previous
<A HREF="sylpheed.html#toc1">Contents</A>
</BODY>
</HTML>
|
