-
Notifications
You must be signed in to change notification settings - Fork 31
Open
Description
I recently ran across an email where the attachment could not be extracted using pzymail. The issue appears to be with the parsing of boundaries and over relying on them to extract content. Below is an example that will not extract the attachment.
To: test@testuser.com
Subject: Testing
Message-ID: <abc123@testuser.com>
Return-Path: bounce@testuser.com
Date: Tue, 06 Oct 2015 11:25:00 +0000
From: "testing" <testing@testsource.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; charset="UTF-8"; boundary="b1_000001"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
--b1_000001
Content-Type: multipart/alternative;
boundary="b3_000001"
--b3_000001
Content-Type: text/plain; format=flowed; charset="UTF-8"
Content-Transfer-Encoding: 8bit
testing
--b3_000001
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 8bit
<html>
<head>
</head>
<body>
testing
</body>
</html>
--b3_000001--
--b1_000002
Content-Type: application/octet-stream;
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="file.txt"
VGhpcyBpcyBhIHRlc3QgZmlsZS4K
--b1_000002--
Metadata
Metadata
Assignees
Labels
No labels