--On Monday, December 14, 2015 6:03 PM +0000 Viktor Dukhovni
<postfix-us...@dukhovni.org> wrote:
On Mon, Dec 14, 2015 at 09:36:33AM -0800, Quanah Gibson-Mount wrote:
Given nginx's complete disregard for RFC's (*) and unwillingness to
examine or fix issues related to the email proxy portion of their
product (IMAP, POP, SMTP), I'd definitely avoid it. I.e., I would not
recommend nginx as a solution in front of postfix to anyone.
*<https://forum.nginx.org/read.php?29,252772,253147>
I would not characterize lack of a SASL implementation as "complete
disregard for RFCs". SASL is difficult to do right in a non-blocking
manner. I don't recall whether nginx is event-based or threaded,
but if it is the former, I too would be reluctant to do SASL (and
I'd be concerned about thread safety in the Cyrus SASL library and
especially the plugins).
Zimbra has already done this for nginx, and it has been in used in
deployments around the world. The goal was simply to contribute the work
back upstream.
Overall, this is just one of many issues that arise if trying to use nginx
as a proxy for email related bits. On the IMAP side, for example, a lack
of "ID" command support continues to exist, despite it having been sent to
upstream by more than one organization. Zimbra has had to extensively
modify nginx to make it functional for POP/IMAP, and there were a number of
hurdles to overcome to make it functional for SMTP the last time we looked.
At least they did finally take the SSL bits for email we submitted back.
--Quanah
--
Quanah Gibson-Mount
Platform Architect
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
