<?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>Log identity</title> 
  <pubDate>Fri, 10 Apr 2026 16:31:15 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/12792</link> 
  <atom:link rel="self" type="application/rss+xml" title="Log identity" href="https://bugs.horde.org/ticket/12792/rss" /> 
  <description>Log identity</description> 
 
   
   
  <item> 
   <title>Is there a way to log which identity the email account being</title> 
   <description>Is there a way to log which identity the email account being used to send out email? Some accounts got compromised and new identities created to perform spamming. The only way to find out was from the horde_prefs table. Reading the log would be faster and more helpful.</description> 
   <pubDate>Thu, 24 Oct 2013 14:08:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12792#t81217</link> 
  </item> 
   
  <item> 
   <title>&gt; Is there a way to log which identity the email account bei</title> 
   <description>&gt; Is there a way to log which identity the email account being used to 
&gt; send out email?

Configure your Mail Transfer Agent (MTA) to only accept messages through SMTP AUTH on port 587. Configure Horde to send messages through that port and use their credentials for SMTP AUTH.

Don&#039;t allow users to setup e-mail addresses without verification that they actually have access to this account. Make sure $conf[user][verify_from_addr] is ticked in Administration-&gt;Horde-&gt;User Capabilities and Constraints.

Your MTA can possibly help too here. For instance, in Postfix there is an option &#039;reject_sender_login_mismatch&#039; which will prevent your users from making up sender addresses. I use the latter, which has the added benefit of being independent from Horde, so it doesn&#039;t matter how users send messages through your server.

&gt; Some accounts got compromised and new identities 
&gt; created to perform spamming.

Limiting the number of messages/recipients can send per hour/day would have limited the impact of compromised accounts. Configure the Administration-&gt;Permissions for IMP and cap both &#039;max_recipients&#039; and &#039;max_timelimit&#039; to a reasonable value.

&gt; The only way to find out was from the 
&gt; horde_prefs table. Reading the log would be faster and more helpful.

Sure.</description> 
   <pubDate>Thu, 24 Oct 2013 17:33:24 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12792#t81218</link> 
  </item> 
   
  <item> 
   <title>Please use the mailing list to ask for support.

http://ww</title> 
   <description>Please use the mailing list to ask for support.

http://www.horde.org/mail/ contains a list of all available mailing lists.</description> 
   <pubDate>Thu, 24 Oct 2013 17:44:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/12792#t81222</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
