I went to sleep at 2 in the morning
with 2700 messages in local queue, now I can say is 0.
All thanks to all of you!
dspam_clean -s -p -u ended at 8:21 I guess because at that time is
the last error for dspam. I keep searching the mail log for more
You can start simscan now, but keep clam=no in simcontrol until we can
get clamd@scan started.
On 8/8/2020 6:40 AM, Diego Piñon Conde wrote:
I went to sleep at 2 in the morning with 2700 messages in local queue,
now I can say is 0.
All thanks to all of you!
dspam_clean -s -p -u ended at 8:2
Also look in freshclam log (/var/log/clamav/freshclam.log)
# tail -n 20 /var/log/clamav/freshclam.log
post output here
On 8/8/2020 8:16 AM, Eric Broch wrote:
You can start simscan now, but keep clam=no in simcontrol until we can
get clamd@scan started.
On 8/8/2020 6:40 AM, Diego Piñon C
El 08/08/2020 a las 11:16 a. m., Eric
Broch escribió:
You can start simscan now, but keep clam=no in simcontrol until
we can get clamd@scan started.
On 8/8/2020 6:40 AM, Diego Piñon
Conde wrote:
El 08/08/2020 a las 11:24 a. m., Eric
Broch escribió:
Also look in freshclam log (/var/log/clamav/freshclam.log)
# tail -n 20 /var/log/clamav/freshclam.log
post output here
On 8/8/2020 8:16 AM, Eric Broch
wrote:
Do this
# systemctl stop clamav-freshclam
# freshclam (post output)
# systemctl start clamav-freshclam
On 8/8/2020 8:42 AM, Diego Piñon Conde wrote:
El 08/08/2020 a las 11:24 a. m., Eric Broch escribió:
Also look in freshclam log (/var/log/clamav/freshclam.log)
# tail -n 20 /var/log/cla
El 08/08/2020 a las 11:53 a. m., Eric
Broch escribió:
Do this
# systemctl stop clamav-freshclam
# freshclam (post output)
# systemctl start clamav-freshclam
On 8/8/2020 8:42 AM, Diego Piñon
Conde wrote:
okay, so database is up to date.
On 8/8/2020 9:01 AM, Diego Piñon Conde wrote:
El 08/08/2020 a las 11:53 a. m., Eric Broch escribió:
Do this
# systemctl stop clamav-freshclam
# freshclam (post output)
# systemctl start clamav-freshclam
On 8/8/2020 8:42 AM, Diego Piñon Conde wrote:
El 08/
You can also tell in the mail log (/var/log/maillog) if messages have
been encrypted, spamdyke will let you know if messages from a certain
host are using TLS. See this entry:
Aug 8 09:59:45 myhost spamdyke[10388]: TLS_ENCRYPTED from: (unknown)
to: (unknown) origin_ip: 66.163.185.72 origin_rd
sorry for the delay Eric!, I was travelling to home...
Job for clamd@scan.service failed because the control process
exited with error code. See "systemctl status clamd@scan.service"
and "journalctl -xe" for details.
Did not start...
systemctl status clamd@sc
can you do this
# ps aux |grep clam
and post output
On 8/8/2020 11:28 AM, Diego Piñon Conde wrote:
sorry for the delay Eric!, I was travelling to home...
Job for clamd@scan.service failed because the control process exited
with error code. See "systemctl status clamd@scan.service" and
"jou
sure!
root 6126 1.0 0.0 112812 964 pts/1 S+
14:59 0:00 grep --color=auto clam
clamupd+ 30315 0.0 0.2 130376 4028 ? Ss 12:00 0:00
/usr/bin/freshclam -d --foreground=true
El 08/08/2020 a las 02:38 p. m., Eric
It was PEBKAC. My settings are now:
#2020-08-08
#tls-certificate-file=/var/qmail/control/servercert.pem
tls-level=smtp
And I'm getting an A+ from the LuxSci TLS tester.
On Sun, Aug 9, 2020 at 4:11 AM Eric Broch wrote:
> You can also tell in the mail log (/var/log/maillog) if messages have bee
I can do a zoom session tomorrow if that works Diego. Ping me directly and we
can see if i can help.
> Il giorno 8 ago 2020, alle ore 11:01, Diego Piñon Conde
> ha scritto:
>
>
> sure!
>
> root 6126 1.0 0.0 112812 964 pts/1S+ 14:59 0:00 grep
> --color=auto clam
>
14 matches
Mail list logo