<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>DKIM signing of outgoing mails</title> 
  <pubDate>Fri, 10 Apr 2026 07:03:43 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/8690</link> 
  <atom:link rel="self" type="application/rss+xml" title="DKIM signing of outgoing mails" href="https://bugs.horde.org/ticket/8690/rss" /> 
  <description>DKIM signing of outgoing mails</description> 
 
   
   
  <item> 
   <title>like signing messages with pgp / smime it would be nice to a</title> 
   <description>like signing messages with pgp / smime it would be nice to also sign messages with dkim

sample implementation for dkim can be found here:
http://php-dkim.sourceforge.net/</description> 
   <pubDate>Tue, 10 Nov 2009 09:03:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8690#t56615</link> 
  </item> 
   
  <item> 
   <title>Isn&#039;t this better done at the MTA level (i.e. hooking into t</title> 
   <description>Isn&#039;t this better done at the MTA level (i.e. hooking into the SMTP server and/or sendmail)?</description> 
   <pubDate>Tue, 10 Nov 2009 18:24:13 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8690#t56648</link> 
  </item> 
   
  <item> 
   <title>And to answer my own question... this *is* something that sh</title> 
   <description>And to answer my own question... this *is* something that should be done at the MTA level.  First, DKIM will never be a drop-in configuration option - it requires access to the organization&#039;s DNS servers for example.  Second, signing outgoing mails is arguably less important than verifying incoming mails.  And verifying is most certainly best done at the MTA level.</description> 
   <pubDate>Fri, 13 Nov 2009 18:58:38 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8690#t56731</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
