[Tickets #13771] Re: Adding "AUTH: PLAIN" in IMP's Received header

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/13771
------------------------------------------------------------------------------
  Ticket             | 13771
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Adding "AUTH: PLAIN" in IMP's Received header
  Queue              | IMP
  Version            | 6.2.4
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2015-01-03 14:45) wrote:

> Please consider adding somthing like
> (AUTH: PLAIN viktor at worker.szepe.net, SSL: TLSv1/SSLv3, 128bits, AES128-SHA)

Why?  Re: the SSL transport parameters - there is no way for PHP to  
know this information since PHP != HTTP server.

> Courier-mta adds this when sending throuhg SMTPS.

AUTH is defined by SMTP.

There is no protocol definition for connecting to the Horde framework.  
  So reporting "AUTH" is simply not semantically correct.

> 1.
> zdkimfilter (only DKIM implementation for Courier-mta) needs an  
> authenticated user to add DKIM signiture

What does this have to do with Horde?

> 2.
> The user is indeed authenticated, logged in to Horde.

Exactly.  So there is NO authentication from browser->Horde.  The  
browser is simply the display window for using Horde.

> 3.
> IMP says "with HTTP" even when https:// is used.

What Jan said - HTTP is the protocol used to connect to the Horde  
server.  There is no such thing as HTTPS as a protocol - it is just  
HTTP with TLS security.