1

Topic: allow bad headers

============ Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.5-1
- Linux/BSD distribution name and version: debianx64 8.4
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? No
- Related log if you're reporting an issue:
====
Hi!
I get letters from some of my counterparties. They block my server with the comment "quarantine: bad-head -..."
Added address amavis whitelist did not help.
How do I know what is wrong with the head? How to resolve to take the letters from some domains, even if the headers is not correct?

----

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

2

Re: allow bad headers

Bad header usually generated by MUA, so the question is, which MUA do you use?
Try to send email to your own mail account, check whether Amavisd on iRedMail server reports similar error.

3 (edited by admin@tayra.ru 2017-01-23 17:16:01)

Re: allow bad headers

My server is blocking incoming messages from some users due to incorrect headers, to the MUA is not reached. I can not fix those headers. I just have to allow such messages.

4

Re: allow bad headers

Seems i misunderstood the original question.

To bypass ALL header checks, add line below in Amavisd config file and restart Amavisd service:

@bypass_header_checks_maps = 1;

FYI: Find the config file: http://www.iredmail.org/docs/file.locat … ml#amavisd