Tickets :: Comment on [#13160] Cannot send email with ActiveSync

* Your Email Address
* Spam protection	Enter the letters below: . ..___..__ .___..__ \|\/\| \| [ __ \| [__) \| \| \| [_./ \| [__)
Comment	>> I am using Horde with an IMAP backend to provide EAS support for an >> existing IMAP+SMTP server. Reading and sending messages work fine >> from the webmail. I can also read messages perfectly from a mobile >> device. Push notifications work too. Unfortunately, sending emails is >> impossible. Sent messages are correctly saved in the sent folder, but >> they are not delivered. >> >> Inspecting the source code of the messages in the sent folder reveals >> errors in the structure of the message. Attached below there is one >> of this messages that are not sent by the SMTP server. >> ---------------------------------------- >> >> From: sender@server.com >> Subject: Test >> Message-Id: <5A958E86-0877-40AC-A78F-7018C9D212BF@gmail.com> >> Date: Sat, 3 May 2014 02:48:18 +0200 >> To: Alberto <receiver@gmail.com> >> User-Agent: Horde Application Framework 5 >> Content-Type: text/plain; charset=us-ascii >> MIME-Version: 1.0 >> >> >> >> MESSAGE CONTENT >> Content-Type: text/plain; >> charset=us-ascii >> Content-Transfer-Encoding: 7bit >> From: sender@server.com >> Mime-Version: 1.0 (1.0) >> Subject: Test >> Message-Id: <5A958E86-0877-40AC-A78F-7018C9D212BF@gmail.com> >> Date: Sat, 3 May 2014 02:48:18 +0200 >> To: Alberto <receiver@gmail.com> >> >> >> >> MESSAGE CONTENT >> >> ------------------ >> >> I believe that the presence of two Form: fields interferes with the >> message sending procedure from the SMTP server. I have no idea why >> the message is structured in this way by the ActiveSync wrapper. >> Messages sent from webmail are fine. > > Not sure where that is coming from. In FRAMEWORK_5_1 we check for the > presence of the From header and only add a new header if it's not > found. See Horde_Core_ActiveSync_Driver::sendMail(). In master > (which currently contains Horde 5.2 code) we actually always remove > the From header and add a new one see the same method as above. > > I can verify that sending email from an EAS client works perfectly > fine here. Check your mail server logs to see why the message was > rejected (or if the message was ever seen by the smtp server at all). > > > >> >> Inspecting the horde logs reveals two php errors with fseek() that >> occur whenever I send a message from the mobile device. I do not know >> if they are related with this issue or not. >> ----------------------------------------- >> >> May 3 00:59:10 localhost HORDE: [horde] PHP ERROR: rewind(): stream >> does not support seeking [pid 15385 on line 124 of >> "/usr/share/php/Horde.php"] > > This is inside the Horde::debug() method, which wouldn't be something > added by us. It's only used during debugging. > > >> May 3 00:59:10 localhost HORDE: [horde] PHP ERROR: fseek(): stream >> does not support seeking [pid 15385 on line 556 of >> "/usr/share/php/Horde/Stream.php"] > > Probably related to above. >
Attachment
Watch this ticket

Saved Queries