Re: Mail Setup

From: Stuart Sears (stuart_at_sjsears.com)
Date: 09/13/04

  • Next message: Bill Tetens: "Test Only"
    To: For users of Fedora Core releases <fedora-list@redhat.com>
    Date: Sun, 12 Sep 2004 23:34:18 +0100
    
    

    On Sunday 12 September 2004 09:44, Robert Slade wrote:
    > Hi,
    >
    > I've tried goggle and the howtos but all I have managed to do is get
    > confused.
    >
    > What I am trying to do is setup a mail server that can handle up to
    > about 20/25 users, some on my network and some external. Currently most
    > are managed using mercury under W2k, but I would like to setup a
    > dedicated mail server to do the job. The other factors are multiple
    > domains and the need to support Webmail and as the users will be using
    > Windows, a virus checker, spam suppression and I that am new to Fedora/
    > Linux.
    Will this be an FC1 or an FC2 box? (it only affects the software that is
    available)
    >
    > I have had a 'play' with postfix and that looks OK as a MTA, my real
    > problem is what next? There are a number of howtos (and books) covering
    > mail setups but I have not been able to find anything that discusses the
    > relative merits of the different MTUs etc.
    They willl _all_ do what you wish, Your requirements are fairly basic.
    Qmail is probably overkill, particularly as FC1/2 doesn't ship with it.
    FC2 ships with sendmail/postfix/exim, all of which are very capable MTAs.

    > For fear of starting a my MTU is better than yours argument, what is the
    > best setup to support the above and where can I find documentation on
    > how to set it up?
    just for the sake of putting my oar into this thread :-)
    everyone has their favourite way of doing things. I'm waiting for the exim
    crowd to get involved...
    my mailserver does very similar things to your requirements, using

    postfix (using TLS/SASL authentication)
    MailScanner (amavisd alternative which can do some extra cool stuff, like
    stripping html from emails before delivery. Sorry, it's a pet hate of mine.)
    clamav (virus scanner. There are plenty of proprietary solutions as well.)
    spamassassin (does what it says on the tin)
    dovecot imap (only providing imap/ssl, but then that's my preference)
    squirrelmail for webmail access.

    the only downside with postfix is decent documentation. Buy a book. The
    O'Reilly book mentioned earlier is excellent (IMHO).

    >
    > Thanks
    >
    > Rob

    -- 
    Stuart Sears RHCE, RHCX
    --
    Jealousy is all the fun you think they have.
    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Bill Tetens: "Test Only"

    Relevant Pages

    • Re: Mail Setup
      ... > What I am trying to do is setup a mail server that can handle up to ... > dedicated mail server to do the job. ... Postfix is a good MTA and I'm sure it can ... For webmail, try installing squirrelmail. ...
      (Fedora)
    • Mail Setup
      ... I've tried goggle and the howtos but all I have managed to do is get ... What I am trying to do is setup a mail server that can handle up to ... relative merits of the different MTUs etc. ...
      (Fedora)
    • Re: Fedora mail server?
      ... Just remember that different functions of a mail server are ... I would recommend Postfix for SMTP server. ... It's much more secure than Sendmail and easier to setup. ... install Dovecot or Cyrus (but Cyrus is more ...
      (linux.redhat)
    • Re: migrate from postfix to qmail
      ... My experience with Qmail is totally the opposite. ... Setup isn't ... one mail server with postfix-dovecot and i would like to migrate it to ... Postfix for years now and before that I used qmail - when it was new. ...
      (freebsd-questions)
    • Re: Subdomains in W2K3
      ... Please find our setup. ... This software has its own mailhost ... messages arrive they hit our SMTP gateway and a force route within the SMTP ... the same mail server. ...
      (microsoft.public.windows.server.dns)