• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

conf/H21-Jul-2005-716504

contrib/H21-Jul-2005-573395

doc/H03-May-2022-1,4511,088

man/H21-Jul-2005-964747

service/H21-Jul-2005-722440

src/H03-May-2022-21,54813,765

AUTHORSH A D15-Jun-20052.4 KiB4738

COPYINGH A D05-Jan-200518.4 KiB357294

COPYING.OpenSSLH A D05-Jan-20056.1 KiB128120

ChangeLogH A D21-Jul-200556.9 KiB1,2381,105

INSTALLH A D14-Jun-20059.1 KiB233177

Makefile.amH A D05-Jan-20052.8 KiB5028

Makefile.inH A D03-May-202213.8 KiB417319

READMEH A D21-Jul-20058.4 KiB229166

README.SSLH A D05-Jan-20055.6 KiB151104

README.inH A D05-Jan-20058.3 KiB229166

TODOH A D05-Jan-200556 32

aclocal.m4H A D21-Jul-200537.1 KiB979938

bincimap.specH A D21-Jul-200561.5 KiB1,4121,207

bincimap.spec.inH A D06-Mar-200561.5 KiB1,4121,243

config.guessH A D25-Aug-200442.2 KiB1,4421,245

config.hH A D21-Jul-20051,001 4013

config.h.inH A D05-Jan-2005832 3924

config.subH A D25-Aug-200430.5 KiB1,5531,412

configureH A D21-Jul-2005142.4 KiB4,7693,931

configure.inH A D21-Jul-20057.4 KiB236198

install-shH A D27-Sep-20036.3 KiB270153

missingH A D27-Sep-20036.3 KiB199159

mkinstalldirsH A D27-Sep-2003722 4123

stamp-h.inH A D21-Jul-200510 21

README

1This documentation is free software; you can redistribute it and/or
2modify it under the terms of the GNU General Public License as
3published by the Free Software Foundation; either version 2 of the
4License, or (at your option) any later version.
5
6You should have received a copy of the GNU General Public License
7along with this program; if not, write to the Free Software
8Foundation, Inc., 59 Temple Street #330, Boston, MA 02111-1307, USA.
9
10=========================================================================
11
12Welcome to Binc IMAP! This is the documentation for v1.2.13final.
13
14Here is a quick guide on how to setup IMAP on your system.
15
16Note that this is not the full documentation for Binc IMAP. You will
17find more about the server by viewing the man pages and reading
18through the bundled documentation under /usr/local/share/doc.
19
20You can also check out the project home page's FAQ and the Life With
21Binc IMAP community documentation site:
22
23http://www.lifewithbincimap.org/
24
25For hints on how to set up different clients with Binc, please visit
26the following page:
27
28http://www.lifewithbincimap.org/index.php/Main/IMAPClientsWithBinc
29
30+=======================================================================+
31|                                                                       |
32|   The following library is required for Binc IMAP to support SSL:     |
33|                                                                       |
34|                 OpenSSL  - http://www.openssl.org/                    |
35|                                                                       |
36+=======================================================================+
37
38For instructions on compiling from the tarball, please scroll down.
39
40If you do not plan to modify the original source code, it will suffice
41to grab one of the precompiled binary RPM packages from:
42
43http://www.bincimap.org/dl/RPMS
44
45NOTE: These are RedHat/SuSe packages. There are packages available for
46Mandrake, Debian and FreeBSD among other distributions. Search for
47"Binc IMAP" or "bincimap" on the respective distributions' web sites
48to learn more.
49
50If you can't find a precompiled binary that matches your system, you
51can grab a source RPM from here:
52
53http://www.bincimap.org/dl/SRPMS
54
55To create RPM packages for your system, you can run the following
56command as root:
57
58rpmbuild --rebuild bincimap-a.b.c-d.src.rpm
59
60At the end of the input, you will see where your binary package has
61been generated. If the rebuild fails, the package is easy to
62build from the tarball.
63
64=========================================================================
65
66Here's how to set up the service when building from the tarball.  Note
67that if you experience any problems in this section, do not hesitate
68to post your problems to the Binc IMAP mailing list.
69
70----------------------
711) Compile the service
72----------------------
73
74./configure
75make
76make install    # Note: You may need to use "sudo make install"
77
78        Add --enable-static to ./configure to build a static binary
79        (a binary that does not depend on the shared libraries on
80        the machine it's built on).
81
82        If you want to place the binaries and configuration files in
83        a different place from what's default, use the --prefix and
84        --sysconfdir arguments to configure.
85
86        To set the location of the log directories (with multilog),
87        set --localstatedir. This will also be the location of the
88	run scripts (daemontools & xinetd).
89
90        If you want smaller binaries, run "make install-strip" instead
91        of "make install".
92
93        To create a self signed SSL certificate, run "make testcert". Read
94        more on SSL certificates in README.SSL.
95
96        "make install" will create the following files:
97
98        /usr/local/bin/bincimap-up
99        /usr/local/bin/bincimapd
100        /usr/local/bin/checkpassword.pl
101        /usr/local/bin/tomaildir++
102        /usr/local/bin/toimapdir
103
104        /usr/local/share/doc/bincimap-manual.dvi
105        /usr/local/share/doc/bincimap-manual.ps
106
107        /usr/local/etc/bincimap.conf
108        /usr/local/etc/xinetd/imap
109        /usr/local/etc/xinetd/imaps
110
111        /usr/local/var/service/imap/run
112        /usr/local/var/service/imap/log/run
113        /usr/local/var/service/imaps/run
114        /usr/local/var/service/imaps/log/run
115
116        /usr/local/var/log/bincimap
117        /usr/local/var/log/bincimap-ssl
118
119--------------------------------
1202) Apply necessary configuration
121--------------------------------
122
123        Edit the destination bincimap.conf file, which by default is
124        installed under /usr/local/etc/bincimap.conf. Check each
125        individual setting.
126
127         * Note the location of your server's SSL PEM-encoded
128           certificate. If you do not have one, you can run "make testcert"
129           to create a test certificate.
130         * Note the default path to users' mail depot, relative to the
131           users' home directories. If the depot directory is ~/Maildir,
132           set path = "Maildir". If the depot is the current directory,
133           set path = ".". Remember that if you're using
134           IMAPdir, the depot needs to have a mailbox called INBOX.
135         * Use the man pages bundled with the distribution, under
136           the man/ directory.
137
138        You can read more about this in the bundled FAQ under the
139        doc/ directory.
140
141        If using daemontools' supervise, tcpserver and multilog,
142        create multilog directores.
143
144mkdir -p /usr/local/var/log/bincimap{,-ssl}
145chown nobody.nobody /usr/local/var/log/bincimap{,-ssl}
146
147        xinetd users will be more familiar with using syslog.
148
149----------------------------
1503) Install the service files
151----------------------------
152
153        With xinetd:
154
155        Edit /usr/local/etc/xinetd/bincimap and
156        /usr/local/etc/xinetd/bincimaps and check that the locations
157        of configuration files and binaries are correct.
158
159        Note the location of your checkpassword authenticator in
160        particular, and use the man pages to find what options you need
161        to pass.
162
163        You may also want to symlink them to /etc/xinetd.d instead
164        of copying the files.
165
166ln -s /usr/local/etc/xinetd/bincimap /etc/xinetd.d/imap
167ln -s /usr/local/etc/xinetd/bincimaps /etc/xinetd.d/imaps
168service xinetd restart
169
170        With daemontools' supervise:
171
172        Edit /usr/local/etc/service/bincimap/run,
173        /usr/local/etc/service/bincimap/log/run,
174        /usr/local/etc/service/bincimaps/run and
175        /usr/local/etc/service/bincimaps/log/run and
176        check that the locations are correct.
177        Note the location of your authenticator in particular.
178
179        Then copy or symlink the service files in place.
180
181ln -s /usr/local/etc/service/bincimap /service/imap
182ln -s /usr/local/etc/service/bincimaps /service/imaps
183
184----------------------------
1854) Securing your service
186----------------------------
187
188        - It's a good thing to not allow users to pass their passwords
189          over a plain text connection. Require that your users enable
190          SSL by setting this option in your Authentication section
191          in bincimap.conf:
192
193            allow plain auth in non ssl = "no"
194
195        - Binc IMAP allows users to retry a login if the password they
196          submit is wrong. To make it harder for malicious users to
197          brute force passwords, Binc IMAP allows you to make it sleep
198          for a certain number of seconds after a failed password. You
199          can set this to 0, for no penalty, but this is a recommended
200          value:
201
202            auth penalty = 4
203
204        - The bincimap-up stub channels input to and output from the
205          main IMAP server. It does this in what we call a "chroot
206          jail". Make sure you set the path to an empty directory on
207          your server, preferable one in which a certain unprivileged
208          user has no rights:
209
210            Security {
211                jail path = "/usr/local/bin",
212                jail user = "nobody",
213                jail group = "nobody"
214            }
215
216Happy IMAPing! With these settings your copy of Binc IMAP should be
217operational.  For more information, please check out the man pages and
218FAQ.
219                                                   Andy :-)
220
221=========================================================================
222Tell us what you think about this server! Post any problems, remarks
223or comments to:
224
225The Binc IMAP mailing list <binc@bincimap.org>
226The Binc IMAP Developers' mailing list <binc-dev@bincimap.org>
227
228Author: Andreas Aardal Hanssen <andreas-binc@bincimap.org>
229

README.SSL

1This documentation is free software; you can redistribute it and/or
2modify it under the terms of the GNU General Public License as
3published by the Free Software Foundation; either version 2 of the
4License, or (at your option) any later version.
5
6You should have received a copy of the GNU General Public License
7along with this program; if not, write to the Free Software
8Foundation, Inc., 59 Temple Street #330, Boston, MA 02111-1307, USA.
9
10=========================================================================
11
12Quick guide to SSL certificates with Binc IMAP.
13
14Table of contents:
15
160. Introduction
171. To generate a private key and certificate request
182. To generate a private key and self-signed certificate
193. To generate a private key and CA signed certificate, acting as
20   one's own CA.
21
22For more information, check out the project home page's FAQ and
23the Life With Binc IMAP community documentation site:
24
25http://www.lifewithbincimap.org/
26
27=========================================================================
28
290. Introduction
30---------------
31
32The are two ways to enable SSL on Binc IMAP. One is to use an SSL
33tunnel (http://www.stunnel.org/), the other is to use Binc IMAP's
34native SSL support. If you compiled Binc with SSL support, the latter
35is much easier to set up.
36
37To use SSL with Binc IMAP, you need a private key and a certificate.
38
39A private key is a random string of bits that is secret to your host.
40If this key is compromised, your SSL server will no longer provide
41significant security for your users.
42
43The certificate is among the first things the server sends to a
44client. The client uses this certificate to make certain that it is
45communicating with the correct host. To do this, it needs to check the
46certificate with a trusted third party certificate, known as a CA
47certificate.
48
49There are in general two types of certificates:
50
51- CA signed certificates
52- Self signed certificates
53
54CAs, or Certificate Authorities, are used by clients to verify the
55authenticity of a certificate. If you want an official CA to verify
56your certificate, you need to send a "certificate request".  Usually
57for a certain price, a signed certificate is returned to you. If you
58do not wish to use an official CA, you can act as your own CA and
59create your own CA signed certificates.
60
61A certificate is not valid unless it is signed. If it is self signed,
62the clients can not verify its identity. In that sense, a self signed
63certificate is only useful in a test environment. The client can not
64identify the server if the server uses a self-signed certificate.
65
66The general idea is:
67
68* If you are testing an SSL enabled server, generate a self-signed
69test certificate.
70
71* If you want to provide an SSL enabled service on a closed network,
72create a CA certificate and a signed host certificate, then install
73the CA certificate on all clients on the network.
74
75* If you want to provide an SSL enabled service on an open network
76such as the Internet, use an official CA to sign your certificate.
77
781. To generate a private key and certificate request
79----------------------------------------------------
80
81Quick hit: "make cert".
82
83To generate a private key and a certificate request, the following
84openssl command can be used:
85
86openssl req -newkey rsa:1024 -keyout bincimap.key -nodes -days 365 -out bincimap.crq
87
88Inside bincimap.crq is a certificate request in PEM encoding, which
89basically means the certificate is base64 encoded and enclosed in a
90start string that says "BEGIN CERTIFICATE REQUEST" and an end string
91that says "END CERTIFICATE REQUEST".
92
93Submit this request file to a CA such as Thawte
94(http://www.thawte.com/) or Verisign (http://www.verisign.com/). When
95you receive the signed certificate from them, store this in a file
96called bincimap.crt.
97
98The file contains the PEM encoded certificate, and it is enclosed in
99a start string that says "BEGIN CERTIFICATE" and an end string that
100says "END CERTIFICATE".
101
102Copy the contents of both these files into a file called
103"bincimap.pem" and place this file at a location that is read-only for
104the bincimap-up process (typically root).
105
106Then edit bincimap.conf, go to the SSL section and set the path of
107this file in the "pem file" option.
108
109You're now ready to use Binc IMAP with SSL.
110
1112. To generate a private key and self-signed certificate
112--------------------------------------------------------
113
114Quick hit: "make testcert".
115
116To generate a private key and a self-signed certificate, the following
117openssl command can be used:
118
119openssl req -newkey rsa:1024 -keyout bincimap.key -x509 -nodes -days 365 -out bincimap.crt
120
121Copy the contents of the generated bincimap.key and bincimap.crt files
122into a file called "bincimap.pem" and place this file at a location
123that is read-only for the bincimap-up process (typically root).
124
125Then edit bincimap.conf, go to the SSL section and set the path of
126this file in the "pem file" option.
127
128You're now ready to test Binc IMAP with SSL.
129
1303. To generate a private key and CA signed certificate, acting as
131   one's own CA.
132------------------------------------------------------------------
133
134Look up the guides on LifeWithBincIMAP.org:
135
136http://lifewithbincimap.org/index.php/Main/DoItYourselfCertificateAuthority
137http://lifewithbincimap.org/index.php/Main/SettingUpYourOwnSSLCertificationAuthority
138
139You're now ready to use Binc IMAP with SSL.
140
141Happy IMAPing!
142                                                   Andy :-)
143
144=========================================================================
145Tell us what you think about this server! Post any problems, remarks
146or comments to:
147
148The Binc IMAP mailing list <lists-bincimap@infeline.org>
149
150Author: Andreas Aardal Hanssen <andreas-binc at bincimap.org>
151

README.in

1This documentation is free software; you can redistribute it and/or
2modify it under the terms of the GNU General Public License as
3published by the Free Software Foundation; either version 2 of the
4License, or (at your option) any later version.
5
6You should have received a copy of the GNU General Public License
7along with this program; if not, write to the Free Software
8Foundation, Inc., 59 Temple Street #330, Boston, MA 02111-1307, USA.
9
10=========================================================================
11
12Welcome to Binc IMAP! This is the documentation for v@VERSION@.
13
14Here is a quick guide on how to setup IMAP on your system.
15
16Note that this is not the full documentation for Binc IMAP. You will
17find more about the server by viewing the man pages and reading
18through the bundled documentation under @datadir@/doc.
19
20You can also check out the project home page's FAQ and the Life With
21Binc IMAP community documentation site:
22
23http://www.lifewithbincimap.org/
24
25For hints on how to set up different clients with Binc, please visit
26the following page:
27
28http://www.lifewithbincimap.org/index.php/Main/IMAPClientsWithBinc
29
30+=======================================================================+
31|                                                                       |
32|   The following library is required for Binc IMAP to support SSL:     |
33|                                                                       |
34|                 OpenSSL  - http://www.openssl.org/                    |
35|                                                                       |
36+=======================================================================+
37
38For instructions on compiling from the tarball, please scroll down.
39
40If you do not plan to modify the original source code, it will suffice
41to grab one of the precompiled binary RPM packages from:
42
43http://www.bincimap.org/dl/RPMS
44
45NOTE: These are RedHat/SuSe packages. There are packages available for
46Mandrake, Debian and FreeBSD among other distributions. Search for
47"Binc IMAP" or "bincimap" on the respective distributions' web sites
48to learn more.
49
50If you can't find a precompiled binary that matches your system, you
51can grab a source RPM from here:
52
53http://www.bincimap.org/dl/SRPMS
54
55To create RPM packages for your system, you can run the following
56command as root:
57
58rpmbuild --rebuild bincimap-a.b.c-d.src.rpm
59
60At the end of the input, you will see where your binary package has
61been generated. If the rebuild fails, the package is easy to
62build from the tarball.
63
64=========================================================================
65
66Here's how to set up the service when building from the tarball.  Note
67that if you experience any problems in this section, do not hesitate
68to post your problems to the Binc IMAP mailing list.
69
70----------------------
711) Compile the service
72----------------------
73
74./configure
75make
76make install    # Note: You may need to use "sudo make install"
77
78        Add --enable-static to ./configure to build a static binary
79        (a binary that does not depend on the shared libraries on
80        the machine it's built on).
81
82        If you want to place the binaries and configuration files in
83        a different place from what's default, use the --prefix and
84        --sysconfdir arguments to configure.
85
86        To set the location of the log directories (with multilog),
87        set --localstatedir. This will also be the location of the
88	run scripts (daemontools & xinetd).
89
90        If you want smaller binaries, run "make install-strip" instead
91        of "make install".
92
93        To create a self signed SSL certificate, run "make testcert". Read
94        more on SSL certificates in README.SSL.
95
96        "make install" will create the following files:
97
98        @bindir@/bincimap-up
99        @bindir@/bincimapd
100        @bindir@/checkpassword.pl
101        @bindir@/tomaildir++
102        @bindir@/toimapdir
103
104        @datadir@/doc/bincimap-manual.dvi
105        @datadir@/doc/bincimap-manual.ps
106
107        @sysconfdir@/bincimap.conf
108        @sysconfdir@/xinetd/imap
109        @sysconfdir@/xinetd/imaps
110
111        @localstatedir@/service/imap/run
112        @localstatedir@/service/imap/log/run
113        @localstatedir@/service/imaps/run
114        @localstatedir@/service/imaps/log/run
115
116        @localstatedir@/log/bincimap
117        @localstatedir@/log/bincimap-ssl
118
119--------------------------------
1202) Apply necessary configuration
121--------------------------------
122
123        Edit the destination bincimap.conf file, which by default is
124        installed under @sysconfdir@/bincimap.conf. Check each
125        individual setting.
126
127         * Note the location of your server's SSL PEM-encoded
128           certificate. If you do not have one, you can run "make testcert"
129           to create a test certificate.
130         * Note the default path to users' mail depot, relative to the
131           users' home directories. If the depot directory is ~/Maildir,
132           set path = "Maildir". If the depot is the current directory,
133           set path = ".". Remember that if you're using
134           IMAPdir, the depot needs to have a mailbox called INBOX.
135         * Use the man pages bundled with the distribution, under
136           the man/ directory.
137
138        You can read more about this in the bundled FAQ under the
139        doc/ directory.
140
141        If using daemontools' supervise, tcpserver and multilog,
142        create multilog directores.
143
144mkdir -p @localstatedir@/log/bincimap{,-ssl}
145chown nobody.nobody @localstatedir@/log/bincimap{,-ssl}
146
147        xinetd users will be more familiar with using syslog.
148
149----------------------------
1503) Install the service files
151----------------------------
152
153        With xinetd:
154
155        Edit @sysconfdir@/xinetd/bincimap and
156        @sysconfdir@/xinetd/bincimaps and check that the locations
157        of configuration files and binaries are correct.
158
159        Note the location of your checkpassword authenticator in
160        particular, and use the man pages to find what options you need
161        to pass.
162
163        You may also want to symlink them to /etc/xinetd.d instead
164        of copying the files.
165
166ln -s @sysconfdir@/xinetd/bincimap /etc/xinetd.d/imap
167ln -s @sysconfdir@/xinetd/bincimaps /etc/xinetd.d/imaps
168service xinetd restart
169
170        With daemontools' supervise:
171
172        Edit @sysconfdir@/service/bincimap/run,
173        @sysconfdir@/service/bincimap/log/run,
174        @sysconfdir@/service/bincimaps/run and
175        @sysconfdir@/service/bincimaps/log/run and
176        check that the locations are correct.
177        Note the location of your authenticator in particular.
178
179        Then copy or symlink the service files in place.
180
181ln -s @sysconfdir@/service/bincimap /service/imap
182ln -s @sysconfdir@/service/bincimaps /service/imaps
183
184----------------------------
1854) Securing your service
186----------------------------
187
188        - It's a good thing to not allow users to pass their passwords
189          over a plain text connection. Require that your users enable
190          SSL by setting this option in your Authentication section
191          in bincimap.conf:
192
193            allow plain auth in non ssl = "no"
194
195        - Binc IMAP allows users to retry a login if the password they
196          submit is wrong. To make it harder for malicious users to
197          brute force passwords, Binc IMAP allows you to make it sleep
198          for a certain number of seconds after a failed password. You
199          can set this to 0, for no penalty, but this is a recommended
200          value:
201
202            auth penalty = 4
203
204        - The bincimap-up stub channels input to and output from the
205          main IMAP server. It does this in what we call a "chroot
206          jail". Make sure you set the path to an empty directory on
207          your server, preferable one in which a certain unprivileged
208          user has no rights:
209
210            Security {
211                jail path = "@bindir@",
212                jail user = "nobody",
213                jail group = "nobody"
214            }
215
216Happy IMAPing! With these settings your copy of Binc IMAP should be
217operational.  For more information, please check out the man pages and
218FAQ.
219                                                   Andy :-)
220
221=========================================================================
222Tell us what you think about this server! Post any problems, remarks
223or comments to:
224
225The Binc IMAP mailing list <binc@bincimap.org>
226The Binc IMAP Developers' mailing list <binc-dev@bincimap.org>
227
228Author: Andreas Aardal Hanssen <andreas-binc@bincimap.org>
229