On 15/03/2008, mufurcz <[EMAIL PROTECTED]> wrote: > > Greetings, > > I need to configure a very simple mail-server (behind firewall), for a > small company: > > a) with less than thirty people (permanent and casual); > b) with no need to access e-mail from outside/home; > c) mail client - some people prefer Outlook, some Thunderbird; > d) no need for virtual mailbox domain(s) (ergo sql database, ldap, etc); > e) the company has no internal DNS server (ergo MX records); > f) has a permanent ADSL connection to an ISP; > d) the domain name management had been delegated to the ISP. > > I am thinking of using the combination of Postfix (as MTA), Courier > maildrop > (to create mail-directories), and Courier-IMAP (for local mail-delivery). > > I am not a seasoned mail administrator, my only experience of handling > mail > comes from managing a Novell's GroupWise (Linux) server running on SLES > 10. >
i prefer dovecot & postfix as a simple combination. there are plenty of howto's around for these 2 on openbsd. sendmail will also do all that you need & the setup is also covered around on the net. IMHO if you're not experienced with email then sendmail can be a bit intimidating at the beginning. my 0.02c, is that for this sort of environment you are better off getting google or an ISP to host the whole lot probably... they should be able to create/delete email accts as needed. if you have to do this on an internal server, you are missing one thing: h) regular backups & tested restores in my experience the smaller the group the less likely they are to change do backups etc etc etc. you might be able to use something like p5-Brackup from CPAN which I've used at home successfully but IIRC the permissions are not backed up. in your env this is probably not an issue. (b) is almost 100% certain that they'll want to change at some point. I'd set up an internal DNS server on the mail server anyway as its a piece of cake & is likely to keep things simple. get your firewall to block outgoing dns & smtp from your good luck. a+ Dave
