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

Use real Outlook ContentId Attribute to resolve CID Attachments #19

Merged
merged 2 commits into from
Dec 18, 2019

Conversation

derrohrbach
Copy link

Outlook saves the CID in MSG Files using Attribute 3712. This merge request allows the usage of this attribute for the ContentId

if (!tryAddCid(cidMap, html, fileAttachment, fileAttachment.getFilename())) {
tryAddCid(cidMap, html, fileAttachment, fileAttachment.getLongFilename());
}
tryAddCid(cidMap, html, fileAttachment, fileAttachment.getContentId());
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You removed the failover for using alternative cid's in favor of Outlook native 3712 attribute. Is that guaranteed to be always present?

Copy link
Author

@derrohrbach derrohrbach Dec 17, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be honest I don't know, I just assumed it does. We can also keep the old failovers too, just to be sure. In my testing 3712 was always there

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it's better to keep the fallback just in case. If you could please amend it I'll merge and release.

@bbottema bbottema merged commit cee5b13 into bbottema:master Dec 18, 2019
@bbottema
Copy link
Owner

bbottema commented Dec 18, 2019

Can't release 1.5.0 right now as OSS Sonatype is having network issues again.

@derrohrbach
Copy link
Author

Thanks for your work and the smooth and simple process of merging changes! Can you update me once you have successfully published it to the OSS Sonatype?

@bbottema bbottema added this to the 1.5.0 milestone Dec 18, 2019
@bbottema
Copy link
Owner

Released in 1.5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants