1

Topic: Proper way to quarantine emails with bad headers?

==== Required information ====
- iRedMail version: 0.8.5
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Linux/BSD distribution name and version: CentOS 6.5
- Related log if you're reporting an issue:
====

We have a couple important emails that have been blocked due to bad headers, see below maillog:

Apr  3 07:00:53 dmzsvr14v policyd: rcpt=6050, whitelist=update, host=xxx.xxx.xxx.xxx (unknown), from=xxxx@xxxx.com, to=xxxx@xxxx.com, size=0
Apr  3 07:01:13 dmzsvr14v amavis[10393]: (10393-02) Blocked BAD-HEADER-0 {DiscardedInternal}, LOCAL [xxx.xxx.xxx.xxx]:42937 [153.88.253.124] <xxxx@xxxx.com> -> <xxxx@xxxxx.com>, Message-ID: <3A30CD44F2C81D4BB1257F06F6065DD01CDE5E7B@ESESSMB209.xxx.xxx>, mail_id: dkj2MUMhAq0m, Hits: -, size: 49805, 440 ms

I tried 'amavisd-release dkj2MUMhAq0m' but I believe these emails have been discarded?

What is the proper configuration to quarantine emails with bad headers?

Thanks!
Luke

----

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

2

Re: Proper way to quarantine emails with bad headers?

1) iRedMail doesn't quarantine and discard BAD-HEADER emails with default settings. Did you configure Amavisd to do this? What's your setting of below two values in Amavisd config file:

$final_bad_header_destiny =
$bad_header_quarantine_method =

2) If you configure Amavisd to quarantine bad header emails on file system, you can release it with 'amavisd-release xxx' directly. If it's quarantined into SQL database, you should specify 'quar_type=Q' in command line.
Reference: http://www.ijs.si/software/amavisd/README.protocol.txt