| Summary | Mail cannot be forwarded via Activesync |
| Queue | Synchronization |
| Queue Version | Git master |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | cheese (at) nosuchhost (dot) net |
| Created | 09/29/2023 (683 days ago) |
| Due | |
| Updated | 10/19/2023 (663 days ago) |
| Assigned | 09/29/2023 (683 days ago) |
| Resolved | 10/18/2023 (664 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Thanks. Appreciate your work.
Assigned to Michael Rubinsky
sending in the ActiveSync forward command. It is too long to be sent
without the SMTP Binary extension, which not many smtp servers
actually support out of the box (including Postfix).
Looking into how we can intercept this and possibly mitigate.
New Attachment: horde-ticket-15152.tar.bz2
testmail-with-references and testmail-without-references are two
stripped down mails and have only differences in their subject and the
amount of references (1 line vs ca 160 lines)
and the activesynclogs for both forwards. once for forwarding with
lots of refernces (throwing error " Server does not support binary
message data." and the second successful try without errors.
thanks for your quick answer.
appreciated
State ⇒ Feedback
either the server error logs or activesync logs?
the mail shall not be used in public
reference /home/75/074/03/42/RAJO
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Mail cannot be forwarded via Activesync
Queue ⇒ Synchronization
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
we have an email, which cannot be forwarded with outlook connected via
activesync.
The problem comes from excessive references in the Mail-Header.
If those get deleted in the original mail, it can be fowarded as usual
Mail header NOT Working:
Importance: high
X-Priority: 1
Date: Tue, 19 Sep 2023 06:23:58 +0000
Message-ID:
<DB9P193MB1946514CCEBEBB30E5445C52C1FAA@DB9P193MB1946.EURP193.PROD.OUTLOOK.COM>
References:
<AM0P193MB0355D772F7839A51F5DC9CEBC14C0@AM0P193MB0355.EURP193.PROD.OUTLOOK.COM>
<AM0P193MB035503DD3B92ADC84B0AF53EC14C0@AM0P193MB0355.EURP193.PROD.OUTLOOK.COM>
<AM0P193MB03552A956ECF6E26A10BFCD8C14C0@AM0P193MB0355.EURP193.PROD.OUTLOOK.COM>
<AM0P193MB03555119E9515D86FFFB511EC14C0@AM0P193MB0355.EURP193.PROD.OUTLOOK.COM>
...
lots of other references
...
<DB9P193MB19467AB595FDD686945B3935C1FAA@DB9P193MB1946.EURP193.PROD.OUTLOOK.COM>
<DB9P193MB1946C55F04F56D24C414C5F6C1FAA@DB9P193MB1946.EURP193.PROD.OUTLOOK.COM>
In-Reply-To:
<DB9P193MB1946C55F04F56D24C414C5F6C1FAA@DB9P193MB1946.EURP193.PROD.OUTLOOK.COM>
Accept-Language: de-DE, en-US