<?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>Check email address for event reminders</title> 
  <pubDate>Thu, 09 Apr 2026 14:30:22 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/14247?Horde=6b9c23adb245169c419124379811065f</link> 
  <atom:link rel="self" type="application/rss+xml" title="Check email address for event reminders" href="https://bugs.horde.org/ticket/14247/rss?Horde=6b9c23adb245169c419124379811065f" /> 
  <description>Check email address for event reminders</description> 
 
   
   
  <item> 
   <title>When chosing to have an email remindet sent for an event, th</title> 
   <description>When chosing to have an email remindet sent for an event, the email address that a user enters into the form is not checked.  If the input is in fact not a valid email address (e.g. just the username with no domain), this leads to problems at the time the reminders are to be sent, with the site administrator receiving emails from the cronjob running horde-alarms. The invalid input should be caught at the time the user fills out the form so that they can enter a valid email address instead.

I see two ways in which the form used for entering an email address for reminders to an event could be improved:

(1) Append the default domain to unqualified addresses just like IMP does. This may be a bit difficult to do since the domains that would need to be appended are only set in IMP&#039;s backends.local.php, so that info might not be available to Kronolith. Maybe the form should be re-displayed in this case with a note to the user to make clear that the email address has been changed automatically.

(2) Do at least some basic checking of user input, i.e. validate that it is a syntactically correct email address.  For instance, an input such as &quot;a@b@c&quot; should never be accepted.</description> 
   <pubDate>Tue, 09 Feb 2016 15:19:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/14247#t89877</link> 
  </item> 
   
  <item> 
   <title>&gt; (1) Append the default domain to unqualified addresses jus</title> 
   <description>&gt; (1) Append the default domain to unqualified addresses just like IMP 
&gt; does. This may be a bit difficult to do since the domains that would 
&gt; need to be appended are only set in IMP&#039;s backends.local.php, so that 
&gt; info might not be available to Kronolith. Maybe the form should be 
&gt; re-displayed in this case with a note to the user to make clear that 
&gt; the email address has been changed automatically.

Not an option, because of the reasons that you mentioned.

&gt; (2) Do at least some basic checking of user input, i.e. validate that 
&gt; it is a syntactically correct email address.  For instance, an input 
&gt; such as &quot;a@b@c&quot; should never be accepted.

No reason to do just basic checking. The only question is whether to use Horde_Mail_Rfc822#parseAddressList() or Horde_Form_Type_email#validateEmailAddress() with optional SMTP server checking.</description> 
   <pubDate>Fri, 12 Feb 2016 11:01:59 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/14247#t89924</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt; (1) Append the default domain to unqualified addresses ju</title> 
   <description>&gt;&gt; (1) Append the default domain to unqualified addresses just like IMP
&gt;&gt; does. This may be a bit difficult to do since the domains that would
&gt;&gt; need to be appended are only set in IMP&#039;s backends.local.php, so that
&gt;&gt; info might not be available to Kronolith. Maybe the form should be
&gt;&gt; re-displayed in this case with a note to the user to make clear that
&gt;&gt; the email address has been changed automatically.

&gt; Not an option, because of the reasons that you mentioned.

OK, so an entry in the email address field that is lacking a domain name would just be a special case of the general &quot;this email address is invalid&quot; scheme then.
</description> 
   <pubDate>Fri, 12 Feb 2016 15:47:47 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/14247#t89939</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
