Recent content by jvdwilk

well... DirectAdmin Support has a different view on that then CloudLinux Support. I opened a ticket on Cloudlinux 9 today with DirectAdmin Support, and got my answer:

Hi, I had the same issue, after OS update (CloudLinux) and updating all pending DA custombuild software rspamd would not start anymore. Fixed it by running da build exim_conf after that I could start rspamd 3.7.4 just fine...

of je stopt de stekker er in... (or you plug in into a socket) Well... with DA support I was able to find the bug... it was located between my ears. I never realised that the setting for 'key length' in the GUI when creating a new SSL keypair also controlled the cipher type. But it does. All I...

Suspecting some bugs now, either in DA or in the letsencrypt.sh script. This is going over my head now: cd /usr/local/directadmin/scripts ./letsencrypt.sh request_full <test_account_domain_name> 4096 is giving warnings on the <test_account_domain_name> subdomains ./letsencrypt.sh request_full...

Really scratching my head now. Even when I create a new hosting account (for testing) and generate a Let's Encrypt certificate for it, it does not get any RSA based ciphers, while earlier the ./letsencrypt.sh request_single your.hostname.com 4096 did give me a certificate with RSA based ciphers.

Yes, that. Exactly that. Thank you Richard ..! A lot! nmap --script ssl-enum-ciphers -p 465 localhost Starting Nmap 7.70 ( https://nmap.org ) at 2021-10-24 11:11 UTC Nmap scan report for localhost (127.0.0.1) Host is up (0.000070s latency). Other addresses for localhost (not scanned): ::1 PORT...

Nope, not that... : nmap --script ssl-enum-ciphers -p 465 localhost Starting Nmap 7.70 ( https://nmap.org ) at 2021-10-22 23:05 UTC Nmap scan report for localhost (127.0.0.1) Host is up (0.000095s latency). Other addresses for localhost (not scanned): ::1 PORT STATE SERVICE 465/tcp open...

I am trying to get a working 'autodiscover' for my hosting servers. Seeing a consistent failing from the Windows 10 'Mail' client, which relies on the 'autodiscover' of Outlook, while my 'autodiscover' works fine with older MS Outlook clients, I started testing my 'autodiscover' with Microsofts...

I was running into the same situation yesterday, also trying to get autodiscover working, and only got it to work after I started tinkering with with rules in the .htaccess file It started working for me when I changed the fore-last line in the .htaccess file: RewriteEngine On RewriteCond...

yes, well... you make it sound very obvious and simple, but I am afraid I have no idea how to fix this, so reporting it here for 'fixing' ..?

While running a regular update from shell, I am seeing a blocking error message on the ClamAV installation: Installing clamav 0.104.0 ... Found /usr/local/directadmin/custombuild/clamav-0.104.0.tar.gz Extracting ... Done. Configuring clamav 0.104.0 ...

@bdacus01 - _most_ of my emails also send fine. Only some of them sit in the queue for a longer time. It's only these emails this forum question is about. And this longer time used to be up to an hour, but with changing the queue runner re-spawn time (-q1h => -q5m) it solves a large part of the...

What Richard is asking is exactly what I wat wondering about also. What is the reason for these mails to not being send out immediatelly? @Peter Laws , there is no reason listed with the messages I am talking about. These message are accepted by Exim for delivery, and then nothing. No defer, no...

Yes, thank you for pointing that out. I had kind of read through the exim man pages, but you focussed in exactly on the important parts. I have found where the -q1h came from. It's the /etc/systemd/system/exim.service script, which starts the exim service. Changing it should be easy, but I fail...

Using a fresh server setup, running CloudLinux 8 and Exim 4.94 All software up-to-date, running with just a few test domain, this new server is to become a new production server. Now, when sending emails, usually things just work as expected. But then sometimes they don't. Especially when the...