Topic awaiting preservation: Linux mail server (Page 1 of 1)

Where I work, we are getting ready to make a Linux mail server. Just wondering what your thoughts on software to use and what you have used that was great and easily configurable and what was just shite.

We are going to be using Slackware (probably 9.2)

Thanks in advance!

Later,

C:\

OK...a little more info maybe?

We have a webhost offsite. The emails go though them and are forwarded to an email account through our ISP. These emails are then filtered through a computer running The Bat!. The Bat! pretty much just filters the emails and puts them in the right folder for that user.

We want to now have a web based email system. So the emails go through the offsite webhost and are then redirected or forwarded to our personal email addresses.

Hope this makes sense because I get myself quite confused on this.

Later,

C:\

Hmmm... Sounds needlessly complex. I'm not sure I follow everything, (Have no clue what The Bat! is either), but I'll take a shot.

Recommendations:

qmail for the MTA
Courier-IMAP for IMAP services
Horde's IMP for webmail access (and with the rest of their stuff you can built a total online replacement for Outhouse.)
Some prefer SquirrelMail for webmail, but personally, I alrady have too many squirrels in my attic.

All work well with SpamAssassin, ClamAV and Mailman. Great thing about Open Source, everybody plays nice together.

Not sure about Slackware support for any of them, but they all work well together under several Linux flavors including most RedHat versions, Mandrake and SuSE, and they run under FreeBSD UNIX as well.

Does that help?

Horde is ok. That's what we provide our clients. SpamAssassin is THE filtering app these days, and we SHOULD be adding it to our hosting servers soon.

Too bad you're going with Linux. A Microsoft Exchange server could provide everything you need. Mailboxes, filtering, web access, PDA/cell access, etc.

I should clarify: The "needlessly complex" comment refers to using an outside server to forward mail to an internal one. This introduces all sorts of opportunities for failure (server, Internet, human) so the far simpler method is to eliminate that middleman.

Once you have your internal mailserver running and tested, just change the domain's MX record in the DNS to point to your mailserver. This lets the web serivces stay with your hosting service, and sends all mail traffic directly to your mailserver with no messy forwarding or external preprocessing to slow things down.

Just make sure you have a secondary MX record in case of connection failure.

Thanks guys.

Bruce, the "needlessly complex" comment is why we are going to do it just as you described. Except we are going to use SquirrelMail. We don't have enough squirrels in our attic As soon as I have everything up and running (which it is well on it's way so far), I will change the MX Record (and being sure to have a back up)

Pugzly...I am not sure why we are not going to use MS Exchange....but....I don't own the place. They had their heart set on using Linux, so that's what we are going to use.

Thanks again. Looks like I'm in for a big endevor here

Later,

C:\

quote:

---

We don't have enough squirrels in our attic

---

I hear tell there's quite an abundance of them over in the East Wing. Good eatin' too!