| Version 6 (modified by , 21 years ago) ( diff ) |
|---|
the CAL Mail Server
This server will provide mail accounts for all members of the CAL domain.
it will probably do so by running the postfix MTA, coupled with the cyrus IMAP daemon.
content filtering for spam and viruses will be handled by a combination of mailscanner, clamav, and spamassassin.
We will probably set up several dummy accounts used only for spam harvesting to train spamassassin.
postfix configuration
we'll have astro.columbia.edu set up as a Virtual Mailbox Domain using an alternate delivery mechanism (rather than just dumping into a maildir directly). Until the spam/virus handling is set up, we'll just deliver directly to the cyrus LMTP socket.
We'll also have test.astro.columbia.edu set up to match, to make it simpler to test things.
postfix now pulls the address maps directly from CAL's LDAP, though it took a bit of tweaking to do this. as it turns out, the postfix library which binds to LDAP binds to the OpenLDAP libraries, and those libraries are configured to pull their entropy sources from /dev/random on the default packages in sarge. Of course, this doesn't work properly if the daemon using these libraries is running within a chroot which doesn't have /dev/random. the ldap_table man page implies that setting the tls_random_file option will direct the libraries to use an alternate entropy source. However, this option doesn't work because the openLDAP libraries are configured to expect /dev/random anyway (probably when the URANDOM_DEVICE variable gets set in the configure stage of compilation).
i resolved this problem by creating a new kernel device node within the postfix chroot:
# mknod -m 444 /var/spool/postfix/dev/random c 1 9
(note that this is in fact a pseudo-random device (1,9) instead of a true random device (1,8). i made this decision because i didn't want a depleted entropy pool to shutdown postfix's smtpd lookups.)
cyrus configuration
cyrus is now configured to accept GSSAPI authentication, and the administrative users are */admin, which matches the kerberos domain arrangments.
in order to get postfix to hand off cleanly to cyrus via LMTP, i had to add the postfix user to the mail group on sedna. This was because /var/run/cyrus/socket was owned cyrus:mail, and mode 0750. postfix was unable to descend into the directory to open up /var/run/cyrus/socket/lmtp.
still to do
- cyrus should only allow TLS-based IMAP connections. should we bother with IMAPS?
- postfix needs to allow relaying based on SMTP AUTH (presumably over TLS) -- how would this work if we don't allow krb5 connections from outside the lab?
