<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Les Mikesell wrote:
<blockquote cite="mid1146759133.17312.37.camel@moola.futuresource.com"
type="cite">
<pre wrap="">On Thu, 2006-05-04 at 11:05, Marc Perkel wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'm advocating for a change in the IMAP specification to allow outgoing
email to be sent over the same connection as incoming rather that having
to separately configure outgoing SMTP email. There are two significant
advantages to this concept.
1) It would greatly simplify setup for clients as they would only have
to configure one connection rather than two.
</pre>
</blockquote>
<pre wrap=""><!---->
Why would it be easier for a client to add a new sending method
than to simply have an option to use the same credentials for
smtp auth for sending.
</pre>
</blockquote>
But - if it were part of IMAP then half of the setup goes away.
Outgoing email configuration goes away.<br>
<blockquote cite="mid1146759133.17312.37.camel@moola.futuresource.com"
type="cite">
<pre wrap=""> </pre>
<blockquote type="cite">
<pre wrap="">2) Spam reduction by authentication. The sending of email over the same
connection tells the server that the person who is the sender of the
email also has demonstrated they have access to read the account. This
would be a powerful whitelisting criteria for eliminating fake senders.
</pre>
</blockquote>
<pre wrap=""><!---->
Smtp auth already handles this.
</pre>
</blockquote>
But - the incoming server and outgoing server can be and usually are
different. I can send email spoofing anyone. But if I send through IMAP
I would be showing the server that the person sending the email has
access to read the email. This would be powerful as an authentication
mechanism. With authenticated SMTP all you are says to the world is
that you have some account somewhere that will accept your email, but
not that you can read it. See the difference?<br>
<blockquote cite="mid1146759133.17312.37.camel@moola.futuresource.com"
type="cite">
<pre wrap=""> </pre>
<blockquote type="cite">
<pre wrap="">So - my question. It seems that it would be easy to do this if there
were a standard. Dovecot would merely hand incoming email off to the
outgoing SMTP server. Besides the difficulty of getting a standard
created, am I right on my assumptions?
</pre>
</blockquote>
<pre wrap=""><!---->
Most current MUA's already handle smtp authentication and
ssl. Why make things worse with yet another standard?
</pre>
</blockquote>
Not making things worse with another standard, just convenient and it
has the ability to demonstrate that the email came for the connection
that read the email. Is simplification and identity verification.<br>
</body>
</html>