Search results

What about adding your own header if the mail is sent from your own system? Something like: acl_check_message: warn add_header = X-MyOutGoingHeader: <some value> When receiving a new mail and if the reply-to is used, the mail will contain a 'In-Reply-To' header. Just thinking out loud now...

Use an acl in exim -> https://serverfault.com/questions/576983/blocking-outgoing-mails-to-some-users-in-exim

Sssst, I was storing my adult stuff up there. :)

Well, the password you show is at least correct... Try to enable Secure FTP (and change your password....)

Just took a quick look at the php source code and I'm wondering if a simple solution would work to change the fpm_children.c function fpm_children_make() where a child is forked and after a successful fork simply write the child pid to the required cgroup.procs. That would prevent the need to...

Well, how I've done it, works good enough for me because I don't have to change the php code. (I still once in a while have nightmares about the apache itk mod). By moving the root php-fpm process (one pid only used when the fpm service is started) will have all subsequent user fpm processes...

This worked for me: https://forum.directadmin.com/threads/how-to-mod_pagespeed-for-apache.58132/

Well, not with the default user slice but that's only for users logging in using ssh e.g. For php-fpm you'll need to do something else, but that's not that hard either. Systemd uses templates like '[email protected]'. You'll need toch use this to start the 'root' fpm-php process for each user...

CentOS 6 went EOL on November 30, 2020.

https://blog.cloudlinux.com/announcing-open-sourced-community-driven-rhel-fork-by-cloudlinux

Yeah, that sucks too.

Well, as 'linux' is actually just a kernel and the tools round it are defined by the distro, FreeBSD might be a good, secure, fast and complete OS to shift the focus to.

That's what I did. The network.target isn't very reliable since CentOS 8. I have to say that I just grep'ed the /var/log/messages file for 'Started', named was the last item, so I used that in the service file.

Yups, and yes, it's a minor bug.

I changed it to: [Unit] Description=DirectAdmin Web Control Panel After=syslog.target network.target named.target So it starts after named. This makes it start successfully the first time.

Yups, I did the same. I see it trying to start 5 times. Dec 9 18:12:34 xxx systemd[1]: directadmin.service: Scheduled restart job, restart counter is at 1. Dec 9 18:12:35 xxx systemd[1]: directadmin.service: Scheduled restart job, restart counter is at 2. Dec 9 18:12:35 xxx systemd[1]...

Wel, that sucks... Time test ubuntu/debian, maybe even back to freebsd.

Compare specs and maybe even beter, compare traceroutes (If you still have soms from the previous hoster). It the new hoster is migrating a lot of vm's to his own system, it's not that hard to believe they might have hit their own limits (overused storage, bandwidth limitations, hardware...

Maybe this helps: https://openlitespeed.org/kb/openlitespeed-modsecurity-module/

If you grep 'google' in assets/apps.js in evolution you'll even find references to pagead2.googlesyndication.com/pagead/js/adsbygoogle.js Not sure what to think about that...