[Tickets #8837] Re: invalid email address

bugs at horde.org bugs at horde.org
Fri Jan 29 11:06:37 UTC 2010


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8837
------------------------------------------------------------------------------
  Ticket             | 8837
  Updated By         | rsalmon at mbpgroup.com
  Summary            | invalid email address
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
+New Attachment     | email.eml
------------------------------------------------------------------------------


rsalmon at mbpgroup.com (2010-01-29 06:06) wrote:

> This still doesn't make any sense. Any message sent via IMP *must*  
> have the charset set on the body - this is done in  
> IMP_Compose::_createMimeMessage().  That's the only reason $charset  
> would be empty inside of Horde_Mime_Part when the message is created.
>
> Could you possibly add some debugging statements at the top of  
> IMP_Compose::_createMimeMessage() to see if $charset is empty there?

The body is fine. The issue is with the header.

using default prefs and config options;
when buildAndSendMessage is called, $charset is set to 'ISO-8859-1'

I've attached the full email sent. In the header, field 'To', if I  
replace 'utf-8' with 'iso-8859-1', email is display fine. So the  
header is encoded just fine, like the body. I just can't find out  
where the 'utf-8' is coming from!










More information about the bugs mailing list