Re: mailfront on IPv6

--20cf307f363a45fbca04a6d04b18
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 28, 2011 at 9:14 PM, Bruce Guenter <[email protected]> wrote:

> On Wed, Jun 22, 2011 at 10:39:10PM -0400, Scott Gifford wrote:
> > I have a version of my ucspitls patch for mailfront 0.96, and will
> probably
> > update it for the newer version sometime soon.  It doesn't fit neatly
> into
> > the plugin architecture, but is still fairly clean.  See:
> >
> > http://www.suspectclass.com/sgifford/ucspi-tls/
>
>
> >  It would definitely be interesting to extend the plugin architecture to
> > allow this as a pure plugin.
>
> I would be interested too, with two large caveats:
>
> 1. While it would be technically possible to graft the functionality
> into the existing system, I don't see why any plugin would have both an
> front-end I/O filter and an internal data handler.

2. Is there any call for more front-end protocol filtering other than
> TLS?  Would this plugin interface be used by anything other than
> STARTTLS?
>

So the functionality required to support the ucspi-tls patch is adding new
verbs (STARTTLS/STLS) and capabilities (CAPABILITIES/EHLO/CAPA responses) to
the IMAP, POP, and SMTP.  All of the I/O filtering is done by manipulating
file descriptors, which is reasonably portable since these programs run
under the UCSPI interface, which defines which FDs are used for
communication over the network.

I think new verbs and capabilities might be of general interest to plugin
developers.

-----Scott.

--20cf307f363a45fbca04a6d04b18
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 28, 2011 at 9:14 PM, Bruce Guenter <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:[email protected]">[email protected]</a>&gt;</span> wrote=
:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">On Wed, Jun 22, 2011 at 10:39:10PM -0400, Scott Gifford w=
rote:<br>
&gt; I have a version of my ucspitls patch for mailfront 0.96, and will pro=
bably<br>
&gt; update it for the newer version sometime soon. =A0It doesn&#39;t fit n=
eatly into<br>
&gt; the plugin architecture, but is still fairly clean. =A0See:<br>
&gt;<br>
&gt; <a href=3D"http://www.suspectclass.com/sgifford/ucspi-tls/" target=3D"=
_blank">http://www.suspectclass.com/sgifford/ucspi-tls/</a><br>
<br>
<br>
&gt; =A0It would definitely be interesting to extend the plugin architectur=
e to<br>
&gt; allow this as a pure plugin.<br>
<br>
</div>I would be interested too, with two large caveats:<br>
<br>
1. While it would be technically possible to graft the functionality<br>
into the existing system, I don&#39;t see why any plugin would have both an=
<br>
front-end I/O filter and an internal data handler.=A0</blockquote><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex;">
2. Is there any call for more front-end protocol filtering other than<br>
TLS? =A0Would this plugin interface be used by anything other than<br>
STARTTLS?<br></blockquote><div><br></div><div>So the=A0functionality=A0requ=
ired to support the ucspi-tls patch is adding new verbs (STARTTLS/STLS) and=
 capabilities (CAPABILITIES/EHLO/CAPA=A0responses) to the IMAP, POP, and SM=
TP. =A0All of the I/O filtering is done by manipulating file descriptors, w=
hich is reasonably portable since these programs run under the UCSPI interf=
ace, which defines which FDs are used for communication over the network.</=
div>

<div><br></div><div>I think new verbs and capabilities might be of general =
interest to plugin developers.</div><div><br></div><div>-----Scott.</div><d=
iv><br></div></div>

--20cf307f363a45fbca04a6d04b18--