[AMaViS-user] how to bypass header check by sender

[Starling Dave (Indy)]

Currently we are running Spamassassin 3.0.2, Amavisd-new 2.2.1, on =
Postfix 2.1.5. The problem is that we have several outside users =
sending mail to us that have headers that do not conform to RFC 2822. =
Many of these messages sent to us have non-encoded 8-bit data in the =
Subject message header.

An example of the message that they receive from us:

INVALID HEADER (INVALID CHARACTERS OR SPACE GAP)

Non-encoded 8-bit data (92 hex) in message header 'Subject': Subject: =
The book\\222s
available\\n

This nondelivery report was generated by the amavisd-new program
at host indyvss3. Our internal reference code for your message
is 03019-01-75.

What I would like is someway to bypass the header check for a list of =
senders (not recipients). Is there an easy way to do this? I see that =
there is bypass_header_check_maps and bad_header_lovers_maps but these =
are for the recipients not the senders. Also, the whitelist only =
bypasses spam checks not header checks.

Thanks.
Dave Starling

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
AMaViS-user mailing list
AMaVi...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

[Mark Martinec]

Dave,

> Currently we are running Spamassassin 3.0.2, Amavisd-new 2.2.1, on Postfix
> 2.1.5. The problem is that we have several outside users sending mail to
> us that have headers that do not conform to RFC 2822. Many of these
> messages sent to us have non-encoded 8-bit data in the Subject message
> header. ...

> What I would like is someway to bypass the header check for a list of

> senders (not recipients). Is there an easy way to do this?

This is currently not possible, but is on a TODO list.

If you can somehow localize these senders, like being your internal
or authenticated users, it is possible to assign a policy bank
to them with disabled header checks.

Mark