<?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>Can&#039;t send mails to IDN-domains (umlaut-domains)</title> 
  <pubDate>Fri, 10 Apr 2026 18:27:13 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/5180</link> 
  <atom:link rel="self" type="application/rss+xml" title="Can&#039;t send mails to IDN-domains (umlaut-domains)" href="https://bugs.horde.org/ticket/5180/rss" /> 
  <description>Can&#039;t send mails to IDN-domains (umlaut-domains)</description> 
 
   
   
  <item> 
   <title>It is now possible to register for domains containing umlaut</title> 
   <description>It is now possible to register for domains containing umlauts. Browsers search for these IDN-domains by enconding them in punny-code. Unfortunatelly horde with the module imp can not send emails to those domains.



It would be great to support these domains, e. g. mail@schöne-welt.info



Tank you.

</description> 
   <pubDate>Thu, 29 Mar 2007 12:50:52 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5180#t30774</link> 
  </item> 
   
  <item> 
   <title>This needs to be done before IMP 4.2.  We should use either </title> 
   <description>This needs to be done before IMP 4.2.  We should use either PEAR&#039;s Net_IDNA or PECL&#039;s idn.</description> 
   <pubDate>Fri, 30 Mar 2007 07:51:55 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5180#t30927</link> 
  </item> 
   
  <item> 
   <title>Uh, why? So far this almost only a nice marketing gag, that </title> 
   <description>Uh, why? So far this almost only a nice marketing gag, that noone uses seriously. Not even all DNS servers have been updated to make this work.

It&#039;s a nice to have, but definitely not high priority.</description> 
   <pubDate>Fri, 30 Mar 2007 09:16:56 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5180#t30930</link> 
  </item> 
   
  <item> 
   <title>&gt; It&#039;s a nice to have, but definitely not high priority.

Ok</title> 
   <description>&gt; It&#039;s a nice to have, but definitely not high priority.

Okay. It&#039;s not so important to give it the highes priority.



&gt; Uh, why? So far this almost only a nice marketing gag, that noone 

&gt; uses seriously. Not even all DNS servers have been updated to make 

&gt; this work.

No, that&#039;s not right. DENIC offers umlaut domains. The name resulution still works with current DNS servers as these domain names will be encoded to regular ascii caracters.



I have access to the statistics of a large german webhoster which hosts far over 100.000 domains. At the moment, 2.77 % of the customers have umlaut domains. This value is constantly improving.



The customers want to use the horde webmailer but can not send emails to umlaut domains. Maybe it is not so important to implement this feature with highest priority, but it still a missing and requested feature.



I think it is worth to implement this feature as soon as possible.</description> 
   <pubDate>Fri, 30 Mar 2007 13:07:24 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5180#t30935</link> 
  </item> 
   
  <item> 
   <title>&gt; Uh, why? So far this almost only a nice marketing gag, tha</title> 
   <description>&gt; Uh, why? So far this almost only a nice marketing gag, that noone 

&gt; uses seriously. Not even all DNS servers have been updated to make 

&gt; this work.

&gt; It&#039;s a nice to have, but definitely not high priority.



Well it is an established RFC, and without this support is entirely impossible to send to these e-mail addresses, so I think that makes it an important bug to fix (ex. consider a site running IMP 4.2 4 years from now when everyone is using IDN.)  Whether other tools down the mail chain fail to send these messages is irrelevant.



More important, the fix to make this work was pretty easy.  We just need to make sure before we send a message that we encode.  We can carry around the unencode address at all other times internally.



http://lists.horde.org/archives/cvs/Week-of-Mon-20070326/066469.html



This still leaves the issue of decoding these IDN e-mail addresses for display purposes, but that is a UI enhancement request rather than a bug.</description> 
   <pubDate>Fri, 30 Mar 2007 21:17:34 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5180#t30999</link> 
  </item> 
   
  <item> 
   <title>Michael, since you already committed the send support, is th</title> 
   <description>Michael, since you already committed the send support, is there a reason you changed this to a high priority bug? Can this be resolved now, or should it be converted into a medium priority enhancement for displaying IDN addresses?</description> 
   <pubDate>Fri, 13 Apr 2007 15:10:18 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5180#t31548</link> 
  </item> 
   
  <item> 
   <title>Yes - I thought I had did that before.  Hmmm...



Anyway, t</title> 
   <description>Yes - I thought I had did that before.  Hmmm...



Anyway, this will be a non-trivial thing to implement since it will effect BC - because the obvious place to do this conversion, MIME_Headers, is split between horde and IMP.</description> 
   <pubDate>Mon, 16 Apr 2007 23:11:46 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5180#t31776</link> 
  </item> 
   
  <item> 
   <title>Ticket 5836 will track the display part of this, so I&#039;m reso</title> 
   <description>Ticket 5836 will track the display part of this, so I&#039;m resolving this ticket.</description> 
   <pubDate>Fri, 26 Oct 2007 03:45:40 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5180#t38104</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
