Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Jun 2004 14:42:55 -0700
From:      Mike Hogsett <hogsett@csl.sri.com>
To:        questions@freebsd.org
Cc:        hogsett@csl.sri.com
Subject:   Mail Server
Message-ID:  <200406302142.i5ULgtfF025128@beast.csl.sri.com>

next in thread | raw e-mail | index | archive | help

I am about to begin the process of building a replacement mail server
for our workgroup using FreeBSD and Sendmail.

In addition to receiving mail from our primary MX and sending mail out
our SMART_HOST, I would like the ability to enable our users to send and
receive email directly from this server while at remote locations.

My initial thought along the above lines is to enable smtps and/or
SSL/TLS for sendmail, and the imap-uw port for imaps/pops.

I have read section 21.10 in the FreeBSD handbook, but this only covers
SMTP Authentication.

I have also found and read
http://www.puresimplicity.net/~hemi/freebsd/sendmail.html and it appears
to cover most of what I need to do.

Additionally I want to integrate SpamAssassin into the mix.  I have
found, read, and implemented the SpamAssassin Milter instructions at
http://networking.ringofsaturn.com/Unix/spamassassin.php This appears to
work well.  Does anyone have any arguments about why I should do it this
way rather than the "invoke spamc via procmail" method we use now?

Lastly, this may seem silly, but how do I generate a certificate signing
request for my imaps/pops/sendmail servers?  I have generated a self
signed certificate and I can accept it and it appears to be working.
When I look at information regarding certificates at either Verisign or
Thawte I have only found information about web server certificates.  Is
there any effective difference between a cert used for Apache and
imaps/pops/sendmail?

If anyone has suggestions, experiences, or pointers to more information
I would greatly appreciate it.

Thanks,

 - Michael Hogsett



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406302142.i5ULgtfF025128>