Alt-N Discussion Groups
MDaemon Discussion Groups
MDaemon Issues
ActiveSync - Attachments not downloading
Jeff X
Newbie
Posts: 3

Newbie
Posts: 3
Jeff X - 09:43am, Jan 21 2022
FYI - This has been happening across several MDaemon versions including v21.5.1.
Scenario - Using same email client on Android devices. Email format type: MIME. Send email with attachment from Office365 account to MDaemon account. The attachment is not included on the receiving device. Have to select 'Redownload email' in the email client. Once this is done, the attachment is included. This happens only when the email w/attachment is sent to an MDaemon account.
This issue was reported to the email client author (9Folders).
Below is their response:
…
According to the log, you have set two accounts. One is MDaemon server (EAS 14.1) and the other is Exchange clone. Two servers are not genuine Exchange servers. Anyway, looking over the log, your mail server(MDaemon) is responding abnormally to the ActiveSync's commands.
The above behavior is no problem in Microsoft Exchange Server or other Exchange-compatible servers.
Please, ask the Mail Server development team you are using. This error message spec is as follow.
https://docs.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-ashttp/f1dda4f4-5a06-4761-8ae6-38189eb649a8
01-20 12:43:41.897|I|AttachmentDownloadThread|-1|EAS|NONE attachments to auto download.
01-20 12:43:41.889|I|AttachmentDownloadThread|-1|EAS|NONE attachments to auto download.
01-20 12:43:41.823|E|JobFetchItem|-1|EAS|unexpected.
01-20 12:43:41.105|W|WBXML|-1|EAS|Server respond a invalid content type: application/vnd.ms-sync.multipart
01-20 12:43:40.350|D|SyncEngineServiceImpl|1|EAS|IEmailService.nxFetchBody: 1, 11317
This error is not allowed in EAS 12.x. But your server Activesync spec doesn't seem to support the attachments downloading.
The Content-Type header indicates the format of the data sent in the request body. When the request body for a command is in WBXML format, the Content-Type header value MUST be set to either "application/vnd.ms-sync.wbxml", or the shortened string "application/vnd.ms-sync". The shortened string is not allowed by protocol versions 2.5 and 12.0.
So attachments downloading of your server doesn't support the conversion. Status: 14 error of Activesync is the conversion error. Please contact your server admin about the issue.
https://docs.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-ascmd/cfcd14f8-9281-4864-966d-bb11259834e0
01-19 07:06:41.155|D|JobFetchAttachment|-1|EAS|trying... EAS[12.1]
01-19 07:06:41.150|I|JobFetchAttachment|-1|EAS|retry attachment download with legacy command.
01-19 07:06:41.150|E|a|-1|EAS|Exception occurred in Job #1.
com.ninefolders.hd3.engine.protocol.EASResponseException: Failed to get attachment file. %d131079
01-19 07:06:41.147|W|JobFetchAttachment|-1|EAS|Failed to get attachment file. status: 14, path: null, type: application/octet-stream
…
|
|
|