Tickets :: [#10696] Sendmail driver/message data EOL issue

6.0.0-beta1

7/6/25

Summary	Sendmail driver/message data EOL issue
Queue	Horde Framework Packages
Queue Version	Git master
Type	Bug
State	Resolved
Priority	2. Medium
Owners	slusarz (at) horde (dot) org
Requester	makeri-kutsonu (at) t-online (dot) de
Created	10/31/2011 (4997 days ago)
Due
Updated	11/19/2011 (4978 days ago)
Assigned
Resolved	11/08/2011 (4989 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/19/2011 03:04:45 PM	twilek (at) gmx (dot) de	Comment #14	Reply to this comment
With the new horde_mail in the pear channel things work flawless again! Thanks! [Show Quoted Text - 11 lines][Hide Quoted Text] Ok thank you, I only have the latest Pear packet for Horde_mail. I will wait for the GIT changes in Horde_mail to make it into the Pear channel to keep my system consistently pear upgradeable. I think that patch started the EOL Problems for me. The problems appear with Horde_Mime-1.3.0 and dissapear when reverting to Horde_Mime-1.2.1... Then you didn't upgrade Horde_Mail either. You need the git version of Horde Mail right now.

11/15/2011 09:31:03 AM	twilek (at) gmx (dot) de	Comment #13	Reply to this comment
Ok thank you, I only have the latest Pear packet for Horde_mail. I will wait for the GIT changes in Horde_mail to make it into the Pear channel to keep my system consistently pear upgradeable. I think that patch started the EOL Problems for me. The problems appear with Horde_Mime-1.3.0 and dissapear when reverting to Horde_Mime-1.2.1... Then you didn't upgrade Horde_Mail either. You need the git version of Horde Mail right now.

11/15/2011 06:00:22 AM	Michael Slusarz	Comment #12	Reply to this comment
I think that patch started the EOL Problems for me. The problems appear with Horde_Mime-1.3.0 and dissapear when reverting to Horde_Mime-1.2.1... Then you didn't upgrade Horde_Mail either. You need the git version of Horde Mail right now.

11/14/2011 07:22:01 PM	twilek (at) gmx (dot) de	Comment #11	Reply to this comment
I think that patch started the EOL Problems for me. The problems appear with Horde_Mime-1.3.0 and dissapear when reverting to Horde_Mime-1.2.1... Details in ~~ticket 10734~~: http://bugs.horde.org/ticket/10734 Changes have been made in Git for this ticket: [mms] Always use canonical line endings in sendmail driver (~~Bug #10696~~). 1 files changed, 2 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/665e293401e447aed3fc4e38f7256cba668f104e

11/14/2011 03:34:25 AM	Git Commit	Comment #10	Reply to this comment
Changes have been made in Git for this ticket: [mms] Always use canonical line endings in sendmail driver (~~Bug #10696~~). 1 files changed, 2 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/665e293401e447aed3fc4e38f7256cba668f104e

11/08/2011 08:19:58 AM	Michael Slusarz	Summary ⇒ Sendmail driver/message data EOL issue Assigned to Michael Slusarz

11/08/2011 08:19:17 AM	Michael Slusarz	Comment #9 Version ⇒ Git master Queue ⇒ Horde Framework Packages State ⇒ Resolved Priority ⇒ 2. Medium	Reply to this comment
This was an issue with the sendmail driver. When wrapping headers, we were possibly using a different EOL than the rest of the message - this was confusing sendmail (apparently SMTP is more forgiving). This has been fixed in the Horde_Mime and Horde_Mail packages.

11/08/2011 08:17:18 AM	Git Commit	Comment #8	Reply to this comment
Changes have been made in Git for this ticket: ~~Bug #10696~~: Always make sure canonical EOLs are passed to Mail drivers 1 files changed, 6 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/b8ee7682e1dfee0ff823804df15c97335ea10359

11/08/2011 08:17:15 AM	Git Commit	Comment #7	Reply to this comment
Changes have been made in Git for this ticket: ~~Bug #10696~~: Added 'canonical' parameter to Horde_Mime_Headers#toArray() and Horde_Mime_Headers#toString(). 2 files changed, 25 insertions(+), 15 deletions(-) http://git.horde.org/horde-git/-/commit/1c3203a5309822b61a10b1c8387f80366f772380

11/08/2011 08:17:09 AM	Git Commit	Comment #6	Reply to this comment
Changes have been made in Git for this ticket: ~~Bug #10696~~: Always use canonical line endings in sendmail driver 1 files changed, 1 insertions(+), 8 deletions(-) http://git.horde.org/horde-git/-/commit/b0de01d534967d6981028d712b389aa30ab24280

11/03/2011 10:04:06 AM	makeri-kutsonu (at) t-online (dot) de	Comment #5	Reply to this comment
Hello ! I installed horde at home, and there forwarded eMails look good. I look for difference - and change in Horde Config the "Mailer" If i set it the "mailer-type" to "Use the local sendmail binary", sendmail_path to "/usr/lib/sendmail" and sendmail_args to "-oi" then, the Mails are "corrupted" (sorry for my english) But, if i set the mailter-type to "Use a SMTP server", host to "locahost", then Mails are O.K. --- But i have one Problem : If i forward Mail with attachment as "in Mailtext", then the Attachment from the original Mail dont forwarded - Why ? Is this wanted thus?

11/01/2011 06:42:29 PM	Michael Slusarz	Comment #4	Reply to this comment
You can forward ANY Mail (as attachment - in the actions) - and the recipient see the Mailheader in the Mail. As mentioned, this is most likely because the line endings in the forwarded message are incorrect. I just don't know where those line endings are coming from. Further, CRLF should be handled automatically by Horde_Mime_Part - sure enough, nobody else has reported this error. The next step is to verify the above statement, so we need the message source of one of these forwarded messages that are broken for you.

11/01/2011 09:05:58 AM	makeri-kutsonu (at) t-online (dot) de	Comment #3	Reply to this comment
For some reason it looks like the line endings are doubled in your message/rfc822 attached message. So it is not being properly parsed when receiving. But I am not able to reproduce. It is independ, if the original mail has attachment or not. You can forward ANY Mail (as attachment - in the actions) - and the recipient see the Mailheader in the Mail. And if i forward a Mail with attachment. then the original Attachment is away (see my first post and pics) With this bugs we cant use horde in our company. Please help and fix it. Thanks. Our System is opensuse 11.4, with php 5.3.5 and postfix 2.7.2 (local on horde), but the real mailserver has exim4 under debian 6

11/01/2011 12:49:11 AM	Michael Slusarz	Comment #2 Priority ⇒ 1. Low	Reply to this comment
For some reason it looks like the line endings are doubled in your message/rfc822 attached message. So it is not being properly parsed when receiving. But I am not able to reproduce.

10/31/2011 01:58:58 PM	makeri-kutsonu (at) t-online (dot) de	Comment #1 State ⇒ Unconfirmed New Attachment: mail-attachment-bilder.zip Patch ⇒ No Milestone ⇒ Priority ⇒ 3. High Type ⇒ Bug Summary ⇒ Mailforward Queue ⇒ IMP	Reply to this comment
Hello ! In Mailforward gives some Problems - i attached pics in the zip-file. Comments to the pics : text-file.png : this is the content of the text file, that i send as attachment 001-original-mail.png : i send a Mail with attachment (original Mail) 002-forward-as attachment.png : i forward the Mail with the Option "as attachment" 003-forward-as-text-in-mail.png : i forward the Mail as "Mailtext" - WHERE IS THE ATTACHMENT (the mail-attachment-file.txt) ??? 004-Mail-forwarded-as-attachment.png : this is the mail, that i forwarded as attachment (002-forward-as attachment.png) : WHY IS THE MAILHEADER IN THE MAIL ??? We CANT SEND such Mail to our customers ! 005-Mail-forwarded-as-Mailtext.png : this is the Mail, that i forwarded as mailtext (003-forward-as-text-in-mail.png) : WHERE IS THE ATTACHED FILE (mail-attachment-file.txt)