Thu, 09 Apr 2026 14:41:44 +0000 https://bugs.horde.org/ticket/13771 Adding "AUTH: PLAIN" in IMP's Received header Now IMP's Received lokks like this: Received: from 178-164-130-123.pool.digikabel.hu (178-164-130-123.pool.digikabel.hu [178.164.130.123]) by worker.szepe.net (Horde Framework) with HTTP; Wed, 31 Dec 2014 17:58:16 +0000 Please consider adding somthing like (AUTH: PLAIN viktor@worker.szepe.net, SSL: TLSv1/SSLv3, 128bits, AES128-SHA) Courier-mta adds this when sending throuhg SMTPS. 1. zdkimfilter (only DKIM implementation for Courier-mta) needs an authenticated user to add DKIM signiture 2. The user is indeed authenticated, logged in to Horde. 3. IMP says "with HTTP" even when https:// is used. Thank you very much! Wed, 31 Dec 2014 18:06:36 +0000 https://bugs.horde.org/ticket/13771#t86968 If Courier's MTA already does this, why should Horde add that? HTTP is correct, because it's the protocol, not the security layer. Fri, 02 Jan 2015 16:32:44 +0000 https://bugs.horde.org/ticket/13771#t86976 > If Courier's MTA already does this, why should Horde add that? > HTTP is correct, because it's the protocol, not the security layer. Courier adds the "AUTH:" line only on authenticated SMTP/S. Horde sends email through sendmail or unauthenticated SMTP. In these cases there is no "AUTH:" line in the Received header. It would be very nice to have a config option to add the "AUTH:" line to Horde's Received header. Thank you! Fri, 02 Jan 2015 17:45:41 +0000 https://bugs.horde.org/ticket/13771#t86977 zdkimfilter check this line: (authuserbuf = strstr(p2, "AUTH: ")) != NULL written in C http://www.tana.it/svn/zdkimfilter/trunk/src/zdkimfilter.c Fri, 02 Jan 2015 17:48:53 +0000 https://bugs.horde.org/ticket/13771#t86978 > Please consider adding somthing like > (AUTH: PLAIN viktor@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. Sat, 03 Jan 2015 21:45:07 +0000 https://bugs.horde.org/ticket/13771#t86990 > If Courier's MTA already does this, why should Horde add that? Exactly. Horde needs to connect to Courier's MTA, and this connection needs to be authenticated, so the authentication details will be added to *that* received header. Which is correct (especially since the Horde username != the username of the user authorized to relay mail.) Sat, 03 Jan 2015 21:46:29 +0000 https://bugs.horde.org/ticket/13771#t86991 Thank you for your answers. To keep it short: I'd like to implement DKIM. zdkimfilter adds the DKIM signiture to messages containing "AUTH: " So I need that string in Horde's email also. Horde is set to use plain SMTP only. Should I hack it into Horde's source code? Sun, 04 Jan 2015 11:45:59 +0000 https://bugs.horde.org/ticket/13771#t86993 All you need to do is to configure Horde to use SMTP authentication. Mon, 05 Jan 2015 11:22:20 +0000 https://bugs.horde.org/ticket/13771#t87002