Re: Mail server security - best practices?
- From: "Steve at fivetrees" <steve@xxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 29 Apr 2006 08:46:38 +0100
<sealinux@xxxxxxxxx> wrote in message
news:1146113618.952386.325750@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The question is, how to divvy up the public services? Right now, the
plan is to run mail and DNS on one machine and web and DNS on the
other. Ideally, I'd like for the incoming mail to not "live" on the
public server but to be delivered to the private one, but that, to me,
defeats the purpose of having public/private servers. The only way I
can think to do it would be to have the private server export the home
directories via NFS so that the email server could deliver the messages
to the user's home directories.
Any ideas?
This might sound a bit round-the-houses, but have you considered:
- Public server picks up the mail
- User's mail client picks up mail from local public server, as if it were
an external POP3 server
- User's mail client uses an IMAP mail store on private machine for
longterm message storage
Works for me ;).
Steve
http://www.fivetrees.com
.
- References:
- Mail server security - best practices?
- From: sealinux
- Mail server security - best practices?
- Prev by Date: Re: openBSD 3.8 firewall using 3com 3C509B nic speed problem
- Next by Date: Re: openBSD 3.8 firewall using 3com 3C509B nic speed problem
- Previous by thread: Re: Mail server security - best practices?
- Next by thread: isakmpd: ESP + AH tunnel in OpenBSD
- Index(es):
Relevant Pages
|