@remit/mailbox-service 0.0.110 → 0.0.112

package/test/fixtures/mime-adversarial-e2e/01-octet-stream-pdf.eml

@@ -1,21 +0,0 @@
-From: alice@example.com
-To: bob@example.com
-Subject: Adversarial fixture 01 octet-stream PDF (Odido shape, #394)
-Date: Fri, 29 May 2026 09:00:00 +0000
-Message-Id: <adv-01-octet-stream-pdf@example.com>
-MIME-Version: 1.0
-Content-Type: multipart/mixed; boundary="=_adv01_="
-
---=_adv01_=
-Content-Type: text/html; charset=us-ascii
-Content-Transfer-Encoding: 7bit
-
-<html><body><p>Your contract PDF is attached.</p></body></html>
---=_adv01_=
-Content-Type: application/octet-stream; name="contract.pdf"
-Content-Transfer-Encoding: base64
-Content-Disposition: attachment; filename="contract.pdf"
-
-JVBERi0xLjQKJWZha2UgcGRmIGZvciBhZHZlcnNhcmlhbCBmaXh0dXJlIDAxIG9j
-dGV0LXN0cmVhbQolRU9GCg==
---=_adv01_=--

package/test/fixtures/mime-adversarial-e2e/02-nested-related-cid-image.eml

@@ -1,31 +0,0 @@
-From: alice@example.com
-To: bob@example.com
-Subject: Adversarial fixture 02 nested related html + cid image
-Date: Fri, 29 May 2026 09:00:00 +0000
-Message-Id: <adv-02-nested-related@example.com>
-MIME-Version: 1.0
-Content-Type: multipart/mixed; boundary="=_adv02_outer_="
-
---=_adv02_outer_=
-Content-Type: multipart/related; boundary="=_adv02_inner_="; type="text/html"
-
---=_adv02_inner_=
-Content-Type: text/html; charset=us-ascii
-Content-Transfer-Encoding: 7bit
-
-<html><body><p>Hi bob,</p><p>Inline logo: <img src="cid:logo@example.com" alt="logo"></p><p>-- alice</p></body></html>
---=_adv02_inner_=
-Content-Type: image/png; name="logo.png"
-Content-Transfer-Encoding: base64
-Content-Disposition: inline; filename="logo.png"
-Content-ID: <logo@example.com>
-
-iVBORw0KGgpmaXh0dXJlMDJjaWRpbWFnZWJ5dGVz
---=_adv02_inner_=--
---=_adv02_outer_=
-Content-Type: application/pdf; name="invoice.pdf"
-Content-Transfer-Encoding: base64
-Content-Disposition: attachment; filename="invoice.pdf"
-
-JVBERi0xLjQKJWFkdiAwMiBmaXh0dXJlIGludm9pY2UKJUVPRgo=
---=_adv02_outer_=--

package/test/fixtures/mime-adversarial-e2e/03-calendar-invite.eml

@@ -1,33 +0,0 @@
-From: alice@example.com
-To: bob@example.com
-Subject: Adversarial fixture 03 calendar invite + html
-Date: Fri, 29 May 2026 09:00:00 +0000
-Message-Id: <adv-03-calendar@example.com>
-MIME-Version: 1.0
-Content-Type: multipart/mixed; boundary="=_adv03_="
-
---=_adv03_=
-Content-Type: text/html; charset=us-ascii
-Content-Transfer-Encoding: 7bit
-
-<html><body><p>Hi bob,</p><p>Meeting invite for our sync on Monday is attached.</p><p>-- alice</p></body></html>
---=_adv03_=
-Content-Type: text/calendar; method=REQUEST; charset=us-ascii; name="invite.ics"
-Content-Transfer-Encoding: 7bit
-Content-Disposition: attachment; filename="invite.ics"
-
-BEGIN:VCALENDAR
-VERSION:2.0
-PRODID:-//Remit//Adversarial Fixture 03//EN
-METHOD:REQUEST
-BEGIN:VEVENT
-UID:adv-03-event@example.com
-DTSTAMP:20260529T090000Z
-DTSTART:20260601T140000Z
-DTEND:20260601T150000Z
-SUMMARY:Adversarial fixture 03 sync
-ORGANIZER:mailto:alice@example.com
-ATTENDEE:mailto:bob@example.com
-END:VEVENT
-END:VCALENDAR
---=_adv03_=--

package/test/fixtures/mime-adversarial-e2e/04-forwarded-rfc822-with-attachments.eml

@@ -1,42 +0,0 @@
-From: alice@example.com
-To: bob@example.com
-Subject: Adversarial fixture 04 forwarded rfc822 with inner attachment
-Date: Fri, 29 May 2026 09:00:00 +0000
-Message-Id: <adv-04-forwarded@example.com>
-MIME-Version: 1.0
-Content-Type: multipart/mixed; boundary="=_adv04_outer_="
-
---=_adv04_outer_=
-Content-Type: text/plain; charset=us-ascii
-Content-Transfer-Encoding: 7bit
-
-Hi bob,
-
-Forwarding the message below for your records. Note the original carries its own attachment.
-
--- alice
---=_adv04_outer_=
-Content-Type: message/rfc822
-Content-Disposition: attachment; filename="forwarded.eml"
-
-From: carol@example.com
-To: alice@example.com
-Subject: Original message with attachment for fixture 04
-Date: Thu, 28 May 2026 12:00:00 +0000
-Message-Id: <adv-04-inner@example.com>
-MIME-Version: 1.0
-Content-Type: multipart/mixed; boundary="=_adv04_inner_="
-
---=_adv04_inner_=
-Content-Type: text/plain; charset=us-ascii
-Content-Transfer-Encoding: 7bit
-
-Original message body before forwarding.
---=_adv04_inner_=
-Content-Type: application/pdf; name="original.pdf"
-Content-Transfer-Encoding: base64
-Content-Disposition: attachment; filename="original.pdf"
-
-JVBERi0xLjQKJWFkdiAwNCBpbm5lciBwZGYKJUVPRgo=
---=_adv04_inner_=--
---=_adv04_outer_=--

package/test/fixtures/mime-adversarial-e2e/05-tnef-winmail.eml

@@ -1,25 +0,0 @@
-X-Remit-Fixture-Note: Synthetic TNEF stub for fixture 05. mailparser surfaces this as an application/ms-tnef attachment with filename "winmail.dat" — which is the #402 contract. The trailing BODYSTRUCTURE round-trip via imapflow is skipped for this shape (see EXPECTATIONS in adversarial-mime.e2e.test.ts). TODO(#402): replace with a real-world winmail.dat capture once we have one to ship.
-From: alice@example.com
-To: bob@example.com
-Subject: Adversarial fixture 05 Outlook TNEF winmail.dat
-Date: Fri, 29 May 2026 09:00:00 +0000
-Message-Id: <adv-05-tnef@example.com>
-MIME-Version: 1.0
-Content-Type: multipart/mixed; boundary="=_adv05_="
-
---=_adv05_=
-Content-Type: text/plain; charset=us-ascii
-Content-Transfer-Encoding: 7bit
-
-Hi bob,
-
-This message carries the Microsoft TNEF (winmail.dat) shape that some Outlook senders still produce. Remit should list the attachment without crashing the body sync.
-
--- alice
---=_adv05_=
-Content-Type: application/ms-tnef; name="winmail.dat"
-Content-Transfer-Encoding: base64
-Content-Disposition: attachment; filename="winmail.dat"
-
-eJ8+IgEAAAABAAAACAAAAAAAAAA=
---=_adv05_=--

package/test/fixtures/mime-adversarial-e2e/06-8bit-non-ascii.eml

@@ -1,15 +0,0 @@
-From: alice@example.com
-To: bob@example.com
-Subject: =?UTF-8?B?Q2Fmw6kgZmHDp2FkZSAtIGFkdmVyc2FyaWFsIGZpeHR1cmUgMDY=?=
-Date: Fri, 29 May 2026 09:00:00 +0000
-Message-Id: <adv-06-8bit@example.com>
-MIME-Version: 1.0
-Content-Type: text/plain; charset=utf-8
-Content-Transfer-Encoding: 8bit
-
-Hallo bob,
-
-De café op de hoek heeft een prachtige façade. We’ll meet there — ben je vrij?
-
-Groetjes,
-alice

package/test/fixtures/mime-adversarial-e2e/07-quoted-printable-soft-breaks.eml

@@ -1,17 +0,0 @@
-From: alice@example.com
-To: bob@example.com
-Subject: Adversarial fixture 07 quoted-printable with soft line breaks
-Date: Fri, 29 May 2026 09:00:00 +0000
-Message-Id: <adv-07-qp@example.com>
-MIME-Version: 1.0
-Content-Type: text/plain; charset=utf-8
-Content-Transfer-Encoding: quoted-printable
-
-Hi bob,
-
-This paragraph deliberately uses quoted-printable soft line breaks so a sing=
-le logical line is wrapped across multiple physical lines without inserting=
- a real newline. The body-sync pipeline must reassemble it back into one l=
-ogical line when rendering.
-
-Also includes a non-ASCII token: caf=C3=A9 r=C3=A9union =E2=80=94 alice

package/test/fixtures/mime-adversarial-e2e/08-alternative-empty-text.eml

@@ -1,18 +0,0 @@
-From: alice@example.com
-To: bob@example.com
-Subject: Adversarial fixture 08 alternative with empty text/plain
-Date: Fri, 29 May 2026 09:00:00 +0000
-Message-Id: <adv-08-empty-text-alt@example.com>
-MIME-Version: 1.0
-Content-Type: multipart/alternative; boundary="=_adv08_="
-
---=_adv08_=
-Content-Type: text/plain; charset=us-ascii
-Content-Transfer-Encoding: 7bit
-
---=_adv08_=
-Content-Type: text/html; charset=us-ascii
-Content-Transfer-Encoding: 7bit
-
-<html><body><p>Hi bob,</p><p>The text/plain sibling of this multipart/alternative is intentionally empty. The HTML part must still render.</p><p>-- alice</p></body></html>
---=_adv08_=--