Exchange Attachments not visible

[Norathus]

Hi,
I've got problems with the following combination:
3 Mail Accounts (2 x IMAP, 1 x Exchange).
I don't sign mails on the IMAP-accounts, but on the Exchange one, when sending mails from other devices (with Outlook or Thunderbird), as I'm still waiting for the feature in Aquamail.
Interestingly enough, Aquamail does no longer display attachments on the Exchange account, when the mail has been signed (on another device).
So when I look at my sent mails, I can only the .p7m-file as an attachment, but for example the .pdf-file I sent is missing.
On incoming mails, which are not signed, the attachments show up as expected.
Looks like: If the mail has been signed, only the signature file ist displayed as an attachment (and not yet interpreted).

Maybe you could have a look into this.

[Anton Donchev]

Hi Norathus,

The .p7m attachment is send when the mail is encrypted. Signed only mails are with .p7s extension.
This means that all the mail content including the pdf file or other attachments and email parts is encrypted and encapsulated into the .p7m message part.

We are planning on implementing the S/MIME for Exchange and when we do AM will be able to parse encrypted mails and display content.

Thanks,
Anton.

[Norathus]

Hi Anton,

I can assure you that the mails are only signed and not encrypted.
The text can be read without any certificate added and configured in Aquamail (and even through Outlook WebAccess (which does not support S/MIME without a special addon)).
When using for example Thunderbird without configured S/MIME it can display the attachments without issues. I would like Aquamail to do the same.

Thanks

[Anton Donchev]

Could you send us example of such an email to smime3@mobisystems.com?

It's interesting, because we do not have S/MIME support for EWS yet and since it is different protocol than IMAP and POP3 we have not changed anything there.
 

[Norathus]

I've sent you a message.

[Norathus]

Are there any news on this?

[Martin, Aqua Mail Support]

Hi Norathus,

We've logged this as a bug to fix in the future.

Martin