1

Topic: Bad header section mime error

==== Required information ====
- iRedMail version (check /etc/iredmail-release):  0.9.4
- Linux/BSD distribution name and version: Debian Jessie
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL
- Web server (Apache or Nginx): apache
- Manage mail accounts with iRedAdmin-Pro? Y
- Related log if you're reporting an issue:
====

Feb 10 18:31:38 mail amavis[31963]: (31963-12) Passed CLEAN {RelayedInternal}, LOCAL [194.40.209.65]:9374 [194.40.209.65] <john@domain1.com> -> <alice@domain2.com>, Queue-ID: CFC672A0, Message-ID: <OF428078B8.6EB2EBE7-ONC1257F55.0056A955-C1257F55.005F7D86@domain1.com>, mail_id: fSS2m0yk8Syw, Hits: 0.8, size: 4366984, queued_as: C66A35DA, 4325 ms

Feb 11 11:23:56 mail amavis[4143]: (04143-17) Blocked BAD-HEADER-0 {DiscardedInternal,Quarantined}, LOCAL [194.40.208.65]:57445 [194.40.208.65] <john@domain1.com> -> <alice@domain2.com>, quarantine: s6MUBCcCz79Z, Queue-ID: 820A2231, Message-ID: <OFDF3E6AF4.76943FCF-ONC1257F56.00391E4A-1455186233981@domain1.com>, mail_id: s6MUBCcCz79Z, Hits: -, size: 397944, 251 ms

X-Amavis-Alert    BAD HEADER SECTION, MIME error: error: unexpected end of parts before epilogue

Hi,
both logs regard the same sender and same recipient,  but were able to receive the first mail but not the second.
What can cause this issue?

Thanks in advance

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Bad header section mime error

Did those 2 emails contain the same content? I mean, same headers and body.