bheam After upgrading to latest and greatest, some attachments just show as "attachment1" in outlook. mail headers are: --=-RvjNZXn5fUViJcMHQXJA Content-Type: application/pdf; charset=utf-8; name=iso-8859-1''Faktura%201805%20fra%20AGDER%20R%D8RSPYLING%20AS.pdf Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=iso-8859-1''Faktura%201805%20fra%20AGDER%20R%D8RSPYLING%20AS.pdf Thanks, Michael
freeloadermatt bheam +1 I am seeing something very similar. Two attachments "attachment1" and "attachment2" as shown below. attachment1 contains a text version of the email with image links. Example "Hello World here is an image [cid:image001.jpg@01DAFAC9.749DCC80]" attachment2 contains html of the same email. Example "<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" [blah blah blah] <p class="MsoNormal"><span style="font-family:"Montserrat Light"">Hello World here is an email" Using Debian 12 Bookworm with gromox (2.30.60.gcef3d09-1+41.1) WalterH the problem seems to happen when emails are sent from MS Exchange (external users with Microsoft-Branded Exchange and Outlook) and Apple IOS Devices
bheam WalterH Unlikely, they're invoices, so probably generated from some kind of onvoicing system. I'm also 90-99% sure this is a regression, as i'm pretty sure these emails were working before i did the upgrade.
PRJ We are having this problem with the attachments renamed to "attachment1" (without file-ending) since we switched to grommunio last year. I've created a ticket on the 30.05.2023. It has todo something with the convertation and the (new) Vmime library is required. A look into the roadmap shows: Q4 2024 "Further improved support for Internet Mail specifications (VMIME)" At least that is the situation/info I have, don't know if this behavior described here is the same?!
bheam WalterH I'm not sure what you mean by that. Do you mean that Macos / EWS creates some headers in the mail that messes with outlooks ability to read the attachment names?