MTA Softwares

[glennda]

I know this may not be most people's here normal line of work but i thought I would ask anyway to see what people think.

 

I'm looking for a Mail Transfer softwares which is either Windows or Linux based but essentially needs to be able to receive email and forward on to lots of multiple servers depending on the domain sent. If possible having a built in AV would be good but not a requirement as it all is scanned at the firewall on the way in.

 

Any Recommendations?

[plasmicsound]

GFI Mail Essentials

Really good at word/phrase content filtering, has several AV filters plugged in from big AV leaders like McAffe Kaspersky etc and easy to set up, runs along side IIS6 MTA

 

We also use Nettica which is based in the states and costs are incredibly cheap for filtering junk.

 

So for us all incoming emails go via Nettica first then to our on site GFI Mailessentials server and then on to Exchange. Outgoing emails go via Exchange to GFI Mail Essentials and then out to the big wide world.

[glennda]

I'm looking for something to use as service provider. I'm purely looking for something to install direct mail to it and then act as a smarthost to relay mail to the end users exchange boxs.

 

 

EDIT: should say we currently use MailMarshall

Edited October 17, 2012 by glennda

[Geoff]

Linux box running postfix. I have 5 such machines handling several million emails/day (each). Qmail is out of date and slow, Exim is more suited to a user facing system where you need to do stuff based on rules (think Exchange/Outlook mail filters) or aliases, Sendmail is just a complete pita to configure. Edited October 17, 2012 by Geoff

[glennda]

Linux box running postfix. I have 5 such machines handling several million emails/day (each).

 

How easy is to to setup for say

 

domain xyz.co.uk -> xx.xx.xx.xx

domain qwe.com -> yy.yy.yy.yy

 

I have around 40 domains to relay for.

[Geoff]

In the main.cf you need to add a list of the domains in the 'relay_domains' section so your MTA will accept mail (If this list gets to be long, turn it into a lookup table with postmap).

 

relay_domains=example.com

 

Then you need to route based on the domain of the receiver, this is done in the 'transport' file, in the relay_transport section. So you'd list each domain like this:

 

example.com      :[gateway.example.com]
.example.com     :[gateway.example.com]

 

The square brackets are important, they stop routing loops by preventing MX lookups for when your mail server is the primary MX for the domain (it deliver the mail to itself otherwise).

 

Once you have the above setup you can consider doing virus scanning or whatever. I would be wary of doing it on a Primary/Backup MX mail server though for performance reasons.

Edited October 17, 2012 by Geoff

[CyberNerd]

^ we used to do precisely this in the olden days of exchange and zimbra.

Student email would relay to zimbra and staff to exchange. We used the relay for this purpose and for virus/spam scanning.

We used Postfix (and MailScanner) as Geoff suggested

[glennda]

Cheers guys - just setting up a VM now.

[Geoff]

Oh, pro-tip for high performance MX servers. Use SSDs for the mail spool.

[glennda]

Thanks fellas - After playing with Postfix and fiddling around we came across start [Mailcleaner] - which is debian based and I've got that setup including ClamAV/ClamSpam in around 15 mins. Its now relaying mail for us.

 

Thanks Fellas

[twin--turbo]

ClearOS 5.2

 

Does the job, Easy to use.

 

Rob