> On Apr 28, 2016, at 7:05 AM, Voytek <li...@sbt.net.au> wrote:
>
> I was updating file type definitions in my header checks when I noticed I
> have header checks as well as mime header checks :
>
> /etc/postfix/main.cf
>
> header_checks = pcre:/etc/postfix/header_checks.pcre
> mime_header_checks = pcre:$config_directory/mime_headers.pcre
Mime_header_checks only applies to messages with mime headers and is normally
used for content-type blocking (like rejecting .exe files).
header_checks (default: empty)
These are applied to initial message headers (except for the
headers that are processed with mime_header_checks).
mime_header_checks (default: $header_checks)
These are applied to MIME related message headers only.
If a message comes in with no mime types, it is checked against header checks.
If a message comes in with mime types it is checked against mime header checks
IF IT EXISTS, and then is checked against header_checks.
> header_checks has (now updated) "/^Content-(Disposition|Type)....” AND
There’s no reason (pretty sure) to have content-(Disposition|Type) in
header_checks.
> mime_header_checks has just "/^Content-(Disposition|Type)...." AND nothing
> else
Yes, that’s pretty usual.
> do I need both ?
Need? No. Want? Probably.
> do I need "/^Content-(Disposition|Type)...." in both checks ?
No. This header would not appear in a non-mime message.
--
The older you get the more you need the people you knew when you were
young.
