Date: Thu, 02 Sep 2004 16:47:47 -0400 From: Forrest Aldrich <forrie@forrie.com> To: Vivek Khera <vivek@khera.org> Cc: ports@freebsd.org Subject: Re: Postfix (current and release) issues... Message-ID: <413786F3.3030006@forrie.com> In-Reply-To: <C545F5F2-FD1F-11D8-8F5B-000A9578CFCC@khera.org> References: <4137822F.4030606@forrie.com> <C545F5F2-FD1F-11D8-8F5B-000A9578CFCC@khera.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Okay, perhaps posting a message to postfix-users will illicit a response ;-) I'm also running into more conflicts on the official release port. Though I'd much prefer to work with -current. ===> Extracting for postfix-2.1.4,1 ===> Vulnerability check disabled >> Checksum OK for postfix/postfix-2.1.4.tar.gz. ===> Patching for postfix-2.1.4,1 echo "<body>See <A HREF="header_checks.5.html">header_checks.5.html</A></BODY>" > /usr/ports/mail/postfix/work/postfix-2.1.4/html/body_checks.5.html ===> Applying extra patch /usr/ports/mail/postfix/work/pfixtls-0.8.18-2.1.3-0.9.7d/pfixtls.diff ===> Applying FreeBSD patches for postfix-2.1.4,1 File to patch: Vivek Khera wrote: > > On Sep 2, 2004, at 4:27 PM, Forrest Aldrich wrote: > >> The port for the official release of postfix is failing the patches >> (reported to maintainer, awaiting a response). Does anyone have a >> clean patch for this or did I hit a bug. >> > > The SPF patch and the TLS patches conflict. Nobody has stepped up to > provide versions that play together well, like the IPv6+TLS combo patch.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?413786F3.3030006>