Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow opening application/octet-stream attachments according to filename extension #6821

Closed
tnt opened this issue Jun 24, 2019 · 7 comments
Closed

Comments

@tnt
Copy link

tnt commented Jun 24, 2019

Hope this is no duplicate.

When an attachment for example is named invoice.PDF instead of invoice.pdf the "open" option is greyed out and clicking on the link results in downloading the file instead of opening it in a new window. Unfortunately people are sending quite often such files (probably created with Windows software...).

@alecpl
Copy link
Member

alecpl commented Jun 25, 2019

Most likely the Content-Type header is wrong. Could you provide a sample message?

@tnt
Copy link
Author

tnt commented Jun 30, 2019

I've checked it and you are right: mime-type "application/octet-stream" was already in the mail. (I should have checked that in the first place - sorry.)

Thank you for your quick response. If standards violating mails are not supported and there is no workaround for the issue it is of course completely agreeable to me if you close this issue.

@alecpl
Copy link
Member

alecpl commented Jul 8, 2019

I think, for application/octet-stream attachments we could consider setting the mimetype according to filename extension, in a way that will allow us opening the file. We do some checks based on extension, so we should do similar thing when checking "Open" action state.

@alecpl alecpl added this to the later milestone Jul 8, 2019
@alecpl alecpl changed the title Mimetype not recognized when filename extension is upper case Allow opening application/octet-stream attachments according to filename extension Jul 8, 2019
@tnt
Copy link
Author

tnt commented Jul 14, 2019

Great, thank you!

@jup31
Copy link

jup31 commented Dec 16, 2019

Does this enhancement has been published ? We need it for a long time on our company ;-) as we are using Bluemind solution based on round cube. Maybe a developer from Bluemind could take it and publish this modification.

@alecpl alecpl modified the milestones: later, 1.5-beta Dec 16, 2019
@jup31
Copy link

jup31 commented Dec 16, 2019

Thanks for adding it on 1.5-beta. This issue is impacting around 400 people in our company since 2015 at least. Ticket as been open in 2015 on Bluemind support but unfortunately not forward to the community.

@alecpl
Copy link
Member

alecpl commented Jun 7, 2020

Fixed.

@alecpl alecpl closed this as completed Jun 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants