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

emails parsed without a content type of multipart present no body #27

Merged
merged 2 commits into from
Oct 4, 2017
Merged

emails parsed without a content type of multipart present no body #27

merged 2 commits into from
Oct 4, 2017

Conversation

dahliagard
Copy link
Contributor

In cases where the content type of the email is not multipart, but instead an inline html or text content type, the message body is discarded and not presented via the API for processing and use. Most commonly presented with autoresponders from web clients such as gmail, but can also be seen in some cases with some mail clients. This patch will check if the processed structure is part of a multipart message to ensure html/text attachments aren't stripped from being an attachment during processing.

Example header

To: redacted
From: Ryan Gard <redacted>
Date: redacted
Message-ID: <redacted>
Subject: test vacation responder 
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Precedence: bulk
X-Autoreply: yes
Auto-Submitted: auto-replied

<div dir="ltr">This is a test vacation responder</div><br/><br/>-- <br/>Ryan Gard<br/>

@Webklex Webklex merged commit 46acaa9 into Webklex:master Oct 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants