AMaViS - A Mail Virus Scanner

Andrea,

> How can I test BAD_HEADER?

Perhaps ... by sending a message with a bad header.


The sub check_header_validity implements the following checks:

- bad mime header section or bad mime structure
- invalid 8-bit characters in header section
- invalid control characters in header section
- folded header field made up entirely of whitespace
- header line longer than rfc2822 limit of 998 characters
- header field syntax error
- missing required header field
- duplicate header field

In addition, syntax errors in MIME structure as reported
by MIME::Parser are included in this category.

  Mark

Dear,

We're using amavisd-new 2.6.4 on Debian Squeeze to call a mail filter.
Although $final_bad_header_destiny is set to D_PASS mail with bad
headers is still quarantined.
In a previous version 2.4.2 we used the setting
$bad_header_quarantine_method = undef;
Is this still valid in 2.6.4? Or how can we prevent mail with bad
headers from being quarantined?

Thx,
P.

P,

> We're using amavisd-new 2.6.4 on Debian Squeeze to call a mail filter.
> Although $final_bad_header_destiny is set to D_PASS mail with bad
> headers is still quarantined.
> In a previous version 2.4.2 we used the setting
> $bad_header_quarantine_method = undef;
> Is this still valid in 2.6.4? Or how can we prevent mail with bad
> headers from being quarantined?

Yes, setting $bad_header_quarantine_method to undef should still
be able to disable quarantining of bad header mail under 2.6.4,
assuming there are no other more serious reasons for quarantining
and that $clean_quarantine_method and $archive_quarantine_method
are left at their default undef value. Are you seing otherwise?
Btw, setting  $bad_header_quarantine_to = undef  would achieve
the same effect.

  Mark