Re: mailfront on IPv6

Scott Gifford <[email protected]> Wed, 29 Jun 2011 02:02:40 -0400
Newsgroups gmane.comp.sysutils.bgware
Message-ID <[email protected]>
--20cf307f32a6987dee04a6d38a91
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jun 29, 2011 at 12:46 AM, Bruce Guenter <[email protected]>wrote:

> On Tue, Jun 28, 2011 at 10:10:13PM -0400, Scott Gifford wrote:
> > I think new verbs and capabilities might be of general interest to plugin
> > developers.
>
> Only for SMTP, since QMQP/QMTP don't have "verbs" or other capabilities,
> which admittedly is probably the only protocol that counts for accepting
> mail.
>

My original patch also adds this support to pop3front and imapfront.  I
assumed they provided a similar plugin mechanism to smtpfront, but maybe
not?

I don't think this answers the original question -- would this
> capability be used by anything other than STARTTLS?
>

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:

   - Support for more obscure SMTP features like ETRN
   - Custom mail communication through custom X-verbs, for example to
   provide some specialized extension between mail servers run by the same
   company, or between a specialized client and server
   - Some existing mailfront features could be implemented as plugins which
   add a new capability and verb, in particular SMTP authentication
   - There could also be alternate implementations of STARTTLS that used the
   same plugin interface, for example if somebody preferred a different TLS
   implementation, or wanted different tradeoffs than the ones in patched
   sslserver (e.g. wanted to start up the TLS processing later in case it
   wasn't used, at the cost of giving up chroot support).

------Scott.

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

On Wed, Jun 29, 2011 at 12:46 AM, Bruce Guenter <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:[email protected]">[email protected]</a>&gt;</span> wrot=
e:<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 Tue, Jun 28, 2011 at 10:10:13PM -0400, Scott Gifford w=
rote:<br>
&gt; I think new verbs and capabilities might be of general interest to plu=
gin<br>
&gt; developers.<br>
<br>
</div>Only for SMTP, since QMQP/QMTP don&#39;t have &quot;verbs&quot; or ot=
her capabilities,<br>
which admittedly is probably the only protocol that counts for accepting<br=
>
mail.<br></blockquote><div><br></div><div>My original patch also adds this =
support to pop3front and imapfront. =A0I assumed they provided a similar pl=
ugin mechanism to smtpfront, but maybe not?</div><div><br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex;">


I don&#39;t think this answers the original question -- would this<br>
capability be used by anything other than STARTTLS?<br></blockquote><div><b=
r></div><div>The ability to add EHLO capabilities and new verbs? =A0I perso=
nally probably wouldn&#39;t use it for anything else, but to speculate on s=
ome possible uses:</div>

<div><ul><li>Support for more obscure SMTP features like ETRN</li><li>Custo=
m mail communication through custom X-verbs, for example to provide some=A0=
specialized=A0extension between mail servers run by the same company, or be=
tween a specialized client and server</li>

<li>Some existing mailfront features could be implemented as plugins which =
add a new capability and verb, in particular SMTP authentication</li><li>Th=
ere could also be alternate implementations of STARTTLS that used the same =
plugin interface, for example if somebody preferred a different TLS impleme=
ntation, or wanted different tradeoffs than the ones in patched sslserver (=
e.g. wanted to start up the TLS processing later in case it wasn&#39;t used=
, at the cost of giving up chroot support).</li>

</ul><div>------Scott.</div></div></div><br>

--20cf307f32a6987dee04a6d38a91--