Re: mailfront on IPv6

--MPkR1dXiUZqK+927
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 29, 2011 at 02:02:40AM -0400, Scott Gifford wrote:
> My original patch also adds this support to pop3front and imapfront.  I
> assumed they provided a similar plugin mechanism to smtpfront, but maybe
> not?

No, there are no plugins for pop3front or imapfront, and they don't make
sense for that neither since the existing plugin architecture only
handles accepting messages.

Incidentally, handling TLS in-process for the latter two is particularly
problematic, as they end up exec'ing a child process after
authentication.  Either the parent would need to hang around handling
the SSL/TLS translation (thus negating the value of in-process
translation), or all the information about the translation would need to
be handed off to the child so it could continue uninterrupted.

> The ability to add EHLO capabilities and new verbs?  I personally probably
> wouldn't use it for anything else, but to speculate on some possible uses:
>=20
>    - Some existing mailfront features could be implemented as plugins whi=
ch
>    add a new capability and verb, in particular SMTP authentication

Ok, you've convinced me.  Now the question is whether to add it to the
existing plugin framework, or add a new one just for protocol
manipulation.  Is it of any use to add this facility to the pop3front or
imapfront?

--=20
Bruce Guenter <[email protected]>                http://untroubled.org/

--MPkR1dXiUZqK+927
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk4LmOMACgkQ6W+y3GmZgOhG6ACcCUVVj9t2AKzePDlQDmBGn75q
OVAAn0giBZT1xqUB0zZAgLftpKZj+XkP
=80SX
-----END PGP SIGNATURE-----

--MPkR1dXiUZqK+927--