<?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>Privacy Extensions</title> 
  <pubDate>Fri, 10 Apr 2026 16:31:15 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/8182</link> 
  <atom:link rel="self" type="application/rss+xml" title="Privacy Extensions" href="https://bugs.horde.org/ticket/8182/rss" /> 
  <description>Privacy Extensions</description> 
 
   
   
  <item> 
   <title>Hi,

it would be great if there would be an option to overri</title> 
   <description>Hi,

it would be great if there would be an option to override (or block) the agent header in outgoing mails. Furthermore an option to hide the first &quot;Received&quot; header should also increase privacy. I think these options should be configurable though admin interface, because I think some admins may not want to hide those informations.



The following little hack shoud do the work, but is not as advanced as described above:

File: /user/share/horde3/imp/lib/MIME/Headers.php

After line: &quot;class IMP_Headers extends MIME_Headers {&quot;

Add this: &quot;function addReceivedHeader() { } function addAgentHeader() { }&quot;</description> 
   <pubDate>Sun, 12 Apr 2009 10:51:30 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8182#t53621</link> 
  </item> 
   
  <item> 
   <title>There are no significant privacy ramifications in the User-A</title> 
   <description>There are no significant privacy ramifications in the User-Agent header.  And removing Received headers is a BAD IDEA.  Both of these make tracking abusive e-mails *more* difficult.



If an admin wants to block (not recommended), they can edit the code as the like.  But this is not something that will (or should) be made available via an admin interface.</description> 
   <pubDate>Thu, 16 Apr 2009 20:04:15 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8182#t53672</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
