On 26/05/2016 13:19, Nick Howitt wrote:
OK, I've been heavily shot at for my set up which is totally
irrelevant to the question I posed and not a pleasant experience. Is
there any possibility of some help with the problem I posted about?
Matus snuck in the most likely answer a while back - message size.
In Amavis it look as if the relevant option is:
$sa_mail_body_size_limit
I don't use Amavis so can't comment much but I believe that would be
the relevant setting to change. Google suggests that it may be as low
as 200kb. SpamAssassin defaults to 500kb. Of course you may still get
messages over that size. I use FuGlu to connect SA and that leaves a
handy message telling me scanning was skipped due to message size. You
don't have that but as you have no SA headers at all in the sample you
posted I'd assume it never got scanned and message size is the most
common culprit.
Hi Kevin,
Thanks for that. I guess I missed the reply while I was being flamed
for not knowing everything about everything and not running my own DNS
resolver.
I'll check that when I get home but I doubt it is the setting. The
message size was only about 39kB in total and bigger messages are
being scanned successfully.
Now at home, my $sa_mail_body_size_limit is set to 500*1024 which seems
an odd way of going about things but looks like it is valid. All my
peacocks-mail.com messages have been less than 80kB.
I'm going to see if I can get a test case with a debug log so I can post
to amavis's list. Unfortunately what was my known test case passed
through SA fine today so I need to find another reliable one.
