On 03/03/2015 12:00 PM, plug-requ...@lists.pdxlinux.org wrote:
> Here are the lines from /var/log/maillog.1 that cause the results of
> logwatch to be rejected:
That's the log entry. I really need to see the main.cf body_checks
entry. Also, let us know if you're using amavis -- it's good bu
On Mon, 2 Mar 2015, Brian Martin wrote:
> You may also want to share the body_checks snippit of your configuration
> (the line itself plus any immediately following lines that begin with
> whitespace), either here on the list or to me privately so I/we know what
> you're looking at.
Brian,
He
>
> Brian,
>
> Looks reasonable, but in my main.cf permit_mynetworks is on line 538
> and body_checks is on line 611.
>
> Might other tests be involved?
>
There are a number of places where Postfix runs tests. For example,
smtpd_helo_restrictions lists a series tests to run when a remote
On Sun, 1 Mar 2015, Brian Martin wrote:
> I'm guessing a bit here since I haven't seen your main.cf file, but in
> general Postfix processes these kinds of checks in the order in which they
> are listed. Find where the body_checks test is being invoked, and
> insert/move permit_mynetworks ahead of
On 03/01/2015 12:00 PM, plug-requ...@lists.pdxlinux.org wrote:
> Postfix uses a file named 'body_checks' to examine message content for
> typical (that is, repetative) words and phrases common in UCE. When it finds
> a hit to a body_checks rule the message is rejected. Works like a charm, but
>
Postfix uses a file named 'body_checks' to examine message content for
typical (that is, repetative) words and phrases common in UCE. When it finds
a hit to a body_checks rule the message is rejected. Works like a charm, but
...
When there is such a rejected message in /var/log/maillog it is
