Binc IMAP

+- AUTHENTICATE no longer requires first argument to be upper case +- Removed some debug info from the log files +- Fixed problem with getting kicked off when the uidvalidity bounces + at first select. diff --git a/doc/OLD/ChangeLog.1.3 b/doc/OLD/ChangeLog.1.3 new file mode 100644 index 0000000..cca9e3c --- /dev/null +++ b/doc/OLD/ChangeLog.1.3 @@ -0,0 +1,76 @@ +* Since 1.3.3: + - Added quotes to the configure.in and m4 scripts to + prevent a configure error on some platforms. + - Updated the copyright headers. + - Fixed several bugs in the handling of command line options. + - Updated the man pages. + - Refactored Maildir::updateFlags() + - Fixed the use of timeouts in the SSL device; an uninitialized + variable was causing select() to sleep too long. + - bincimap-up now has a fixed timeout of 60 seconds, and the main + server times out after 30 minutes. + - Fixed timeouts in IO devices. + - Now renames files with ":2," when moving them from new/ to cur/. + - Added heuristics to help detect errors when invoking checkpassword. + - Fixed the "make cert" and "make testcert" scripts. + - Improved the logging mechanisms. + - The server reports an error correctly when started in SSL mode, + without any compiled-in SSL support. + - Fixed a bug in the BODY response. + - Fixed a bug in the INTERNALDATE response. + - LIST and LSUB now allow the reference to end with the delimiter + character. + - The server now handles strftime returning 0 (for example, if the + passed buffer was too short). + - Merged several patches from Jerry LundstrÃ¶m. fsync() fixes for + NFS, and a patch that allows 1.2 subscribe lists to work with 1.3, + - Integrated Jerry LundstrÃ¶m's patch to prevent resetting + of the mailbox path when a mailbox is closed. + - Integrated Jerry LundstrÃ¶m's patch to allow changing + of the mailbox delimiter. + - When updating flags, the list of files is read first, then + iterated when renaming files. This removes a race condition + on XFS, where renaming files changed the order in which + they are scanned. + - Fixed a bug in the response to BODY fetches, where the + list of headers would be returned also when no headers + were in the fetch attribute. + - Fixed a bug where the server would not recover properly + after a client tried a command in the wrong state. + +* Since 1.3.2: + - The response code is now included in the OK response. + - Compile errors fixed. + - Replaced opendir()/dirfd() with open(). + - Fixed a lockup due to dangling symlinks. + - Fix a bug where FIELDS in a BODY fetch was empty. + - Added a missing space in RFC822.SIZE response. + - A memory leak and a bug caused by saving the subscribed + file to a full file system were fixed. + - Fixed the --logtype command line argument. + - Fixed LITERAL+ support in APPEND. + - Fixed a bug in the LSUB operator where a map iterator + was used on a multimap. + - Binc 1.3 now compiles with --without-ssl. + - Integrated several bugfixes from 1.2. + +* Since 1.3.1: + - Moved chroot settings out of the conf files and into + configure. + - Fixed wildcards in LIST and LSUB. + - Fixed the line count for multiparts in the MIME parser. + - Syncs the directory when saving the cache file. + - Fixed LITERAL+ support in APPEND. + - Fixed IODevice:readStr() and how it's used in APPEND. + - Assume IMAPdir as the default depot instead of Maildir++. + - Documentation updates: README, README.SSL and README.DEPOT. + - Added native protocol dumping support by exporting the + PROTOCOLDUMP variable. + - Compile fixes. + +* Since 1.3.0: + - Fixed lockups due to major bugs in the IODevice classes. + - Fixed bugs in the refactored MIME parser that rendered + it useless. + - Tested with pine, Mozilla mail and Evolution. + diff --git a/doc/OLD/HTML/bincimap-faq.html b/doc/OLD/HTML/bincimap-faq.html new file mode 100644 index 0000000..61e7129 --- /dev/null +++ b/doc/OLD/HTML/bincimap-faq.html @@ -0,0 +1,926 @@ + + + + + + + + Binc IMAP - FAQ + + + + + + + + + + + + + + + + + + +

+ + + + + + + + + +

+ + + + + +

Binc IMAP - FAQ

+ GNU General Public License
+ Andreas Aardal Hanssen <andreas@hanssen.name> +

+ +

General questions +
+
Q: Why did you start writing Binc IMAP?
+
Q: What is "Binc"?
+
+
About Binc IMAP +
+
Q: What are the advantages of Binc IMAP?
+
Q: So Binc IMAP doesn't focus on security?
+
Q: Is Binc IMAP fast?
+
Q: Is Binc IMAP a stable, secure server?
+
+
Configuration +
+
Q: Which configuration files are used by Binc IMAP?
+
Q: How can I tell Binc IMAP where my mailboxes/folders are?
+
Q: How can I get SSL to work?
+
+
Usage +
+
Q: How do I find my folders in Binc IMAP?
+
+
Authentication +
+
Q: How does Binc IMAP authentication work?
+
+
Compiling +
+
Q: How do I fix this: "Unable to find required function getopt_long"?
+
Q: How do I fix this: "Unable to find the crypto library which is part of OpenSSL"?
+
Q: How do I fix this: "Unable to find the ssl library which is part of OpenSSL"?
+
+
Installing +
+
Q: How do I install Binc IMAP?
+
Q: Why does Binc IMAP (RPM) install under /opt?
+
+

+ +

+ + +Q: Why did you start writing Binc IMAP? + + +

+
First of all, I work a lot with qmail servers, and there haven't +really been many Maildir capable IMAP4rev1 servers around. I used +Courier-IMAP for years, but after loads of abuse from the Courier +community and its author, I found that earth had room for one more +IMAP4rev1 server.
+ +
Enjoying the simplicity of qmail-pop3d, I decided to create an IMAP +server that was equally simple to install and use, and that could work +side-by-side with qmail-pop3d to provide IMAP service to qmail +users.
+ +
I had already written an IMAP server for proxying POP3-accounts at +work, and I had so many good experiences from that project that I +beleived that I could really write a great IMAP server.
+ +
Well, it's up to you to determine how great it is, but I swear it has +it's advantages over the existing Maildir capable IMAP servers out +there.
+

+ +

+ + +Q: What is "Binc"? + + +

+ +
This should be quite obvious: Binc Is Not Courier-IMAP :-).
+ +

+ +

+ + +Q: What are the advantages of Binc IMAP? + + +

+ +
Binc IMAP is a light weight alternative to existing IMAP +servers. It's easier to install, easier to maintain, and it's easy to +integrate into existing (perhaps legacy) authentication +environments.
+ +
Binc IMAP is small and simple. The total number of lines of source +code is much smaller in Binc than in the other servers. Version +1.0.24-1 of Binc IMAP has about 18000 lines of code. There are only +17000 lines of hand written code, including comments. Few lines in +itself does not imply that the code is better, but it's +certainly much easier to maintain.
+ +
It is also written in C++, using standard C++ data components. If +this server crashes, it'll most likely abort, and not suffer a +segmentation fault, which is the most common reason for exploits.
+ +
Binc IMAP uses an object oriented design all the way. A modular, +simple design with few lines of code means that it's easier to uncover +bugs, and it's easier to fix them without disturbing the rest of the +source code.
+ +

+ +

+ + +Q: So Binc IMAP doesn't focus on security? + + +

Security comes naturally with a service with a clean, correct + design and no bugs
Security can not be claimed. To prove that a server is not + secure, one must simply find a way to exploit it. Claiming + that a server is secure is like claiming that nobody can find a way + to break it.
The only true argument is to prove that it's secure. And + that's almost impossible.
Binc IMAP focuses on creating a service with a clean, correct + design with no bugs. Time and experience will tell wether it's a + secure server or not.

+ +

+ + +Q: Is Binc IMAP fast? + + +

Binc IMAP focuses its optimizations on the type of activity that +dominates the lifetime of an IMAP connection, which is idle time.

+ +

Pending updates: When a client issues NOOP, CHECK or similar, + the server must give the latest changes to the depository. If no + changes have been made, this operation will with Binc IMAP + consist of only two stat-calls, which is extremely fast.
FETCH: Multiple subsequent operations on the same message + will never cause the message to be parsed more than twice - once + for header-only operations and once for full message info.
STATUS: The status command is typically used to check for + new messages in all subscribed mailboxes. If no changes have been + made to a mailbox, the status command in Binc IMAP consists of + only two stat calls, which is extremely fast.
SEARCH: The search keys are weighted, and the search query is + sorted with lightest-search first. This prevents unnecessary + processing of slow search keys if the light search keys do not + match the message set.

+ +

Some activity is not optimal in Binc IMAP, and searching for random +text in particular is no faster than a sequential search using +standard UNIX tools such as grep. Searching for text in a large +mailbox is quite rare, however, compared to the random activity of +close-to-idle clients.

+ +

+ + +Q: Is Binc IMAP a stable, secure server? + + +

+
It's hard to write bug free programs, especially with a complex +protocol like IMAP4rev1. Any attempts to verify code usually comes +down to the limitations in the author's experience with +verification. Or as +Donald Knuth +said (my favorite quote):
+ +
"Beware of bugs in the above code; I have only proved it correct, + not tried it."
+ +
Knuth teaches that it can be easy to prove that your code is +correct, but who's going to prove that your proof is correct? +Proving your proof might turn out to be close to impossle. What you +can have, is conventions and principles that prevent bugs from showing +up in your programs. Here are mine:
+ +
+
Don't reinvent the wheel. Unless absolutely necessary, write + code that doesn't exist already.
+
Spend your time on making it work as simple as possible, + then start making optimizations.
+
Don't let optimization obfuscate your source code.
+
Find a better algorithm, or if you can't get the speed that you + want, change to a more efficient programming language.
+
Handle all error conditions.
+
Avoid buffers altogether.
+
Don't hand write parsers unless strictly necessary - they are + hard to get right.
+
For G's sake, be compliant! If the standard has flaws, then + help fix the flaws - don't break the standard.
+
+ +
Now I don't pay $2.56^n where n equals the total number of +bugs discovered in Binc IMAP, but I will certainly give you +many pats on the back if I get the chance. :-)
+ +
I could go on and on, but the point is that I have tried my best to +perform all the expected tasks in the most logical and obvious way +possible, using all my C++ security experience to aid me. But at the +time of writing, the server is young, the community small, and we are +only in Beta. So time will have to tell how stable and secure we +are.
+ +

+ +

+ + +Q: Which configuration files are used by Binc IMAP? + + +

+
+
/etc/opt/bincimap/supervise/imap/run
+
/etc/opt/bincimap/supervise/imaps/run
+
/etc/opt/bincimap/xinetd/imap
+
/etc/opt/bincimap/xinetd/imaps
+
+ +
These files are for administrators. You can set up Binc IMAP's +authentication method here.
+ +
+
/etc/opt/bincimap/bincimap.conf
+
+ +
This first file is for setting global administrator settings, such +as paths to the host's SSL certificate, timeouts for idle clients and +so on. It need not be readable for anyone but root.
+ +
+
$HOME/.bincimap
+
+ +
This file is for individual settings, such as what the exact path +is to this user's depository, which default Mailbox type to use and +which type of depository the user uses.
+ +

+ +

+ + +Q: How can I tell Binc IMAP where my mailboxes/folders are? + + +

+ +
The configuration file has a section called Mailbox. You can +set the path to your users' mail depository there, relative to +the users' home areas.
+ +
If your depository is not is users' homeareas, for instance if your +depository has a /var/mail/user/ structure, you can safely set +path to "." or "". Your authenticator must then +change to the full path of the depository, /var/mail/user/, +before invoking bincimapd.
+ +
For a Maildir++ depository under standard home areas, with +the mailbox path set to "Maildir" in bincimap.conf, your structure +would typically look something like this:
+ + + + + + + + + + + + +
File system + IMAP + Description +
+
+~/Maildir/
+~/Maildir/.Sent/
+      
+
+
+"INBOX"
+"INBOX/Sent"
+      
+
+
+The main mailbox, the INBOX.
+A user created mailbox.
+      
+
+ +
If you use IMAPdir (setting depot="IMAPdir" and for instance +path="IMAPdir"), the structure would be slightly different:
+ + + + + + + + + + + + +
File system + IMAP + Description +
+
+~/IMAPdir/INBOX -> ../Maildir
+~/IMAPdir/Sent/
+~/IMAPdir/Sent.2003/
+~/Maildir/
+      
+
+
+"INBOX"
+"Sent"
+"Sent/2003"
+<zip>
+      
+
+
+The main mailbox symlink, the INBOX.
+A user created mailbox.
+A sublevel user created mailbox.
+Invisible.
+      
+
+ +
With no seperate directory for the mail depository, your structure +would be like this with IMAPdir, and similar with Maildir++ (the +prefix folder is simply dropped, and INBOX itself is a Maildir, note +that the MTA must be instructed to deliver to INBOX and not +Maildir):
+ + + + + + + + + + + + +
File system + IMAP + Description +
+
+~/INBOX
+~/Sent/
+~/Sent.2003/
+      
+
+
+"INBOX"
+"Sent"
+"Sent/2003"
+      
+
+
+The main mailbox, the INBOX, a Maildir.
+A user created mailbox.
+A sublevel user created mailbox.
+      
+
+ +

+ +

+ + +Q: How can I get SSL to work? + + +

+ +
SSL in Binc IMAP is quite simple to set up. First you need a PEM +encoded certificate file. In some distributions, you can generate this +file by changing to /usr/share/ssl/certs and running "make". A script +will give you the option to build a PEM file.
+ +
When you have a PEM file, edit bincimap.conf in the SSL +section . You need to add an item called pem file and set it to +point to your PEM certificate. The path name must be absolute. For +example:
+ +
+  SSL {
+    pem file = "/usr/share/ssl/certs/mypemfile.pem",
+    ca file = "",
+    cipher list = "!ADH:RC4+RSA:HIGH:MEDIUM:LOW:EXP:+SSLv2:+EXP",
+    verify peer = "no"
+  }
+
+ +
The item ca file in bincimap.conf tells Binc IMAP +which file on your system contains a bundle of certificate +authorities.
+ +
Next comes the item called cipher list. It tells Binc IMAP +about which ciphers you want your server to support. This depends on +what version of OpenSSL you're running.
+ +
Last comes an option called verify peer. This tells Binc +IMAP wether to attempt to verify the client's identity.
+ +
Visit this link +at the Apache.org website to read more about SSL and TLS +principles.
+ +

+ +

+ + +Q: How do I find my folders in Binc IMAP? + + +

+ +
Binc IMAP can be configured to use two types of depositories: +Maildir++ and IMAPdir.
+ +
Using Maildir++, all folders in Binc IMAP must be subfolders of +INBOX. This is the default setting.
+ +
This means that if you want to create a folder called work, +you have to create INBOX.work or INBOX/work.
+ +
For some graphical IMAP clients like Outlook (look out!) or +Mozilla Mail, this means you need to right click on +INBOX and select "Create subfolder".
+ +
Using IMAPdir, folders can be created in any levels. See also this question.
+ +

+ +

+ + +Q: How does Binc IMAP authentication work? + + +

+
Binc IMAP is spawned by xinetd, tcpserver or any other TCP wrapper +running as root.
+ +
It immediately goes into pre-authentication mode, where it expects +the client to enter STARTTLS if the client is not already running an +SSL connection. When in TLS/SSL mode, it will accept clear text +authentication.
+ +
Binc IMAP uses the same authentication method as +qmail-pop3d, checkpassword. The pre-authentication stub invokes +the checkpassword compatible authenticator, which if the password is +correct in turn invokes the main Binc IMAP daemon.
+ +
The checkpassword documentation is +required reading for everyone running Binc IMAP.
+ +

+ +

+ + +Q: How do I fix this: "Unable to find required function getopt_long"? + + +

+ +
The getopt_long function is a GNU extension to the POSIX.2 getopt +function. It allows long arguments such as --enable-ssl.
+ +
Unfortunately, this function is not defined on all +platforms. Specifically, it is known to not exist on FreeBSD.
+ +
For FreeBSD users, install gnugetopt from ports. Otherwise, +post this problem with as much relevant info as you can provide, to +the mailing list.
+ +

+ +

+ + +Q: How do I fix this: "Unable to find the crypto library which is part of OpenSSL"? + + +

+ +
The crypto library is a part of OpenSSL. This +library is required for Binc IMAP to compile.
+ +
If you can not get Binc IMAP to compile with OpenSSL, there should +be a static RPM package available for download.
+ +

+ +

+ + +Q: How do I fix this: "Unable to find the ssl library which is part of OpenSSL"? + + +

+ +
The crypto library is a part of OpenSSL. This +library is required for Binc IMAP to compile.
+ +
If you can not get Binc IMAP to compile with OpenSSL, there should +be a static RPM package available for download.
+ +

+ +

+ + +Q: How do I install Binc IMAP? + + +

+ +
The easiest way to install Binc IMAP on your server is to +follow these instructions:
+ +
+
Download the RPM from http://www.bincimap.andreas.hanssen.name/dl/RPMS
+
Install the RPM
+
Copy, edit and perhaps symlink the configuration files: +
+
with daemontools: +
+
ln -s /etc/opt/bincimap/supervise/imap /service/imap
+
ln -s /etc/opt/bincimap/supervise/imaps /service/imaps
+
+
+
with xinetd: +
+
ln -s /etc/opt/bincimap/xinetd/imap /etc/xinetd.d/imap
+
ln -s /etc/opt/bincimap/xinetd/imaps /etc/xinetd.d/imaps
+
service xinetd restart
+
+
+
+
+
Check that the service is up by connecting using a standard IMAP client
+
+ +
If you want to build Binc IMAP from source, there's a README +file that gives you the instructions step by step, inside the +tarball. You can also get some clues by inspecting the bundled +bincimap-spec file's install section.
+ +

+ +

+ + +Q: Why does Binc IMAP (RPM) install under /opt? + + +

+ +
The reason for this is that I have tried my best to follow the File System Hierarchy +Standard.
+ +
Binaries go under /opt/bincimap/bin
+ +
Host specific configuration goes under /etc/opt/bincimap
+ +
If you want your files elsewhere, there's always the option to build +the project from source. :-)
+ +

+ +

+ + + + + + + + +

+ +

+

+

+ + + ++FLAGS \Flagged +* FETCH (FLAGS (\Seen \Flagged)) +8 OK STORE completed + + + +

+ +

If all these tests work fine, try connecting with an IMAP client +such as Mozilla, Outlook, Eudora, Netscape, Mutt or Pine.

+ + + +

+ + +Q: How do I find my folders in Binc IMAP? + + +

+ +
Binc IMAP can be configured to use two types of depositories: +Maildir++ and IMAPdir.
+ +
Using Maildir++, all folders in Binc IMAP must be subfolders of +INBOX. This is the default setting.
+ +
This means that if you want to create a folder called work, +you have to create INBOX.work or INBOX/work.
+ +
For some graphical IMAP clients like Outlook (look out!) or +Mozilla Mail, this means you need to right click on +INBOX and select "Create subfolder".
+ +
Using IMAPdir, folders can be created in any levels. See also this question.
+ +

+ +

+ + +Q: How does Binc IMAP authentication work? + + +

+
Binc IMAP is spawned by xinetd, tcpserver or any other TCP wrapper +running as root.
+ +
It immediately goes into pre-authentication mode, where it expects +the client to enter STARTTLS if the client is not already running an +SSL connection. When in TLS/SSL mode, it will accept clear text +authentication.
+ +
Binc IMAP uses the same authentication method as +qmail-pop3d, checkpassword. The pre-authentication stub invokes +the checkpassword compatible authenticator, which if the password is +correct in turn invokes the main Binc IMAP daemon.
+ +
The checkpassword documentation is +required reading for everyone running Binc IMAP.
+ +

+ +

+ + +Q: What does this mean: "Server broke for , /bin/checkpassword returned 111 (internal error)"? + + +

+ +
This log line is printed by bincimap-up, and reflects how +confusing checkpassword can be at times. Most often, though, the +problem is easy to solve.
+ +
Log in as the user who tried to log in. If you are using a virtual +mail account system like vpopmail, become the user that mail accounts +are stored as.
+ +
Try running the bincimapd daemon manually. If you can execute the +binary, there will be no output and the server will simply exit. Most +often, however, you will get an error such as "command not found" or +"permission denied". This should explain quite easily what the problem +is. Note that the bincimapd binary must have read and execute +permissions for all users (755).
+ +
If this didn't solve your problem, please post to the mailing list +a stack trace. To create a stacktrace, attach to tcpserver/xinetd +using "strace -s 1024 -f -p 2>&1 >dump". Log in to reproduce the +error. Then interrupt the strace program and email the "dump" file to +the mailing list. Note: It is likely that the dump file +contains passwords in plain text.
+ +

+ +

+ + +Q: How do I fix this: "Unable to find required function getopt_long"? + + +

+ +
Note: This only applies to versions 1.1.6 or older.
+ +
The getopt_long function is a GNU extension to the POSIX.2 getopt +function. It allows long arguments such as --enable-ssl.
+ +
Unfortunately, this function is not defined on all +platforms. Specifically, it is known to not exist on FreeBSD.
+ +
For FreeBSD users, install gnugetopt from ports. Otherwise, +post this problem with as much relevant info as you can provide, to +the mailing list.
+ +

+ +

+ + +Q: How do I fix this: "Unable to find the crypto library which is part of OpenSSL"? + + +

+ +
The crypto library is a part of OpenSSL. This +library is required for Binc IMAP to compile.
+ +
If you can not get Binc IMAP to compile with OpenSSL, there should +be a static RPM package available for download.
+ +

+ +

+ + +Q: How do I fix this: "Unable to find the ssl library which is part of OpenSSL"? + + +

+ +
The crypto library is a part of OpenSSL. This +library is required for Binc IMAP to compile.
+ +
If you can not get Binc IMAP to compile with OpenSSL, there should +be a static RPM package available for download.
+ +

+ +

+ + +Q: How do I install Binc IMAP? + + +

+ +
The easiest way to install Binc IMAP on your server is to +follow these instructions:
+ +
+
Download the RPM from http://www.bincimap.andreas.hanssen.name/dl/RPMS
+
Install the RPM
+
Copy, edit and perhaps symlink the configuration files: +
+
with daemontools: +
+
ln -s /etc/opt/bincimap/supervise/imap /service/imap
+
ln -s /etc/opt/bincimap/supervise/imaps /service/imaps
+
+
+
with xinetd: +
+
ln -s /etc/opt/bincimap/xinetd/imap /etc/xinetd.d/imap
+
ln -s /etc/opt/bincimap/xinetd/imaps /etc/xinetd.d/imaps
+
service xinetd restart
+
+
+
+
+
Check that the service is up by connecting using a standard IMAP client
+
+ +
If you want to build Binc IMAP from source, there's a README +file that gives you the instructions step by step, inside the +tarball. You can also get some clues by inspecting the bundled +bincimap-spec file's install section.
+ +

+ +

+ + +Q: Why does Binc IMAP (RPM) install under /opt? + + +

+ +
The reason for this is that I have tried my best to follow the File System Hierarchy +Standard.
+ +
Binaries go under /opt/bincimap/bin
+ +
Host specific configuration goes under /etc/opt/bincimap
+ +
If you want your files elsewhere, there's always the option to build +the project from source. :-)
+ +

+ +

+ + + + + + + + +

+ +

+ + + + + +

+

+ + + diff --git a/doc/OLD/HTML/bincimap-goals.html b/doc/OLD/HTML/bincimap-goals.html new file mode 100644 index 0000000..fd387e8 --- /dev/null +++ b/doc/OLD/HTML/bincimap-goals.html @@ -0,0 +1,160 @@ + + + + + + + + Binc IMAP - Goals + + + + + + + + + + + + + + + + + + +

+ + + + + + + + + +

+ + + + + +

Binc IMAP - Goals

+ GNU General Public License
+ Andreas Aardal Hanssen <andreas@hanssen.name> +

+ +

+ +The Binc IMAP project is more than programming. This is a list of the main goals and visions +that the author of Binc IMAP has put to ground. + +
+
Helpful, hospitable community +
+
Although it is expected that users of Binc IMAP do their homework before posting, the server author + and community of the Binc IMAP mailing list will be friendly and will approach everyone with respect. + The same is expected from those who post to the list.
+
There will be no RTFM on the project's mailing list. Flaming and personal insults on the project's mailing list will result in banning of the originator.
+
The community is encouraged to pay back to the project's contributors by sharing their own + contributions to Binc IMAP through the GPL license.
+
+
+
Security through good design +
+
A well designed server is less exposed to bugs than a poorly designed server.
+
The server will strive to use every kind of security enhancing feature, while + keeping the implementation details as simple as possible.
+
The source is open and downloadable. Potential bugs and/or nasty pieces of + code are easily uncovered when the whole community is able to study every line of + code in detail. Bugs should always be reported to the project's mailing list.
+
+
+
No competition +
+
Under no circumstance will this project be in market driven competition with other + IMAP servers.
+
Binc IMAP is first and foremost a quality driven project.
+
This project is meant to influence the community of authors of + network protocols and servers, and hopes to increase the general quality + of software that is used all over the globe and beyond.
+
+
+
Modularity +
+
Binary modularity +
Pluggable extension support. Modules that are loaded into Binc can change a + great deal of Binc's behavior. Adding your own extension or altering Binc + IMAP's behavior should be as easy as it can get, and it should not require a + recompile of the Binc IMAP core.
+
Pluggable authentication support. By supporting checkpassword + compatible authentication modules, Binc IMAP clients can authenticate against great + number of authorities.
+
+
Source modularity +
With a modular and simple yet advanced object oriented design, it should be + easy to quickly understand what every method and function does. This will + increase third party developers' ability to write extensions and modifications fast.
+
Development of the design and implementation of Binc IMAP will focus on + extensibility, robustness and speed. +
+ +
+
+
Quality over quantity +
+
Binc IMAP's releases are milestones. We strive for perfection.
+
Work on improving the existing design and extensibility will always go ahead of + adding new features.
+
Through extensive module support, the community is encouraged to contribute + to the adding and testing of new features. Core design and implementation will + always focus on quality.
+
+
+
+ +
+Last updated: 2003-03-24 + + +

+ + + + + + + + +

+ +

+

+

+ + + +"> + + + + + + + +

+

+ + + diff --git a/doc/OLD/HTML/bincimap-imapdir.html b/doc/OLD/HTML/bincimap-imapdir.html new file mode 100644 index 0000000..2309a0d --- /dev/null +++ b/doc/OLD/HTML/bincimap-imapdir.html @@ -0,0 +1,257 @@ + + + + + + + + Binc IMAP - IMAPdir + + + + + + + + + + + + + + + + + + +

+ + + + + + + + + +

+ + + + + +

Binc IMAP - IMAPdir

+ GNU General Public License
+ Andreas Aardal Hanssen <andreas@hanssen.name> +

+ +

+ +
This document describes the generic mail folder structure +IMAPdir.
+ +
The goal of the work behind this specification is to provide the +community with an unambiguous representation of a mailbox hierarchy +where a mailbox name has a one-to-one match against a file system +representation. The hierarchy and naming style is inspired by the +IMAP4 protocol.
+ +
Rather than being a completely new mailbox format, this specification +sets conventions on how to represent a mailbox hierarchy on a file +system, using existing mailbox formats. IMAPdir is not bound to +any protocol.
+ +
IMAPdir works with any mailbox format where one mailbox can +be identified by a file, a directory or a symbolic link. One entry in +an IMAPdir folder is a candidate for a mailbox. If the +IMAPdir client can not identify a directory entry as a +selectable mailbox, then the client must either skip the entry or +mark it as invalid (in IMAP, marked as \NoSelect).
+ +
+
There is no limitation to the type of file system or the number of +file systems represented inside an IMAPdir.
+
There are no reserved ordinary folder +names such as "Sent", "Draft" or "Trash".
+
Clients of the mailboxes inside an IMAPdir +folder must follow the respective format and protocol conventions +strictly.
+
+ +
The format of a mailbox representation in IMAPdir is a +sequence of one or more US-ASCII characters (32-126), encoded using +the following rules:
+ +
+
A dot '.' character represents a soft hierarchy delimiter with two exceptions: +
+
A leading dot represents the dot itself.
+
A dot '.' preceded by a backslash '\' represents the dot '.' itself.
+
+
+
A backslash '\' preceded by a backslash '\' represents the backslash '\' itself. For all other cases than before a dot '.' or a backslash '\', a stray backslash '\' character is considered an error.
+
A backslash '\' as the first character of an entry is considered an error.
+
All other characters represent themselves.
+
+ +Note that the protocol used to fetch the mailbox using the +structuring IMAPdir convention may restrict the character set +allowed. The clients must in those cases translate the mailbox +names to a selectable format. + +
As with Maildir++, +submailboxes can not be represented in a recursive fashion in the file +system. The mailbox' representation name will contain the soft +hierarchy delimiter character dot '.', and all mailboxes must reside +in the same root level directory.
+ +
The following example shows the typical content of an +IMAPdir stored under the directory mail/. The file +system column displays the contents as viewed by the UNIX command +'ls -al -F'.
+ + + + + + + + + + + + +
File system + IMAP + Description +
+
+mail/INBOX -> /var/mail/paul
+mail/INBOX.old/ -> ../Maildir/
+mail/INBOX.outbox/
+mail/work
+mail/3rd\. of July
+mail/Sent.2003.Jan/
+mail/Sent.2003.Feb/
+mail/Sent.2003.Mar/
+mail/.foo
+      
+
+
+"INBOX"
+"INBOX/old"
+"INBOX/outbox"
+"work"
+"3rd. of July"
+"Sent/2003/Jan"
+"Sent/2003/Feb"
+"Sent/2003/Mar"
+".foo"
+      
+
+
+Symbolic link to mbox
+Symbolic link to Maildir
+Maildir
+mbox
+mbox
+Maildir
+Maildir
+Maildir
+mbox
+      
+
+ +
In other multi level mailbox formats, INBOX is treated as a +special case.
+ +
+
Maildir++
+ +
+
Maildir++ + defines the mail directory itself as + INBOX. Any subdirectories inside starting with a single dot + '.', and containing the file maildirfolder are interpreted as + a Maildir++ + submailbox. + +
A Maildir is by + Dan J. Bernstein's definition identified by a directory that + contains the subdirectories cur, + new and tmp and nothing else.
+ +
The Maildir++ + definition follows naturally from Maildir++ + being an extension to Dan J. Bernstein's Maildir + format. However, although the directory ~/Maildir/ itself is a + standard representation of INBOX for Maildir clients, it is + not standard for other mailbox formats. With Maildir++, + your mailboxes and INBOX in particular must be a Maildir. +
+ +
mbox
+ +
+
When using the mbox storage format, the user's INBOX is typically + stored at /var/spool/mail/<username>.
+ +
Using this format, the mail depository client must both have the + path to the user's INBOX and the path to the user's local + mailbox depository, typically mail/.
+
+ +
+ +
Note that although IMAPdir has no restrictions with regards +to mailbox names, the protocol that uses IMAPdir might. For +example, IMAP servers will require the mailbox INBOX to be +present.
+ +
+ +
Last updated on 2003-03-20.
+ +
Please direct comments to IMAPdir or this document to the +Binc IMAP mailing list. Remember to search the archives +first.
+ +

+ + + + + + + + +

+ +

+

+

+ + + diff --git a/doc/OLD/HTML/bincimap-tech.html b/doc/OLD/HTML/bincimap-tech.html new file mode 100644 index 0000000..e5fce32 --- /dev/null +++ b/doc/OLD/HTML/bincimap-tech.html @@ -0,0 +1,503 @@ + + + + + + + + Binc IMAP - Technical Documentation + + + + + + + + + + + + + + + + + + +

+ + + + + + + + + +

+ + + + + +

Binc IMAP - Technical Documentation

+ GNU General Public License
+ Andreas Aardal Hanssen <andreas@hanssen.name> +

+ +

Binc in my home area, IMAPdir and cousins

+ +

+ +
Binc IMAP uses either Maildir++ +or a structure called IMAPdir to +store its set of mailboxes. IMAPdir is more or less similar to Maildir++, +but it provides more flexibility with regards to mailbox names and +hierarchy structure.
+ +
In a sense, IMAPdir takes all +the goods from Maildir and adds root +level mailboxes, submailboxes both of regular root level mailboxes and +of the special mailbox INBOX, mail in mailboxes of any level, and with +no restrictions.
+ +
In the root of the IMAPdir +structure, Binc IMAP stores the list of a user's subscribed folders in +a file called +bincimap-subscribed. This file should only be edited manually +if you are confident with Binc::Storage. Normally the +administrator and the IMAP user will leave this to Binc IMAP.
+ +
Binc IMAP's Maildir backend +(default) will temporarily create a lock file called +bincimap-scan-lock inside a Maildir when it is +scanning for mailbox changes and delegating unique message +identifiers. This is to ensure that UIDs are delegated exactly once to +every message that has been detected by any one Binc IMAP server +instance.
+ +
Inside each Maildir, Binc IMAP +stores two files that allow multiple instances of the server to +communicate the state and changes of the mailbox: +bincimap-uidvalidity and +bincimap-cache. These files are safe to delete, although that +will trigger UIDVALIDITY to bounce and clients may have to +resynchronize their local state.
+ +

+ +

Object Oriented Design: Brokers, Depots, Operators.

+ +

+ + + + + + +
+
Binc IMAP's design is simple and modular. This + makes it easy to maintain and extend.
+ +
Although the IMAP protocol is relatively complex, you will + find that Binc IMAP's solution is surprisingly easy to + grasp.
+ +
At the heart of Binc IMAP's implementation lies the basic + functionality for Object Oriented Design provided by the ISO C++ + standard and general knowledge in the area of standard Design + Patterns.
+ +
The main components are:
+ +
+
The Broker
+
The BrokerFactory
+
The Command
+
The Depot
+
The DepotFactory
+
The Mailbox
+
The Operator
+
The Session
+
The IO
+
+ + +
+ +
+Broker + +
One Broker holds a set of Operators. For each + state Binc IMAP is in, the BrokerFactory delegates exactly one Broker to hold the relevant Operator objects.
+ +
Typically, an Operator can be assigned to + more than one Broker. For example, the Operator that serves the IMAP command "NOOP" (a + command that is available in all three IMAP states), + NoopOperator, is available in all Broker objects.
+ +
The Broker is responsible for first passing + the Depot and the IO + singleton to the appropriate Operator, + generating a Command object.
+ +
The Broker is also responsible for passing + the resulting Command object to the Operator together with the Depot, generating the untagged responses + that come as a result of the processing.
+ +
+ + + + +
+
+Broker *broker = BrokerFactory.getBroker(STATE_SELECTED);
+if (broker != NULL)
+  throw CriticalException("no broker for selected state");
+
+Command command;
+
+try {
+  broker.parse(com, command);
+  broker.process(depot, command);
+} catch (...
+        
+
+ +
+BrokerFactory + +
The BrokerFactory manages the Broker objects.
+ +
Given a state, the BrokerFactory provides a Broker that holds all the Operator objects available to the client.
+ +
This provides a modular and safe separation of the priviledges + available at the different states in the IMAP session.
+ +
The preauthenticate stub has a BrokerFactory that can only generate Broker objects for the non-authenticated + state.
+ +
+Command + +
A Command object holds all information + that was passed to the Operator that served + a specific IMAP command.
+ +
Command objects are named. Examples of + such names are "CHECK", "SUBSCRIBE" and "LOGOUT".
+ +
For the name "FETCH", the Command object + is decorated with + sequence set, optionally a section and so on. The + parse() method in each Operator is + responsible for decorating the Command + object.
+ +
The Command object is + short-lived. It is created, decorated, passed on to the Operator, then discarded.
+ +
+Depot + +
A Depot is responsible for handling the + different Mailbox objects, and it is the + mailbox structure authority.
+ +
Given an IMAP mailbox path as input, a Depot + can give the caller a corresponding Mailbox + object if it finds one that successfully identifies the type of Mailbox. + +
The Depot is also aware of what the + default Mailbox type object is. This + Mailbox object is used when creating new IMAP + mailboxes.
+ +
Finally, the Depot is used to translate + mailbox names to a representation on the file system and back. There + are currently two specializations of the Depot + object available: one for Maildir++ + and one for IMAPdir. Each has + its own characteristics in how do translate the mailbox hierarchy to + the file system.
+ + + + + +
+
+Mailbox *mailbox = depot.getDefaultMailbox();
+if (mailbox == NULL)
+  throw CriticalException("no default mailbox provided");
+
+try {
+  mailbox->imapCreate("work/2003/07/todo");
+} catch (...
+        
+
+ +
+DepotFactory + +
The DepotFactory manages the Depot objects.
+ +
New Depot objects are assigned to the DepotFactory in runtime. This makes it easy + to add new Depot objects using loadable + modules. The Depot objects are registered and + accessed via their names, such as "Maildir++" + or "IMAPdir".
+ +
The DepotFactory gives individual + users of Binc IMAP the option to choose the Depot object that suits their needs the best.
+ +
+IO + +
The IO is a global. It consists of two instances - + com and logger.
+ +
com reads and writes characters to and from the client, + and hides the optional SSL encryption.
+ +
logger writes characters to Binc IMAP's log files. It + hides the method used to log data. Currently it supports logging to + stderr and syslog.
+ +
+Mailbox + +
The Mailbox is an abstract for Binc IMAP's different + backends. Bundled with Binc is a backend for Maildir. The class + Maildir inherits Mailbox.
+ +
In short, a Mailbox contains all methods needed for Binc + IMAP to serve a specific backend. It also holds a method to identify + a Mailbox of its own kind.
+ +
All registered Mailbox objects are held by the + Depot.
+ +
+ + + + +
+
+Mailbox *mailbox = depot.getSelectedMailbox();
+if (mailbox == NULL)
+  throw CriticalException("no selected mailbox in selected state");
+
+mailbox->imapExpunge();
+mailbox->imapClose();
+        
+
+ +
+Operator + +
An Operator is associated with an IMAP command such as + "SEARCH" or "AUTHENTICATE". In short, the Operator is used to + perform an arbitrary operation on a Mailbox.
+ +
Typically, an Operator can be assigned to one or more + Broker objects. + +
Operators contain, among others, the two public methods: + parse() and process().
+ +
When given the IO singleton as input, the parse() + method generates a Command object. This object can then be + fed to process() together with a Depot.
+ +
When processing its command, an Operator is allowed to + generate untagged responses and it can also update the + state of a Mailbox, the Depot or the + Session singleton.
+ +
Operator objects are assigned + dynamically to each Broker, making it + very easy to write + extensions that add or replace existing Operator objects using Binc IMAP's loadable + module support.
+ +
+Session + +
The Session is a singleton object that holds + information that is relevant to the current IMAP session.
+ +
Currently, the Session contains information about:
+ +
+
Global configuration (administrator settings)
+
Local configuration (user settings)
+
Command line arguments
+
Folder subscription list
+
+ +
+ +
Last updated on 2003-03-20.
+ +
Please direct comments on this document to the Binc IMAP mailing list. Remember to search +the archives first.
+ +

+ + + + + + + + +

+ +

+

+

+ + + +style with only LF. The MaildirMessage is an + implementation of Message used in Maildir. When using a Maildir + mailbox, Mailbox::iterator will return a reference to a + MaildirMessage. MaildirMessage also uses a MaildirMessageCache + singleton to handle cacheing of messages.

+ +

Although the inside of MaildirMessage both deals with files, + cacheing and MIME, the Operator needs not think about this.

+ + + +

+Operator +

+ +
An Operator is associated with an IMAP command such as + "SEARCH" or "AUTHENTICATE". In short, the Operator is used to + perform an arbitrary operation on a Mailbox.
+ +
Typically, an Operator can be assigned to one or more + Broker objects. + +
Operators contain, among others, the two public methods: + parse() and process().
+ +
The parse() method decorates a Request object. This object can then be fed to + process() together with a Depot.
+ +
When processing its request, an Operator + is allowed to generate untagged responses and it can also + update the state of a Mailbox, the Depot or the Session + singleton.
+ +
Operator objects are assigned + dynamically to each Broker, making it + very easy to write extensions that add or replace existing Operator objects using Binc IMAP's loadable + module support.
+

+ +

+Session +

+
The Session is a singleton object that holds + information that is relevant to the current IMAP session.
+ +
Currently, the Session contains information about:
+ +
+
Global configuration (administrator settings)
+
Local configuration (user settings)
+
Command line arguments
+
Folder subscription list
+
+

+ +

Last updated on 2003-07-31.

+ +

Please direct comments on this document to the Binc IMAP mailing list. Remember to search +the archives first.

+ + + + + + + + + + +

+ +

+ + + + + +

+

+ + + diff --git a/doc/OLD/HTML/bincimap.css b/doc/OLD/HTML/bincimap.css new file mode 100644 index 0000000..cf6c0b7 --- /dev/null +++ b/doc/OLD/HTML/bincimap.css @@ -0,0 +1,8 @@ +a:link { color: #fff; font-size: 12pt; font-family: Arial, Helvetica, Verdana; text-decoration: underline } +a:active { color: #fff; font-size: 12pt; font-family: Arial, Helvetica, Verdana; text-decoration: underline } +a { color: #fff; font-size: 12pt; font-family: Arial, Helvetica, Verdana; text-decoration: underline } +a:vlink { color: #fff; font-size: 12pt; font-family: Arial, Helvetica, Verdana; text-decoration: underline } +body { color: #fff; font-size: 12pt; font-family: Arial, Helvetica, Verdana } +.bodytext { color: #fff; font-size: 12pt; font-family: Arial, Helvetica, Verdana } +.headtext { color: #fff; font-size: 20pt; font-family: Arial, Helvetica, Verdana } + diff --git a/doc/OLD/README b/doc/OLD/README new file mode 100644 index 0000000..ec630b3 --- /dev/null +++ b/doc/OLD/README @@ -0,0 +1,109 @@ +This documentation is free software; you can redistribute it and/or +modify it under the terms of the GNU General Public License as +published by the Free Software Foundation; either version 2 of the +License, or (at your option) any later version. + +You should have received a copy of the GNU General Public License +along with this program; if not, write to the Free Software +Foundation, Inc., 59 Temple Street #330, Boston, MA 02111-1307, USA. + +========================================================================= + +Welcome to Binc IMAP! This is the documentation for v1.3.4. + +The is an unstable development version, and it is not recommended for +production systems. + +Here is a quick guide on how to setup IMAP on your system. + +You can also check out the project home page's FAQ and the Life With +Binc IMAP community documentation site: + +http://www.bincimap.org/ +http://www.lifewithbincimap.org/ + +Binc IMAP requires OpenSSL - http://www.openssl.org/, for SSL support. + +Installation instructions +------------------------- + +Installing Binc IMAP is easy! View the options by passing --help to the +configure script. Here's how to install the server using default options. Log +in as root on your machine, then: + +# ./configure +# make +# make install + +Binc IMAP's "make install" stage tells you exactly where all files are copied. +To uninstall, type "make uninstall". + +Configuring the server +---------------------- + +You need to figure out one thing before you start using the server. Binc IMAP +doesn't run as a standalone TCP server. It relies on a TCP wrapper, like +xinetd, inetd or tcpserver. + + 1) I will be using xinetd. + - This is the recommended default. If you don't know what the other + options are about, then this is definitely the way to go. Just + make sure that xinetd is installed on your server. + + 2) I will be using svscan / tcpserver + - Before anything, make sure that logging works with multilog. + + 3) I will need to use another TCP wrapper. + - You should be able to figure out how to run Binc IMAP by looking + at the bundled xinetd and daemontools files. Otherwise, see if the + community pages can help you along the way. Or post a message to + the mailing list. + +Configuring Binc IMAP is easy! Simply locate your config file called +"bincimap-config". It was installed as part of the "make install" stage. Edit +this file. It contains reasonable defaults, but it should be easy enough to +understand what you'd need to change. + +NOTE: tcpserver users, make sure LOG_TYPE is set to "multilog" if you prefer + using multilog. + +Choose your depot setting with care. The default depot, IMAPdir, is always +best for fresh installs. If you're upgrading from a Courier-IMAP server, the +Maildir++ depot will give you a smoother transition. You should still aim at +moving to IMAPdir. For more on depots (or if you don't know what a depot is in +this setting), see README.DEPOT. + +Check the SSL settings. See also README.SSL for more on generating an SSL +certificate and key. + +Starting the server +------------------- + +This assumes you used /usr/local as prefix when you installed Binc IMAP. + +1) xinetd users: + + a) Create a symlink from /usr/local/etc/xinetd-bincimap to /etc/xinetd.d/imap. + b) Create a symlink from /usr/local/etc/xinetd-bincimaps to /etc/xinetd.d/imaps. + c) Restart xinetd. + +2) svscan users: + + a) Create a symlink from /usr/local/share/service/bincimap to /service/imap. + b) Create a symlink from /usr/local/share/service/bincimaps to /service/imaps. + +The server should be available immediately. + +Happy IMAPing! With these settings your copy of Binc IMAP should be +operational. For more information, please check out the man pages and +FAQ. + Andy :-) + +========================================================================= +Tell us what you think about this server! Post any problems, remarks +or comments to: + +The Binc IMAP mailing list +The Binc IMAP Developers' mailing list + +Author: Andreas Aardal Hanssen diff --git a/doc/OLD/README.SSL b/doc/OLD/README.SSL new file mode 100644 index 0000000..3048a65 --- /dev/null +++ b/doc/OLD/README.SSL @@ -0,0 +1,141 @@ +This documentation is free software; you can redistribute it and/or +modify it under the terms of the GNU General Public License as +published by the Free Software Foundation; either version 2 of the +License, or (at your option) any later version. + +You should have received a copy of the GNU General Public License +along with this program; if not, write to the Free Software +Foundation, Inc., 59 Temple Street #330, Boston, MA 02111-1307, USA. + +========================================================================= + +Quick guide to SSL certificates with Binc IMAP. + +Table of contents: + +0. Introduction +1. To generate a private key and certificate request +2. To generate a private key and self-signed certificate +3. To generate a private key and CA signed certificate, acting as + one's own CA. + +For more information, check out the project home page's FAQ and +the Life With Binc IMAP community documentation site: + +http://www.lifewithbincimap.org/ + +========================================================================= + +0. Introduction +--------------- + +The are two ways to enable SSL on Binc IMAP. One is to use an SSL +tunnel (http://www.stunnel.org/), the other is to use Binc IMAP's +native SSL support. If you compiled Binc with SSL support, the latter +is much easier to set up. + +To use SSL with Binc IMAP, you need a private key and a certificate. + +A private key is a random string of bits that is secret to your host. +If this key is compromised, your SSL server will no longer provide +significant security for your users. + +The certificate is among the first things the server sends to a +client. The client uses this certificate to make certain that it is +communicating with the correct host. To do this, it needs to check the +certificate with a trusted third party certificate, known as a CA +certificate. + +There are in general two types of certificates: + +- CA signed certificates +- Self signed certificates + +CAs, or Certificate Authorities, are used by clients to verify the +authenticity of a certificate. If you want an official CA to verify +your certificate, you need to send a "certificate request". Usually +for a certain price, a signed certificate is returned to you. If you +do not wish to use an official CA, you can act as your own CA and +create your own CA signed certificates. + +A certificate is not valid unless it is signed. If it is self signed, +the clients can not verify its identity. In that sense, a self signed +certificate is only useful in a test environment. The client can not +identify the server if the server uses a self-signed certificate. + +The general idea is: + +* If you are testing an SSL enabled server, generate a self-signed +test certificate. + +* If you want to provide an SSL enabled service on a closed network, +create a CA certificate and a signed host certificate, then install +the CA certificate on all clients on the network. + +* If you want to provide an SSL enabled service on an open network +such as the Internet, use an official CA to sign your certificate. + +1. To generate a private key and certificate request +---------------------------------------------------- + +Quick hit: "make cert". + +To generate a private key and a certificate request, the following +openssl command can be used: + +openssl req -newkey rsa:1024 -keyout bincimap.key -nodes -days 365 -out bincimap.crq + +Inside bincimap.crq is a certificate request in PEM encoding, which +basically means the certificate is base64 encoded and enclosed in a +start string that says "BEGIN CERTIFICATE REQUEST" and an end string +that says "END CERTIFICATE REQUEST". + +Submit this request file to a CA such as Thawte (http://www.thawte.com/) or +Verisign (http://www.verisign.com/). When you receive the signed certificate +from them, store this in a file called bincimap.cert. + +The file contains the PEM encoded certificate, and it is enclosed in +a start string that says "BEGIN CERTIFICATE" and an end string that +says "END CERTIFICATE". + +Then edit bincimap-config and set the full filename and path to your +certificate file and your private key file. + +You're now ready to use Binc IMAP with SSL. + +2. To generate a private key and self-signed certificate +-------------------------------------------------------- + +Quick hit: "make testcert". + +To generate a private key and a self-signed certificate, the following +openssl command can be used: + +openssl req -newkey rsa:1024 -keyout bincimap.key -x509 -nodes -days 365 -out bincimap.cert + +Then edit bincimap-config and set the full filename and path to your +certificate file and your private key file. + +You're now ready to test Binc IMAP with SSL. + +3. To generate a private key and CA signed certificate, acting as + one's own CA. +------------------------------------------------------------------ + +Look up the guides on LifeWithBincIMAP.org: + +http://lifewithbincimap.org/index.php/Main/DoItYourselfCertificateAuthority +http://lifewithbincimap.org/index.php/Main/SettingUpYourOwnSSLCertificationAuthority + +You're now ready to use Binc IMAP with SSL. + +Happy IMAPing! + Andy :-) + +========================================================================= +Tell us what you think about this server! Post any problems, remarks +or comments to: + +The Binc IMAP mailing list + +Author: Andreas Aardal Hanssen -- cgit v1.2.3