> On Feb 5, 2018, at 10:40 AM, Andris Reinman <andris.rein...@gmail.com> wrote:
> 
> Hi,
> 
> As the thread covers some open source MTAs then I'd like to mention our MTA 
> as well – ZoneMTA https://github.com/zone-eu/zone-mta
> 
> ZoneMTA can be deployed in a clustered setup (queue is stored in replicated 
> MongoDB), it is able to handle blacklisting (if blacklisting is detected, 
> then the current IP is disabled for that host for some period and other IPs 
> are used), and has been running on production for over a year for us 
> delivering ~100 msg/sec (single server) on peak times of the day.
> 
> It also has built-in support for Prometheus monitoring 
> https://github.com/zone-eu/zone-mta#metrics-for-prometheus

Looks like a very nice feature set, but the trailing end of the README would 
make me worry about what patents it's violating.

Cheers,
  Steve

> 
> Regards,
> Andris Reinman
> ZoneMTA
> 
> 2018-02-05 20:03 GMT+02:00 Steve Atkins <st...@blighty.com>:
> 
> > On Feb 5, 2018, at 9:27 AM, Marc Goldman via mailop <mailop@mailop.org> 
> > wrote:
> >
> >
> > I agree with sticking to facts so lets cover a few here:
> >
> > 1. PMTA (formerly Port25 now Message Systems) is the 800 lb gorilla in the 
> > MTA world.
> >
> > 2. I own 2 enterprise licenses for PMTA 4.0 and paid support for a number 
> > of years (up to r11). I found the support to be very helpful at first but 
> > over the years it produced diminishing returns and more and more I felt 
> > deferred to the forum and to our own engineers to sort out issues and 
> > uncover abilities so I stopped paying for support and subsequently was 
> > unable to receive new releases including the major one to 4.5
> >
> > 3. Recently (about a year after Message Systems purchased) I reached out to 
> > the team to find out how I can begin paying for software updates again so I 
> > could upgrade to 4.5.
> >
> > I received an email telling me I would need to pay RETROACTIVELY for the 
> > years I did NOT receive support in order to upgrade.
> >
> > Has anyone ever heard of a policy like that?
> 
> Yes, it's pretty much normal. It dissuades people from only paying for 
> support every few years when they need support or want an updated version, 
> while not paying the ongoing fees that pay for development of that updated 
> version.
> 
> >
> > Regardless, it made me not the slightest bit interested in continuing with 
> > PMTA again.
> >
> > We also have multiple Green Arrow installs. It is a great MTA and the 
> > support is excellent and I find their pricing model is really quite fair.
> >
> > With that said, it isn’t perfect. They control the Postgres DB and only 
> > grant read access. Their API however is robust and allows you to do pretty 
> > much whatever you need.
> >
> > We have used a few open source MTAs over the years including Qmail, 
> > Postfix, Haraka and recently dabbling in Postal.
> >
> > We have considered building our own MTA but the costs and time involved 
> > make it somewhat prohibitive.
> >
> > However, I can definitely say that having ones own MTA solves all the 
> > issues mentioned herein and until one makes that step (or invests heavily 
> > in a team and technologies to manage Open Source MTAs), the 3rd parties 
> > will retain a strong position that holds many of us hostage in a sense and 
> > does not satisfy each ESPs individual needs.
> 
> None of the open source MTAs seem to offer anywhere near the tuning, 
> configurability and monitoring that's really needed to run a modern ESP. Not 
> surprising, large ESPs aren't a huge market and large ESPs that aren't 
> already committed to one or the other of the commercial product lines are an 
> even smaller one.
> 
> As spam filters get more selective, especially about grey mail, the need for 
> high quality infrastructure (and staff!) is moving down to the smaller end of 
> the market too, but I doubt that's enough of an organized revenue source to 
> drive developing ESP-grade instrumentation for, e.g., Haraka, any time soon.
> 
> Cheers,
>   Steve
> 
> 
> _______________________________________________
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> 


_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Reply via email to