On Sun, Nov 11, 2018 at 06:43:27PM +0100, Matus UHLAR - fantomas wrote: > >On Sat, Nov 10, 2018 at 08:04:42PM -0500, listsb wrote: > >>i've just noticed that every mail received seems to be hitting the > >>ALL_TRUSTED test [ALL_TRUSTED=-1], regardless of where the message has come > >>from. i have the following: > >> > >>>grep -riF 'internal_networks' /etc/spamassassin/* > >>/etc/spamassassin/99_local-config.cf:internal_networks > >>198.19.20.50/32 > >>/etc/spamassassin/99_local-config.cf:internal_networks > >>198.19.20.212/32 > >> > >>here is a set of sample headers, slightly sanitized: > >> > >>http://dpaste.com/33J7SF5 > >> > >>how can i troubleshoot why this is happening? > > On 11.11.18 19:23, Henrik K wrote: > >Are you perhaps using amavisd-new 2.11.x ? It has originating bug that > >makes it always hit ALL_TRUSTED. > > > >https://gitlab.com/amavis/amavis/issues/6 > > is it the right issue? This one mentions DKIM not signing. > > Can it be the patch that causes everything hitting ALL_TRUSTED? > > You have also commented you need to investigate the patch, have you already?
Yes https://lists.amavis.org/pipermail/amavis-users/2018-November/005539.html https://lists.amavis.org/pipermail/amavis-users/2018-November/005540.html It's trivial to see from logs. Incoming external mail is always marked AcceptedInternal / LOCAL. Passed CLEAN {AcceptedInternal,Quarantined}, LOCAL Amavisd-new passes originating flag to SpamAssassin internally with some suppl_attr magic.. that's why it's even harder to diagnose, if you don't know that it happens in the background..
