diff options
author | Dylan Baker <dylan@pnwbakers.com> | 2017-07-14 14:10:47 -0700 |
---|---|---|
committer | Dylan Baker <dylan@pnwbakers.com> | 2017-08-17 10:59:49 -0700 |
commit | e024d670a3ba363df3b15b8d45fc87ac80c3de6b (patch) | |
tree | 5a9f97c201802a52f8c4560a43000d4857e885b6 /tests/db | |
parent | 26511b7a21acab317aab0832dcb7fd455ab1b496 (diff) |
db/utils: Handle multipart/signed inside multipart/mixed
It is possible (and actual mail clients such as kmail do) to embed a
multipart/signed within a multipart/mixed (this is briefly mentioned in
the acknowledgements of RFC 3156, and is perfectly valid according to
RFC 1341, which says that a multipart/mixed is exactly like a top level
message, except that the header may be empty.
Diffstat (limited to 'tests/db')
-rw-r--r-- | tests/db/utils_test.py | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/tests/db/utils_test.py b/tests/db/utils_test.py index ea0b6f20..d2c92577 100644 --- a/tests/db/utils_test.py +++ b/tests/db/utils_test.py @@ -593,7 +593,6 @@ class TestMessageFromFile(TestCaseClassCleanup): self.assertIn('Malformed OpenPGP message:', m.get_payload(2).get_payload()) - @unittest.expectedFailure def test_signed_in_multipart_mixed(self): """It is valid to encapsulate a multipart/signed payload inside a multipart/mixed payload, verify that works. |