Date: Sat, 25 May 2002 10:09:09 -0500 From: "David W. Chapman Jr." <dwcjr@inethouston.net> To: Lucky Green <shamrock@cypherpunks.to> Cc: freebsd-stable@freebsd.org Subject: Re: IPv6 and SSL Message-ID: <20020525150909.GB48227@leviathan.inethouston.net> In-Reply-To: <001901c2039c$6f4e2910$c33a080a@LUCKYVAIO> References: <001901c2039c$6f4e2910$c33a080a@LUCKYVAIO>
next in thread | previous in thread | raw e-mail | index | archive | help
> AFAICT, the conflicts between the postfix TLS patch and IPv6 patch are > not necessarily FreeBSD-specific, but are caused by a conflict between > the generic postfix TLS patch and the IPv6 patch. > > This may be due in part to the fact that the postfix TLS patch itself is > not part of the official postfix release. So we have a port on top of a > patch on top of another patch on top of a base distribution. > > Anybody that finds a fix, or even figures out what the cause of the > problem is, probably should notify the general postfix TLS patch > maintainer at http://www.aet.tu-cottbus.de/personen/jaenicke/pfixtls/ > > --Lucky, who is very much looking forward to being able to use postfix > with both TLS and IPv6, but who is wondering if this discussion even > belongs in freebsd-stable, since postfix is part of the ports collection > and (unfortunately ;) not part of the base FreeBSD release. > This is exactly what I was talking about. If they don't modify the exact same lines, then converting them to context diffs if they aren't already should fix this. -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. <www.inethouston.net> dwcjr@freebsd.org FreeBSD Committer <www.FreeBSD.org> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020525150909.GB48227>