Here the line, redacted: Dec 9 09:30:36.700 [10600] dbg: received-header: unparseable: from host4.domain.it (LHLO host4.domain.it) (1.1.1.1) by host3.domain.it with LMTP; Tue, 3 Dec 2019 11:55:44 +0100 (CET)
Thank you Francesco On Mon, Dec 9, 2019 at 9:22 AM Henrik K <h...@hege.li> wrote: > On Mon, Dec 09, 2019 at 09:10:25AM +0100, hg user wrote: > > Investigating why a message scored X when arrived and Y now (recovered > from > > user inbox), I realized that UNPARSEABLE_RELAY_COUNT rule fires on all > messages > > recovered from user inbox. > > In almost all cases this is not a problem, except for XPRIO_SHORT_SUBJ: > it > > fired on X and didn't fire on Y due to UNPARSEABLE_RELAY_COUNT... > > > > How can I understand why UNPARSEABLE_RELAY_COUNT rule fires? > > Use debugging > > spamassassin -t -D -L < message | grep unparseable: > > Show the output here if you can, it might need to be added in SA code. > >
