https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7909

--- Comment #6 from Andrey L <[email protected]> ---
Ok, we are one step closer. This is a definite bug in spamass-milter . Now, I
just have to figure why it happens...

I think it would be nice if we can track this bug here, as spamass-milter is
de-facto unmaintained...

May 19 11:36:14 mail postfix/smtpd[11268]: connect from
kot50.emails.tinkoff.ru[185.138.181.50]
May 19 11:36:14 mail postfix/smtpd[11268]: Anonymous TLS connection established
from kot50.emails.tinkoff.ru[185.138.181.50]: TLSv1.2 with cipher
ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
May 19 11:36:14 mail postfix/smtpd[11268]: 4FlR6Q4RNhz3xJc:
client=kot50.emails.tinkoff.ru[185.138.181.50]
May 19 11:36:14 mail postfix/cleanup[11275]: 4FlR6Q4RNhz3xJc:
message-id=<20210519113112.0.20210519113112_eui_@1163550.1906942035.28485779.masssending.tinkoff>
May 19 11:36:14 mail spamd[8167]: spamd: connection from ::1 [::1]:35572 to
port 783, fd 5
May 19 11:36:14 mail spamd[8167]: spamd: handle_user (getpwnam) unable to find
user: 'tattink'
May 19 11:36:14 mail spamd[8167]: spamd: still running as root: user not
specified with -u, not found, or set to root, falling back to nobody
May 19 11:36:14 mail spamd[8167]: spamd: processing message
<20210519113112.0.20210519113112_eui_@1163550.1906942035.28485779.masssending.tinkoff>
for tattink:65534
May 19 11:36:14 mail spamd[8167]: received-header: unparseable: from
kot50.emails.tinkoff.ru (unknown) by mail.lelik.us (Postfix 3.4.14/8.13.0) with
SMTP id unknown Wed, 19 May 2021 11:36:14 +0300 (envelope-from
<[email protected]>);
May 19 11:36:14 mail spamd[8167]: metadata: X-Spam-Relays-Trusted: 
May 19 11:36:14 mail spamd[8167]: metadata: X-Spam-Relays-Untrusted: 
May 19 11:36:14 mail spamd[8167]: metadata: X-Spam-Relays-Internal: 
May 19 11:36:14 mail spamd[8167]: metadata: X-Spam-Relays-External: 
May 19 11:36:14 mail spamd[8167]: spamd: clean message (2.6/5.0) for
tattink:65534 in 0.2 seconds, 27671 bytes.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to