Temporarily disable clamd + spamd on microbel #152

New Issue

oysteikt · 2024-08-30T13:30:37+02:00

oysteikt commented

2024-08-30 13:30:37 +02:00

I'm not sure these are actually used? microbel seems to be complaining at least. Might be flukes, but I don't think they should trigger panic log warnings either way

email sample (paniclog not empty)

2024-06-29 13:06:50 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out)
2024-06-29 13:07:03 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out)
2024-07-06 12:03:16 spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection timed out
2024-07-06 12:03:23 spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection timed out
2024-07-06 15:45:19 spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection timed out
2024-07-07 12:52:36 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out)
2024-07-08 09:20:30 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out)
2024-07-25 05:59:19 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out)
2024-07-30 11:03:42 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out)
2024-08-03 14:14:58 spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection timed out

I'm not sure these are actually used? microbel seems to be complaining at least. Might be flukes, but I don't think they should trigger panic log warnings either way <details> <summary>email sample (<i>paniclog not empty</i>)</summary> ``` 2024-06-29 13:06:50 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out) 2024-06-29 13:07:03 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out) 2024-07-06 12:03:16 spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection timed out 2024-07-06 12:03:23 spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection timed out 2024-07-06 15:45:19 spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection timed out 2024-07-07 12:52:36 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out) 2024-07-08 09:20:30 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out) 2024-07-25 05:59:19 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out) 2024-07-30 11:03:42 malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read from socket (Connection timed out) 2024-08-03 14:14:58 spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection timed out ``` </details>

oysteikt added this to the Email Next Gen milestone 2024-08-30 13:30:37 +02:00

oysteikt added the

security

crash report

bug

labels 2024-08-30 13:30:37 +02:00

oysteikt added this to the Kanban project 2024-08-30 13:30:37 +02:00

felixalb commented

2024-09-01 21:31:21 +02:00

This type of thing might look like creep from upgrading microbel over several debian/clamd versions over several years. Taking a backup, deleting all configuration files and overrides, and reinstalling it should hopefully work.

oysteikt added the

mail

label 2024-12-08 00:56:07 +01:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Drift/issues#152