Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread remo 
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
> 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 Broch escribió:
>> 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 "journalctl -xe" 
>>> for details.
>>> 
>>> Did not start...
>>> 
>>> systemctl status clamd@scan.servic
>>> 
>>> ● clamd@scan.service - clamd scanner (scan) daemon
>>>Loaded: loaded (/usr/lib/systemd/system/clamd@.service; enabled; vendor 
>>> preset: disabled)
>>>Active: failed (Result: start-limit) since Sat 2020-08-08 14:15:23 -03; 
>>> 3min 28s ago
>>>  Docs: man:clamd(8)
>>>man:clamd.conf(5)
>>>https://www.clamav.net/documents/
>>>   Process: 4316 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf 
>>> (code=exited, status=1/FAILURE)
>>> 
>>> Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner (scan) 
>>> daemon.
>>> Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service entered failed 
>>> state.
>>> Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
>>> Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service holdoff time over, 
>>> scheduling restart.
>>> Aug 08 14:15:23 pegasus systemd[1]: Stopped clamd scanner (scan) daemon.
>>> Aug 08 14:15:23 pegasus systemd[1]: start request repeated too quickly for 
>>> clamd@scan.service
>>> Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner (scan) 
>>> daemon.
>>> Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service entered failed 
>>> state.
>>> Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
>>> Hint: Some lines were ellipsized, use -l to show in full.
>>> 
>>> journalctl -xe
>>> 
>>> -- The result is failed.
>>> Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service entered failed 
>>> state.
>>> Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
>>> Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service holdoff time over, 
>>> scheduling restart.
>>> Aug 08 14:15:23 pegasus systemd[1]: Stopped clamd scanner (scan) daemon.
>>> -- Subject: Unit clamd@scan.service has finished shutting down
>>> -- Defined-By: systemd
>>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>> --
>>> -- Unit clamd@scan.service has finished shutting down.
>>> Aug 08 14:15:23 pegasus systemd[1]: start request repeated too quickly for 
>>> clamd@scan.service
>>> Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner (scan) 
>>> daemon.
>>> -- Subject: Unit clamd@scan.service has failed
>>> -- Defined-By: systemd
>>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>> --
>>> -- Unit clamd@scan.service has failed.
>>> --
>>> 
>>> 
>>> El 08/08/2020 a las 12:26 p. m., Eric Broch escribió:
 Diego
 
 Please try this new configuration file...
 
 Attached is a new scan.conf (scan.conf.test).
 
 put it into your directory /etc/clamd.d
 
 # mv /etc/clamd.d/scan.conf /etc/clamd.d/scan.conf.bak
 
 # mv /etc/clamd.d/scan.conf.test /etc/clamd.d/scan.conf
 
 # systemctl start clamd@scan
 
 Eric
 
 
 
 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/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:
> 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:21 I guess because at that time is 
>> the last error for dspam. I keep searching the mail log for more 
>> errors.
>> 
>> Aug  8 08:21:37 pegasus dspam[17546]: query error: Deadlock found 
>> whe

Re: [qmailtoaster] TLS reason: 503_MAIL_first_(#5.5.1)

2020-08-08 Thread Chris 
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 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_rdns:
> sonic329-10.consmr.mail.ne1.yahoo.com auth: (unknown) encryption:
> TLS_PASSTHROUGH reason: (empty)
> On 8/7/2020 8:51 PM, Chris wrote:
>
>
>
> On Sat, Aug 8, 2020 at 1:26 PM Eric Broch  wrote:
>
>> What version of qmail do you have?
>>
> qmail-1.03-3.2.qt.el7.x86_64
>
>>
>> And, what about the email coming from the qmailtoaster-list? Can you send
>> that header along?
>>
> I send most mailing list emails to my gmail account, so I can communicate
> with the list even if my mail server is down.  :)
>
> -Chris
>
>
>
>> It can depend on the remote host as well. If you have a gmail account
>> send yourself an email from it and send the header along. Here's a header
>> from  a gmail account.
>>
>> Received: from unknown (HELO mail-qk1-f177.google.com) (209.85.222.177)
>>   by myhost.whitehorsetc.com with ESMTPS (ECDHE-RSA-AES128-GCM-SHA256 
>> encrypted)
>>
>>
>> On 8/7/2020 7:12 PM, Chris wrote:
>>
>> When I disabled TLS in spamdyke, I sent myself a message from one of the
>> problematic systems that was known to trigger repeats.  That message's
>> headers indicate qmail did not pick up the TLS encryption:
>>
>> Content-Type: ⁨text/html; charset=UTF-8⁩
>> Mime-Version: ⁨1.0⁩
>> X-Ses-Outgoing: ⁨2020.08.07-54.240.37.249⁩
>> Dkim-Signature: ⁨v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
>> s=2ybsbk45dtwlgerewyfzx5qt442lak5j; d=reddit.com; t=1596830148;
>> h=From:To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID:Date;
>> bh=hrVase2qeFHtu0bLhsrYTx2n7ISeji9Uin83vE7Xdh4=;
>> b=QrrO2K0wMkJ8uIgTRE1XSNq892ay6s7FXgEnkwZY0KaDDViiUV4h5y5HVYIoZjcv
>> wqZ97y/QgJEKnC98NPGJ9bJJnGbdoHUdaxY+VOx52u6nm8ofu3cS3BQELBuid+PMf2Y
>> E+QOoLacnNtusPmpc1+PVwJKNuIGRsk2pCUmk7os=⁩
>> Dkim-Signature: ⁨v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
>> s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1596830148;
>> h=From:To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID:Date:Feedback-ID;
>> bh=hrVase2qeFHtu0bLhsrYTx2n7ISeji9Uin83vE7Xdh4=;
>> b=V18r7xu5iTXqr9kSFDcX/StzbVKQX9nSXcJ/Q4JoHpVRoK5u2sCNikDVVBghOzeT
>> vInG1XcJaOMYMofcCKv0F8TwYAc253AdkK+b5PRn/eE1C2BucNO73/zCggwTSTI6lZG
>> IMPzOiBk77HYMfSH4YEKQWY7dWSqdQGPX0Glf7Wg=⁩
>> Return-Path: ⁨<
>> 01000173ca7e6738-e1b4d416-58b8-47ad-8a02-3c9e2696d0c8-000...@amazonses.com
>> >⁩
>> Feedback-Id:
>> ⁨1.us-east-1.UqlFplRllIQtiw+Kq2b87y7uRSu9p66fMici2AQNsMU=:AmazonSES⁩
>> Content-Transfer-Encoding: ⁨7bit⁩
>> Received: ⁨(qmail 8880 invoked by uid 89); 7 Aug 2020 19:56:04 -⁩
>> Received: ⁨by simscan 1.4.0 ppid: 8871, pid: 8873, t: 2.0387s scanners:
>> attach: 1.4.0 clamav: 0.101.4/m:59/d:25897 spam: 3.4.2⁩
>> *Received: ⁨from unknown (HELO a37-249.smtp-out.amazonses.com
>> ) (54.240.37.249) by
>> mail.bayhosting.net  with SMTP; 7 Aug 2020
>> 19:56:02 -⁩*
>> ⁨<
>> 01000173ca7e6738-e1b4d416-58b8-47ad-8a02-3c9e2696d0c8-000...@email.amazonses.com
>> >⁩
>> Delivered-To: ⁨ckni...@ghostwheel.com⁩
>> Received-Spf: ⁨pass (mail.bayhosting.net: SPF record at amazonses.com
>> designates 54.240.37.249 as permitted sender)
>>
>>
>>
>> On Sat, Aug 8, 2020 at 12:59 PM Eric Broch 
>> wrote:
>>
>>> That's the nature of spamdyke. See the documentation. I understand why
>>> it was programmed the way it was, with TLS, so that it could, after
>>> decrypting the email, operate spam blocking techniques. With qmail doing
>>> decryption everything that passes through spamdyke is encrypted so
>>> examining the email is not possible.
>>> tls-level   none, smtp smtp-no-passthrough or smtps none: Do not offer
>>> or allow SSL/TLS, even if qmail supports it.
>>>
>>> smtp: If tls-certificate-file is given, offer TLS during the SMTP
>>> conversation and decrypt the traffic. If tls-certificate-file is not
>>> given, allow qmail to offer TLS (if it has been patched to provide TLS) and
>>> pass the encrypted traffic to qmail.
>>>
>>> smtp-no-passthrough: If tls-certificate-file is given, offer TLS during
>>> the SMTP conversation and decrypt the traffic. If tls-certificate-file is
>>> not given, prevent TLS from starting.
>>>
>>> smtps: Initiate a SSL session at the beginning of the connection,
>>> before SMTP begins.
>>>
>>> If tls-level is given multiple times, spamdyke will use the last value
>>> it finds.
>>>
>>> If tls-level is not given, spamdyke will use a value of smtp.
>>>
>>> tls-level is not valid within configuration directories.
>>>
>>> See TLS

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread Diego Piñon Conde 

  
  
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
  Broch escribió:


  
  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 "journalctl -xe" for details.
Did not start...

systemctl status clamd@scan.servic
● clamd@scan.service
  - clamd scanner (scan) daemon
     Loaded: loaded (/usr/lib/systemd/system/clamd@.service;
  enabled; vendor preset: disabled)
     Active: failed (Result: start-limit) since Sat 2020-08-08
  14:15:23 -03; 3min 28s ago
   Docs: man:clamd(8)
     man:clamd.conf(5)
     https://www.clamav.net/documents/
    Process: 4316 ExecStart=/usr/sbin/clamd -c
  /etc/clamd.d/%i.conf (code=exited, status=1/FAILURE)
  
  Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd
  scanner (scan) daemon.
  Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service
  entered failed state.
  Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service
  failed.
  Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service
  holdoff time over, scheduling restart.
  Aug 08 14:15:23 pegasus systemd[1]: Stopped clamd scanner
  (scan) daemon.
  Aug 08 14:15:23 pegasus systemd[1]: start request repeated too
  quickly for clamd@scan.service
  Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd
  scanner (scan) daemon.
  Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service
  entered failed state.
  Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service
  failed.
  Hint: Some lines were ellipsized, use -l to show in full.

journalctl -xe
-- The result is failed.
  Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service
  entered failed state.
  Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service
  failed.
  Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service
  holdoff time over, scheduling restart.
  Aug 08 14:15:23 pegasus systemd[1]: Stopped clamd scanner
  (scan) daemon.
  -- Subject: Unit clamd@scan.service
  has finished shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit clamd@scan.service
  has finished shutting down.
  Aug 08 14:15:23 pegasus systemd[1]: start request repeated too
  quickly for clamd@scan.service
  Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd
  scanner (scan) daemon.
  -- Subject: Unit clamd@scan.service
  has failed
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit clamd@scan.service
  has failed.
  --
  

El 08/08/2020 a las 12:26 p. m.,
  Eric Broch escribió:


  
  Diego
  Please try this new configuration file...
  
  Attached is a new scan.conf (scan.conf.test).
  put it into your directory /etc/clamd.d
  
  # mv /etc/clamd.d/scan.conf /etc/clamd.d/scan.conf.bak
  # mv /etc/clamd.d/scan.conf.test /etc/clamd.d/scan.conf
  # systemctl start clamd@scan
  Eric
  
  
  
  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/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 o

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread Eric Broch 

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 
"journalctl -xe" for details.


Did not start...

/*systemctl status clamd@scan.servic*/

● clamd@scan.service - clamd scanner (scan) daemon
   Loaded: loaded (/usr/lib/systemd/system/clamd@.service; enabled; 
vendor preset: disabled)
   Active: failed (Result: start-limit) since Sat 2020-08-08 14:15:23 
-03; 3min 28s ago

 Docs: man:clamd(8)
   man:clamd.conf(5)
https://www.clamav.net/documents/
  Process: 4316 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf 
(code=exited, status=1/FAILURE)


Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner 
(scan) daemon.
Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service entered 
failed state.

Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service holdoff time 
over, scheduling restart.

Aug 08 14:15:23 pegasus systemd[1]: Stopped clamd scanner (scan) daemon.
Aug 08 14:15:23 pegasus systemd[1]: start request repeated too quickly 
for clamd@scan.service
Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner 
(scan) daemon.
Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service entered 
failed state.

Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

/*journalctl -xe*/

-- The result is failed.
Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service entered 
failed state.

Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service holdoff time 
over, scheduling restart.

Aug 08 14:15:23 pegasus systemd[1]: Stopped clamd scanner (scan) daemon.
-- Subject: Unit clamd@scan.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit clamd@scan.service has finished shutting down.
Aug 08 14:15:23 pegasus systemd[1]: start request repeated too quickly 
for clamd@scan.service
Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner 
(scan) daemon.

-- Subject: Unit clamd@scan.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit clamd@scan.service has failed.
--

El 08/08/2020 a las 12:26 p. m., Eric Broch escribió:


Diego

Please try this new configuration file...

Attached is a new scan.conf (scan.conf.test).

put it into your directory /etc/clamd.d

# mv /etc/clamd.d/scan.conf /etc/clamd.d/scan.conf.bak

# mv /etc/clamd.d/scan.conf.test /etc/clamd.d/scan.conf

# systemctl start clamd@scan

Eric


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/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:


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:21 I guess because at that time 
is the last error for dspam. I keep searching the mail log for 
more errors.


Aug  8 08:21:37 pegasus dspam[17546]: query error: Deadlock 
found when trying to get lock; try restarting transaction: see 
sql.errors for more details

Aug  8 08:21:37 pegasus dspam[17546]: bailing on error -2
Aug  8 08:21:37 pegasus dspam[17546]: received invalid result 
(!DSR_ISSPAM && !DSR_ISINNOCENT): -2


clamd@scan still refuse to start, but I'm really don't sure I 
wanna use it. Virus db update takes forever and kill my server 
for at least 20 minutes, at least with clamAV version.  I 
didn't get to test with the EPEL version...


Is this the time for enable simscan Eric? Yesterday replace 
simscan with qmail-queue in /etc/tcprules.d/tcp.smtp


El 07/08/2020 a las 11:08 p. m., Eric Broch escribió:


good!

you can run instead:

# dspam_clean -s -p -u

for all users

or

dspam_clean -s -p -u u...@domain.tld us...@domain.tld ... 
us...@domain.tld


for the users you choose.

This will also purge the database.


On 8/7/2020 8:01 PM, Diego Piñon Conde wrote:

/purge-4.1.sql finally ends with no message

El vie., 7 ago. 2020 a las 19:28, Eric Broch 
(mailto:ebr...@whitehorsetc.com>>) 
escribió:


optimize dspam also...

 # mysql  -u dspam -p dspam <
/usr/share/dspam/sql-scripts/mysql/purge-4.1.sql

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread Diego Piñon Conde 

  
  
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@scan.servic
● clamd@scan.service - clamd scanner (scan) daemon
     Loaded: loaded (/usr/lib/systemd/system/clamd@.service;
  enabled; vendor preset: disabled)
     Active: failed (Result: start-limit) since Sat 2020-08-08
  14:15:23 -03; 3min 28s ago
   Docs: man:clamd(8)
     man:clamd.conf(5)
     https://www.clamav.net/documents/
    Process: 4316 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf
  (code=exited, status=1/FAILURE)
  
  Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner
  (scan) daemon.
  Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service
  entered failed state.
  Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
  Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service holdoff
  time over, scheduling restart.
  Aug 08 14:15:23 pegasus systemd[1]: Stopped clamd scanner (scan)
  daemon.
  Aug 08 14:15:23 pegasus systemd[1]: start request repeated too
  quickly for clamd@scan.service
  Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner
  (scan) daemon.
  Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service
  entered failed state.
  Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
  Hint: Some lines were ellipsized, use -l to show in full.

journalctl -xe
-- The result is failed.
  Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service
  entered failed state.
  Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
  Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service holdoff
  time over, scheduling restart.
  Aug 08 14:15:23 pegasus systemd[1]: Stopped clamd scanner (scan)
  daemon.
  -- Subject: Unit clamd@scan.service has finished shutting down
  -- Defined-By: systemd
  -- Support:
  http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit clamd@scan.service has finished shutting down.
  Aug 08 14:15:23 pegasus systemd[1]: start request repeated too
  quickly for clamd@scan.service
  Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner
  (scan) daemon.
  -- Subject: Unit clamd@scan.service has failed
  -- Defined-By: systemd
  -- Support:
  http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit clamd@scan.service has failed.
  --
  

El 08/08/2020 a las 12:26 p. m., Eric
  Broch escribió:


  
  Diego
  Please try this new configuration file...
  
  Attached is a new scan.conf (scan.conf.test).
  put it into your directory /etc/clamd.d
  
  # mv /etc/clamd.d/scan.conf /etc/clamd.d/scan.conf.bak
  # mv /etc/clamd.d/scan.conf.test /etc/clamd.d/scan.conf
  # systemctl start clamd@scan
  Eric
  
  
  
  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/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:
  
  

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:21 I guess because
at that time is the last error for dspam. I keep
searching the mail log for more errors.

Aug  8 08:21:37 pegasus dspam[17546]: query error:
Deadlock found when trying

Re: [qmailtoaster] TLS reason: 503_MAIL_first_(#5.5.1)

2020-08-08 Thread Eric Broch 
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_rdns: 
sonic329-10.consmr.mail.ne1.yahoo.com auth: (unknown) encryption: 
TLS_PASSTHROUGH reason: (empty)


On 8/7/2020 8:51 PM, Chris wrote:



On Sat, Aug 8, 2020 at 1:26 PM Eric Broch > wrote:


What version of qmail do you have?

qmail-1.03-3.2.qt.el7.x86_64

And, what about the email coming from the qmailtoaster-list? Can
you send that header along?

I send most mailing list emails to my gmail account, so I can 
communicate with the list even if my mail server is down.  :)


-Chris

It can depend on the remote host as well. If you have a gmail
account send yourself an email from it and send the header along.
Here's a header from  a gmail account.

Received: from unknown (HELOmail-qk1-f177.google.com  
) (209.85.222.177)
   bymyhost.whitehorsetc.com    with ESMTPS 
(ECDHE-RSA-AES128-GCM-SHA256 encrypted)


On 8/7/2020 7:12 PM, Chris wrote:

When I disabled TLS in spamdyke, I sent myself a message from one
of the problematic systems that was known to trigger repeats. 
That message's headers indicate qmail did not pick up the TLS
encryption:

Content-Type: ⁨text/html; charset=UTF-8⁩
Mime-Version: ⁨1.0⁩
X-Ses-Outgoing: ⁨2020.08.07-54.240.37.249⁩
Dkim-Signature: ⁨v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=2ybsbk45dtwlgerewyfzx5qt442lak5j; d=reddit.com
; t=1596830148;

h=From:To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID:Date;
bh=hrVase2qeFHtu0bLhsrYTx2n7ISeji9Uin83vE7Xdh4=;
b=QrrO2K0wMkJ8uIgTRE1XSNq892ay6s7FXgEnkwZY0KaDDViiUV4h5y5HVYIoZjcv
wqZ97y/QgJEKnC98NPGJ9bJJnGbdoHUdaxY+VOx52u6nm8ofu3cS3BQELBuid+PMf2Y
E+QOoLacnNtusPmpc1+PVwJKNuIGRsk2pCUmk7os=⁩
Dkim-Signature: ⁨v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com
; t=1596830148;

h=From:To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID:Date:Feedback-ID;
bh=hrVase2qeFHtu0bLhsrYTx2n7ISeji9Uin83vE7Xdh4=;
b=V18r7xu5iTXqr9kSFDcX/StzbVKQX9nSXcJ/Q4JoHpVRoK5u2sCNikDVVBghOzeT
vInG1XcJaOMYMofcCKv0F8TwYAc253AdkK+b5PRn/eE1C2BucNO73/zCggwTSTI6lZG
IMPzOiBk77HYMfSH4YEKQWY7dWSqdQGPX0Glf7Wg=⁩
Return-Path:
⁨<01000173ca7e6738-e1b4d416-58b8-47ad-8a02-3c9e2696d0c8-000...@amazonses.com

>⁩
Feedback-Id:
⁨1.us-east-1.UqlFplRllIQtiw+Kq2b87y7uRSu9p66fMici2AQNsMU=:AmazonSES⁩
Content-Transfer-Encoding: ⁨7bit⁩
Received: ⁨(qmail 8880 invoked by uid 89); 7 Aug 2020 19:56:04 -⁩
Received: ⁨by simscan 1.4.0 ppid: 8871, pid: 8873, t: 2.0387s
scanners: attach: 1.4.0 clamav: 0.101.4/m:59/d:25897 spam: 3.4.2⁩
*Received: ⁨from unknown (HELO a37-249.smtp-out.amazonses.com
) (54.240.37.249) by
mail.bayhosting.net  with SMTP; 7 Aug
2020 19:56:02 -⁩*

⁨<01000173ca7e6738-e1b4d416-58b8-47ad-8a02-3c9e2696d0c8-000...@email.amazonses.com

>⁩
Delivered-To: ⁨ckni...@ghostwheel.com
⁩
Received-Spf: ⁨pass (mail.bayhosting.net
: SPF record at amazonses.com
 designates 54.240.37.249 as permitted sender)



On Sat, Aug 8, 2020 at 12:59 PM Eric Broch
mailto:ebr...@whitehorsetc.com>> wrote:

That's the nature of spamdyke. See the documentation. I
understand why it was programmed the way it was, with TLS, so
that it could, after decrypting the email, operate spam
blocking techniques. With qmail doing decryption everything
that passes through spamdyke is encrypted so examining the
email is not possible.

|tls-level| |none|,|smtp||smtp-no-passthrough|or|smtps|
|none|: Do not offer or allow SSL/TLS, even if qmail supports it.

|smtp|: If|tls-certificate-file|is given, offer TLS during
the SMTP conversation and decrypt the traffic.
If|tls-certificate-file|is not given, allow qmail to offer
TLS (if it has been patched to provide TLS) and pass the
encrypted traffic to qmail.

|smtp-no-passthrough|: If|tls-certificate-file|is given,
offer TLS during the SMTP conversation and decrypt the
traffic. If|tls-certificate-file|is not given, prevent TLS
from starting.

|smtps|: Initiate a SSL session at the b

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread Eric Broch 

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/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:


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:21 I guess because at that time 
is the last error for dspam. I keep searching the mail log for 
more errors.


Aug  8 08:21:37 pegasus dspam[17546]: query error: Deadlock found 
when trying to get lock; try restarting transaction: see 
sql.errors for more details

Aug  8 08:21:37 pegasus dspam[17546]: bailing on error -2
Aug  8 08:21:37 pegasus dspam[17546]: received invalid result 
(!DSR_ISSPAM && !DSR_ISINNOCENT): -2


clamd@scan still refuse to start, but I'm really don't sure I 
wanna use it. Virus db update takes forever and kill my server 
for at least 20 minutes, at least with clamAV version.  I didn't 
get to test with the EPEL version...


Is this the time for enable simscan Eric? Yesterday replace 
simscan with qmail-queue in /etc/tcprules.d/tcp.smtp


El 07/08/2020 a las 11:08 p. m., Eric Broch escribió:


good!

you can run instead:

# dspam_clean -s -p -u

for all users

or

dspam_clean -s -p -u u...@domain.tld us...@domain.tld ... 
us...@domain.tld


for the users you choose.

This will also purge the database.


On 8/7/2020 8:01 PM, Diego Piñon Conde wrote:

/purge-4.1.sql finally ends with no message

El vie., 7 ago. 2020 a las 19:28, Eric Broch 
(mailto:ebr...@whitehorsetc.com>>) 
escribió:


optimize dspam also...

 # mysql  -u dspam -p dspam <
/usr/share/dspam/sql-scripts/mysql/purge-4.1.sql

On 8/7/2020 4:24 PM, Eric Broch wrote:


what's this yield

# ls -la /var/log/clamd

On 8/7/2020 4:19 PM, Diego Piñon Conde wrote:

Same error

systemctl start clamd@scan
Job for clamd@scan.service 
failed because a timeout was exceeded. See "systemctl
status clamd@scan.service "
and "journalctl -xe" for details.

El vie., 7 ago. 2020 a las 19:08, Eric Broch
(mailto:ebr...@whitehorsetc.com>>) escribió:

run the following and try to restart clamd@scan

curl -o /etc/clamd.d/scan.confhttps://raw.githubusercontent.com/qmtoaster/scripts/master/scan.conf  


On 8/7/2020 4:05 PM, Diego Piñon Conde wrote:

 systemctl start clamd@scan               Job for
clamd@scan.service 
failed because a timeout was exceeded. See
"systemctl status clamd@scan.service
" and "journalctl -xe"
for details.

Did Not start

El vie., 7 ago. 2020 a las 18:44, Eric Broch
(mailto:ebr...@whitehorsetc.com>>) escribió:

don't stop it. allow it to go until it starts.
sometimes it takes quite a while.

On 8/7/2020 3:39 PM, Diego Piñon Conde wrote:


systemctl start clamd@scan

freeze and do nothing

# ls -ld /var/log/dspam

/drwxrwx--- 2 dspam mail 81 Feb 18 03:57
/var/log/dspam/

# ls -la /var/log/dspam /
/

/total 10256
drwxrwx---   2 dspam    mail       81 Feb 18
03:57 .
drwxr-xr-x. 16 root     root     4096 Aug  7
17:53 ..
-rw-r--r--   1 dspam    mail        0 Feb 18
03:57 sql.errors
-rw-rw   1 vpopmail mail 10493507 Feb 18
01:53 sql.errors-20200218
-rw---   1 dspam    mail        0 Feb 18
03:57 sql.errors-20200218.gz/






El vie., 7 ago. 2020 a las 18:31, Eric Broch
(mailto:ebr...@whitehorsetc.com>>) escribió:

What's the output of the following commands?

# ls -ld /var/log/dspam

and

# ls -la /var/log/dspam

On 8/7/2020 2:46 PM, Diego Piñon Conde wrote:

This is the only weird message i can
repeated times see from now
[00 ]Aug  7 17:40:54 pegasus dspam[19962]:
Unable to open file for writing:
/var/log/dspam/sql.errors: Permission denied
[00]Aug  7 17:40:55 pegasus dspam[19962]:
bailing on error -2
[00]Aug  7 17:40:55 pegasus dspam[19962]:
received invalid result (!DSR_ISSP

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread Diego Piñon Conde 

  
  
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/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:
  
  

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:21 I guess because at
that time is the last error for dspam. I keep searching
the mail log for more errors.

Aug  8 08:21:37 pegasus dspam[17546]: query error:
Deadlock found when trying to get lock; try restarting
transaction: see sql.errors for more details
Aug  8 08:21:37 pegasus dspam[17546]: bailing on error
-2
Aug  8 08:21:37 pegasus dspam[17546]: received invalid
result (!DSR_ISSPAM && !DSR_ISINNOCENT): -2

clamd@scan still refuse to start, but I'm really don't
sure I wanna use it. Virus db update takes forever and
kill my server for at least 20 minutes, at least with
clamAV version.  I didn't get to test with the EPEL
version...

Is this the time for enable simscan Eric? Yesterday
replace simscan with qmail-queue in
/etc/tcprules.d/tcp.smtp
  
  
  El 07/08/2020 a las 11:08
p. m., Eric Broch escribió:
  
  

good!
you can run instead: 

# dspam_clean -s -p -u 

for all users

or 

dspam_clean -s -p -u u...@domain.tld
  us...@domain.tld ... us...@domain.tld
for the users you choose.
This will also purge the database.



On 8/7/2020 8:01 PM, Diego
  Piñon Conde wrote:


  
  /purge-4.1.sql finally ends with no
message
  
  
  
El vie., 7 ago.
  2020 a las 19:28, Eric Broch ()
  escribió:


  
optimize dspam also...

 # mysql  -u dspam -p dspam <
  /usr/share/dspam/sql-scripts/mysql/purge-4.1.sql

On 8/7/2020 4:24 PM, Eric Broch wrote:


  what's this yield
  # ls -la /var/log/clamd
  On 8/7/2020 4:19 PM, Diego Piñon Conde
wrote:
  
  

  Same error
  
  
  systemctl start clamd@scan
Job for clamd@scan.service
failed because a timeout was exceeded.
See "systemctl status clamd@scan.service"
and "journalctl -xe" for details.
  



  El vie.,
7 ago. 2020 a las 19:08, Eric Broch
()
escribió:
  
  

  run the following and try to
restart clamd

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread Eric Broch 

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/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 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:21 I guess because at that time is 
the last error for dspam. I keep searching the mail log for more 
errors.


Aug  8 08:21:37 pegasus dspam[17546]: query error: Deadlock found 
when trying to get lock; try restarting transaction: see sql.errors 
for more details

Aug  8 08:21:37 pegasus dspam[17546]: bailing on error -2
Aug  8 08:21:37 pegasus dspam[17546]: received invalid result 
(!DSR_ISSPAM && !DSR_ISINNOCENT): -2


clamd@scan still refuse to start, but I'm really don't sure I wanna 
use it. Virus db update takes forever and kill my server for at 
least 20 minutes, at least with clamAV version.  I didn't get to 
test with the EPEL version...


Is this the time for enable simscan Eric? Yesterday replace simscan 
with qmail-queue in /etc/tcprules.d/tcp.smtp


El 07/08/2020 a las 11:08 p. m., Eric Broch escribió:


good!

you can run instead:

# dspam_clean -s -p -u

for all users

or

dspam_clean -s -p -u u...@domain.tld us...@domain.tld ... 
us...@domain.tld


for the users you choose.

This will also purge the database.


On 8/7/2020 8:01 PM, Diego Piñon Conde wrote:

/purge-4.1.sql finally ends with no message

El vie., 7 ago. 2020 a las 19:28, Eric Broch 
(mailto:ebr...@whitehorsetc.com>>) 
escribió:


optimize dspam also...

 # mysql  -u dspam -p dspam <
/usr/share/dspam/sql-scripts/mysql/purge-4.1.sql

On 8/7/2020 4:24 PM, Eric Broch wrote:


what's this yield

# ls -la /var/log/clamd

On 8/7/2020 4:19 PM, Diego Piñon Conde wrote:

Same error

systemctl start clamd@scan
Job for clamd@scan.service 
failed because a timeout was exceeded. See "systemctl
status clamd@scan.service " and
"journalctl -xe" for details.

El vie., 7 ago. 2020 a las 19:08, Eric Broch
(mailto:ebr...@whitehorsetc.com>>) escribió:

run the following and try to restart clamd@scan

curl -o /etc/clamd.d/scan.confhttps://raw.githubusercontent.com/qmtoaster/scripts/master/scan.conf  


On 8/7/2020 4:05 PM, Diego Piñon Conde wrote:

 systemctl start clamd@scan           Job for
clamd@scan.service  failed
because a timeout was exceeded. See "systemctl status
clamd@scan.service " and
"journalctl -xe" for details.

Did Not start

El vie., 7 ago. 2020 a las 18:44, Eric Broch
(mailto:ebr...@whitehorsetc.com>>) escribió:

don't stop it. allow it to go until it starts.
sometimes it takes quite a while.

On 8/7/2020 3:39 PM, Diego Piñon Conde wrote:


systemctl start clamd@scan

freeze and do nothing

# ls -ld /var/log/dspam

/drwxrwx--- 2 dspam mail 81 Feb 18 03:57
/var/log/dspam/

# ls -la /var/log/dspam /
/

/total 10256
drwxrwx---   2 dspam  mail       81 Feb 18 03:57 .
drwxr-xr-x. 16 root root     4096 Aug  7 17:53 ..
-rw-r--r--   1 dspam  mail        0 Feb 18 03:57
sql.errors
-rw-rw   1 vpopmail mail 10493507 Feb 18
01:53 sql.errors-20200218
-rw---   1 dspam  mail        0 Feb 18 03:57
sql.errors-20200218.gz/






El vie., 7 ago. 2020 a las 18:31, Eric Broch
(mailto:ebr...@whitehorsetc.com>>) escribió:

What's the output of the following commands?

# ls -ld /var/log/dspam

and

# ls -la /var/log/dspam

On 8/7/2020 2:46 PM, Diego Piñon Conde wrote:

This is  the only weird message i can
repeated times see from now
[00 ]Aug  7 17:40:54 pegasus dspam[19962]:
Unable to open file for writing:
/var/log/dspam/sql.errors: Permission denied
[00]Aug  7 17:40:55 pegasus dspam[19962]:
bailing on error -2
[00]Aug  7 17:40:55 pegasus dspam[19962]:
received invalid result (!DSR_ISSPAM &&
!DSR_ISINNOCENT): -2
[00]Aug  7 17:40:55 pegasus dspam[19962]:
process_message returned error -5.  delivering.

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread Diego Piñon Conde 

  
  
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:
  
  

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:21 I guess because at that
time is the last error for dspam. I keep searching the mail
log for more errors.

Aug  8 08:21:37 pegasus dspam[17546]: query error: Deadlock
found when trying to get lock; try restarting transaction:
see sql.errors for more details
Aug  8 08:21:37 pegasus dspam[17546]: bailing on error -2
Aug  8 08:21:37 pegasus dspam[17546]: received invalid
result (!DSR_ISSPAM && !DSR_ISINNOCENT): -2

clamd@scan still refuse to start, but I'm really don't sure
I wanna use it. Virus db update takes forever and kill my
server for at least 20 minutes, at least with clamAV
version.  I didn't get to test with the EPEL version...

Is this the time for enable simscan Eric? Yesterday replace
simscan with qmail-queue in /etc/tcprules.d/tcp.smtp
  
  
  El 07/08/2020 a las 11:08 p. m.,
Eric Broch escribió:
  
  

good!
you can run instead: 

# dspam_clean -s -p -u 

for all users

or 

dspam_clean -s -p -u u...@domain.tld
  us...@domain.tld
  ... us...@domain.tld
for the users you choose.
This will also purge the database.



On 8/7/2020 8:01 PM, Diego
  Piñon Conde wrote:


  
  /purge-4.1.sql finally ends with no message
  
  
  
El vie., 7 ago. 2020 a
  las 19:28, Eric Broch ()
  escribió:


  
optimize dspam also...

 # mysql  -u dspam -p dspam <
  /usr/share/dspam/sql-scripts/mysql/purge-4.1.sql

On 8/7/2020 4:24 PM, Eric Broch wrote:


  what's this yield
  # ls -la /var/log/clamd
  On 8/7/2020 4:19 PM, Diego Piñon Conde wrote:
  
  

  Same error
  
  
  systemctl start clamd@scan
Job for clamd@scan.service
failed because a timeout was exceeded. See
"systemctl status clamd@scan.service"
and "journalctl -xe" for details.
  



  El vie., 7
ago. 2020 a las 19:08, Eric Broch ()
escribió:
  
  

  run the following and try to restart
clamd@scan
  curl -o /etc/clamd.d/scan.conf https://raw.githubusercontent.com/qmtoaster/scripts/master/scan.conf 


  On 8/7/2020 4:05 PM, Diego Piñon
Conde wrote:
  
  

   systemctl start clamd@scan      
        Job for clamd@scan.service
failed because a timeout was
exceeded. See "systemctl status clamd@scan.service"
and "journalctl -xe" for details.
  
  
  Did Not start

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread Diego Piñon Conde 

  
  
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:
  
  

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 errors.
  
  Aug  8 08:21:37 pegasus dspam[17546]: query error: Deadlock
  found when trying to get lock; try restarting transaction: see
  sql.errors for more details
  Aug  8 08:21:37 pegasus dspam[17546]: bailing on error -2
  Aug  8 08:21:37 pegasus dspam[17546]: received invalid result
  (!DSR_ISSPAM && !DSR_ISINNOCENT): -2
  
  clamd@scan still refuse to start, but I'm really don't sure I
  wanna use it. Virus db update takes forever and kill my server
  for at least 20 minutes, at least with clamAV version.  I
  didn't get to test with the EPEL version...
  
  Is this the time for enable simscan Eric? Yesterday replace
  simscan with qmail-queue in /etc/tcprules.d/tcp.smtp


El 07/08/2020 a las 11:08 p. m.,
  Eric Broch escribió:


  
  good!
  you can run instead: 
  
  # dspam_clean -s -p -u 
  
  for all users
  
  or 
  
  dspam_clean -s -p -u u...@domain.tld
us...@domain.tld
... us...@domain.tld
  for the users you choose.
  This will also purge the database.
  
  
  
  On 8/7/2020 8:01 PM, Diego Piñon
Conde wrote:
  
  

/purge-4.1.sql finally ends with no message



  El vie., 7 ago. 2020 a
las 19:28, Eric Broch ()
escribió:
  
  

  optimize dspam also...
  
   # mysql  -u dspam -p dspam <
/usr/share/dspam/sql-scripts/mysql/purge-4.1.sql
  
  On 8/7/2020 4:24 PM, Eric Broch wrote:
  
  
what's this yield
# ls -la /var/log/clamd
On 8/7/2020 4:19 PM, Diego Piñon Conde wrote:


  
Same error


systemctl start clamd@scan
  Job for clamd@scan.service
  failed because a timeout was exceeded. See
  "systemctl status clamd@scan.service"
  and "journalctl -xe" for details.

  
  
  
El vie., 7
  ago. 2020 a las 19:08, Eric Broch ()
  escribió:


  
run the following and try to restart
  clamd@scan
curl -o /etc/clamd.d/scan.conf https://raw.githubusercontent.com/qmtoaster/scripts/master/scan.conf 


On 8/7/2020 4:05 PM, Diego Piñon Conde
  wrote:


  
 systemctl start clamd@scan        
        Job for clamd@scan.service
  failed because a timeout was exceeded.
  See "systemctl status clamd@scan.service"
  and "journalctl -xe" for details.


Did Not start

  
  
  
El
  vie., 7 ago. 2020 a las 18:44, Eric
  Broch ()
  escribió:


  
don't stop it. allow it to go
  until it starts. sometimes it

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread Eric Broch 

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 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:21 I guess because at that time is 
the last error for dspam. I keep searching the mail log for more errors.


Aug  8 08:21:37 pegasus dspam[17546]: query error: Deadlock found 
when trying to get lock; try restarting transaction: see sql.errors 
for more details

Aug  8 08:21:37 pegasus dspam[17546]: bailing on error -2
Aug  8 08:21:37 pegasus dspam[17546]: received invalid result 
(!DSR_ISSPAM && !DSR_ISINNOCENT): -2


clamd@scan still refuse to start, but I'm really don't sure I wanna 
use it. Virus db update takes forever and kill my server for at least 
20 minutes, at least with clamAV version.  I didn't get to test with 
the EPEL version...


Is this the time for enable simscan Eric? Yesterday replace simscan 
with qmail-queue in /etc/tcprules.d/tcp.smtp


El 07/08/2020 a las 11:08 p. m., Eric Broch escribió:


good!

you can run instead:

# dspam_clean -s -p -u

for all users

or

dspam_clean -s -p -u u...@domain.tld us...@domain.tld ... 
us...@domain.tld


for the users you choose.

This will also purge the database.


On 8/7/2020 8:01 PM, Diego Piñon Conde wrote:

/purge-4.1.sql finally ends with no message

El vie., 7 ago. 2020 a las 19:28, Eric Broch 
(mailto:ebr...@whitehorsetc.com>>) escribió:


optimize dspam also...

 # mysql  -u dspam -p dspam <
/usr/share/dspam/sql-scripts/mysql/purge-4.1.sql

On 8/7/2020 4:24 PM, Eric Broch wrote:


what's this yield

# ls -la /var/log/clamd

On 8/7/2020 4:19 PM, Diego Piñon Conde wrote:

Same error

systemctl start clamd@scan
Job for clamd@scan.service  failed
because a timeout was exceeded. See "systemctl status
clamd@scan.service " and
"journalctl -xe" for details.

El vie., 7 ago. 2020 a las 19:08, Eric Broch
(mailto:ebr...@whitehorsetc.com>>)
escribió:

run the following and try to restart clamd@scan

curl -o /etc/clamd.d/scan.confhttps://raw.githubusercontent.com/qmtoaster/scripts/master/scan.conf  


On 8/7/2020 4:05 PM, Diego Piñon Conde wrote:

 systemctl start clamd@scan       Job for
clamd@scan.service  failed
because a timeout was exceeded. See "systemctl status
clamd@scan.service " and
"journalctl -xe" for details.

Did Not start

El vie., 7 ago. 2020 a las 18:44, Eric Broch
(mailto:ebr...@whitehorsetc.com>>) escribió:

don't stop it. allow it to go until it starts.
sometimes it takes quite a while.

On 8/7/2020 3:39 PM, Diego Piñon Conde wrote:


systemctl start clamd@scan

freeze and do nothing

# ls -ld /var/log/dspam

/drwxrwx--- 2 dspam mail 81 Feb 18 03:57
/var/log/dspam/

# ls -la /var/log/dspam /
/

/total 10256
drwxrwx---   2 dspam    mail       81 Feb 18 03:57 .
drwxr-xr-x. 16 root     root     4096 Aug  7 17:53 ..
-rw-r--r--   1 dspam    mail        0 Feb 18 03:57
sql.errors
-rw-rw   1 vpopmail mail 10493507 Feb 18 01:53
sql.errors-20200218
-rw---   1 dspam    mail        0 Feb 18 03:57
sql.errors-20200218.gz/






El vie., 7 ago. 2020 a las 18:31, Eric Broch
(mailto:ebr...@whitehorsetc.com>>) escribió:

What's the output of the following commands?

# ls -ld /var/log/dspam

and

# ls -la /var/log/dspam

On 8/7/2020 2:46 PM, Diego Piñon Conde wrote:

This is  the only weird message i can repeated
times see from now
[00 ]Aug  7 17:40:54 pegasus dspam[19962]:
Unable to open file for writing:
/var/log/dspam/sql.errors: Permission denied
[00]Aug  7 17:40:55 pegasus dspam[19962]:
bailing on error -2
[00]Aug  7 17:40:55 pegasus dspam[19962]:
received invalid result (!DSR_ISSPAM &&
!DSR_ISINNOCENT): -2
[00]Aug  7 17:40:55 pegasus dspam[19962]:
process_message returned error -5.  delivering.

I 'm still looking

El vie., 7 ago. 2020 a las 17:06, Philip Nix
Guru (mailto:phi...@ows.ch>>)
escribió:

Hello

a

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread Eric Broch 
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:21 I guess because at that time is the 
last error for dspam. I keep searching the mail log for more errors.


Aug  8 08:21:37 pegasus dspam[17546]: query error: Deadlock found when 
trying to get lock; try restarting transaction: see sql.errors for 
more details

Aug  8 08:21:37 pegasus dspam[17546]: bailing on error -2
Aug  8 08:21:37 pegasus dspam[17546]: received invalid result 
(!DSR_ISSPAM && !DSR_ISINNOCENT): -2


clamd@scan still refuse to start, but I'm really don't sure I wanna 
use it. Virus db update takes forever and kill my server for at least 
20 minutes, at least with clamAV version.  I didn't get to test with 
the EPEL version...


Is this the time for enable simscan Eric? Yesterday replace simscan 
with qmail-queue in /etc/tcprules.d/tcp.smtp


El 07/08/2020 a las 11:08 p. m., Eric Broch escribió:


good!

you can run instead:

# dspam_clean -s -p -u

for all users

or

dspam_clean -s -p -u u...@domain.tld us...@domain.tld ... 
us...@domain.tld


for the users you choose.

This will also purge the database.


On 8/7/2020 8:01 PM, Diego Piñon Conde wrote:

/purge-4.1.sql finally ends with no message

El vie., 7 ago. 2020 a las 19:28, Eric Broch 
(mailto:ebr...@whitehorsetc.com>>) escribió:


optimize dspam also...

 # mysql  -u dspam -p dspam <
/usr/share/dspam/sql-scripts/mysql/purge-4.1.sql

On 8/7/2020 4:24 PM, Eric Broch wrote:


what's this yield

# ls -la /var/log/clamd

On 8/7/2020 4:19 PM, Diego Piñon Conde wrote:

Same error

systemctl start clamd@scan
Job for clamd@scan.service  failed
because a timeout was exceeded. See "systemctl status
clamd@scan.service " and
"journalctl -xe" for details.

El vie., 7 ago. 2020 a las 19:08, Eric Broch
(mailto:ebr...@whitehorsetc.com>>)
escribió:

run the following and try to restart clamd@scan

curl -o /etc/clamd.d/scan.confhttps://raw.githubusercontent.com/qmtoaster/scripts/master/scan.conf  


On 8/7/2020 4:05 PM, Diego Piñon Conde wrote:

 systemctl start clamd@scan     Job for
clamd@scan.service  failed
because a timeout was exceeded. See "systemctl status
clamd@scan.service " and
"journalctl -xe" for details.

Did Not start

El vie., 7 ago. 2020 a las 18:44, Eric Broch
(mailto:ebr...@whitehorsetc.com>>) escribió:

don't stop it. allow it to go until it starts.
sometimes it takes quite a while.

On 8/7/2020 3:39 PM, Diego Piñon Conde wrote:


systemctl start clamd@scan

freeze and do nothing

# ls -ld /var/log/dspam

/drwxrwx--- 2 dspam mail 81 Feb 18 03:57 /var/log/dspam/

# ls -la /var/log/dspam /
/

/total 10256
drwxrwx---   2 dspam    mail     81 Feb 18 03:57 .
drwxr-xr-x. 16 root     root   4096 Aug  7 17:53 ..
-rw-r--r--   1 dspam    mail      0 Feb 18 03:57
sql.errors
-rw-rw   1 vpopmail mail 10493507 Feb 18 01:53
sql.errors-20200218
-rw---   1 dspam    mail      0 Feb 18 03:57
sql.errors-20200218.gz/






El vie., 7 ago. 2020 a las 18:31, Eric Broch
(mailto:ebr...@whitehorsetc.com>>) escribió:

What's the output of the following commands?

# ls -ld /var/log/dspam

and

# ls -la /var/log/dspam

On 8/7/2020 2:46 PM, Diego Piñon Conde wrote:

This is  the only weird message i can repeated
times see from now
[00 ]Aug  7 17:40:54 pegasus dspam[19962]:
Unable to open file for writing:
/var/log/dspam/sql.errors: Permission denied
[00]Aug  7 17:40:55 pegasus dspam[19962]:
bailing on error -2
[00]Aug  7 17:40:55 pegasus dspam[19962]:
received invalid result (!DSR_ISSPAM &&
!DSR_ISINNOCENT): -2
[00]Aug  7 17:40:55 pegasus dspam[19962]:
process_message returned error -5.  delivering.

I 'm still looking

El vie., 7 ago. 2020 a las 17:06, Philip Nix
Guru (mailto:phi...@ows.ch>>)
escribió:

Hello

a bit hard to debug without checking system

if you got multitail

create a file with :

multitail -Z red,black,inverse -T -S -x "

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

2020-08-08 Thread Diego Piñon Conde 

  
  
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
  errors.
  
  Aug  8 08:21:37 pegasus dspam[17546]: query error: Deadlock found
  when trying to get lock; try restarting transaction: see
  sql.errors for more details
  Aug  8 08:21:37 pegasus dspam[17546]: bailing on error -2
  Aug  8 08:21:37 pegasus dspam[17546]: received invalid result
  (!DSR_ISSPAM && !DSR_ISINNOCENT): -2
  
  clamd@scan still refuse to start, but I'm really don't sure I
  wanna use it. Virus db update takes forever and kill my server for
  at least 20 minutes, at least with clamAV version.  I didn't get
  to test with the EPEL version...
  
  Is this the time for enable simscan Eric? Yesterday replace
  simscan with qmail-queue in /etc/tcprules.d/tcp.smtp


El 07/08/2020 a las 11:08 p. m., Eric
  Broch escribió:


  
  good!
  you can run instead: 
  
  # dspam_clean -s -p -u 
  
  for all users
  
  or 
  
  dspam_clean -s -p -u u...@domain.tld
us...@domain.tld
... us...@domain.tld
  for the users you choose.
  This will also purge the database.
  
  
  
  On 8/7/2020 8:01 PM, Diego Piñon
Conde wrote:
  
  

/purge-4.1.sql finally ends with no message



  El vie., 7 ago. 2020 a las
19:28, Eric Broch ()
escribió:
  
  

  optimize dspam also...
  
   # mysql  -u dspam -p dspam <
/usr/share/dspam/sql-scripts/mysql/purge-4.1.sql
  
  On 8/7/2020 4:24 PM, Eric Broch wrote:
  
  
what's this yield
# ls -la /var/log/clamd
On 8/7/2020 4:19 PM, Diego Piñon Conde wrote:


  
Same error


systemctl start clamd@scan
  Job for clamd@scan.service
  failed because a timeout was exceeded. See
  "systemctl status clamd@scan.service"
  and "journalctl -xe" for details.

  
  
  
El vie., 7 ago.
  2020 a las 19:08, Eric Broch ()
  escribió:


  
run the following and try to restart
  clamd@scan
curl -o /etc/clamd.d/scan.conf https://raw.githubusercontent.com/qmtoaster/scripts/master/scan.conf 


On 8/7/2020 4:05 PM, Diego Piñon Conde
  wrote:


  
 systemctl start clamd@scan            
    Job for clamd@scan.service
  failed because a timeout was exceeded. See
  "systemctl status clamd@scan.service"
  and "journalctl -xe" for details.


Did Not start

  
  
  
El vie., 7
  ago. 2020 a las 18:44, Eric Broch ()
  escribió:


  
don't stop it. allow it to go until
  it starts. sometimes it takes quite a
  while.

On 8/7/2020 3:39 PM, Diego Piñon
  Conde wrote:


  
systemctl start clamd@scan
 freeze and do nothing 
# ls -ld /var/log/dspam
drwxrwx--- 2 dspam mail 81 Feb
18 03:57 /var/log/dspam
 # ls -la /var/log/dspam 
  
total 10256
drwx