Postfix as Smarthost
-
Has anyone worked with building their own smarthost? We are looking to build one using Postfix on Linux to handle many servers that need a smarthost to relay on their behalf. I've built many Postfix email systems before but not a dedicated smarthost. Anyone have any guidance? This is all for internal use, not for reselling or anything and it doesn't need to be doing spam filtering or anything like that as it is pure text emails being sent for alerts and such. Very basic. We could use Zimbra but seems way to heavy when we could have a tiny, tiny system just doing Postfix alone.
-
@scottalanmiller Not familiar with either of those.
-
@scottalanmiller i have not, but it does look kind of interesting!
-
We are planning on cloud hosting on IaaS, Rackspace I'm sure. Although that shouldn't be a factor outside of a point of interest. Will be CentOS 6 underneath.
-
why aren't you using O365 to relay your text messages?
-
I'll always have a soft spot in my heart for Zimbra, but I completely understand preferring not to use it for this.
-
@Dashrender said:
why aren't you using O365 to relay your text messages?
O365 is not a relay. It's an end point.
-
@NetworkNerd said:
I'll always have a soft spot in my heart for Zimbra, but I completely understand preferring not to use it for this.
Me too. Although partially because it is built on Postfix. It's just so heavy for this though.
-
@scottalanmiller said:
@Dashrender said:
why aren't you using O365 to relay your text messages?
O365 is not a relay. It's an end point.
If you're sending less than 500 emails per day, it's a relay as well.
-
@Nara said:
@scottalanmiller said:
@Dashrender said:
why aren't you using O365 to relay your text messages?
O365 is not a relay. It's an end point.
If you're sending less than 500 emails per day, it's a relay as well.
can you relay at really small volume? We need much more than that but was not aware that any relay was available.
-
Setting Postfix up as a smarthost's pretty straightforward. I've done it in reverse as an inbound mail gateway instead of using an MS Exchange Edge Transport role. I'm guessing you'd be allowing access based on IP?
While you want to keep it simple, I can't stress strongly enough to use at least outbound spam filtering. That way, in case you do somehow start churning out spam, it'll get caught before your IP gets blacklisted.
