Search found 11 matches
- 13 Jul 2021 13:03
- Forum: 4.x Bugs
- Topic: daily upgrade 12.7.
- Replies: 14
- Views: 11783
Re: daily upgrade 12.7.
Same problem here. I think the upgrade for MariaDB 10.1 to 10.2 is a major upgrade and needs an uninstall of MariaDB 10.1...
- 13 Apr 2021 14:54
- Forum: Discussion
- Topic: A bit puzzled about Lets Encrypt and its function?
- Replies: 2
- Views: 4009
Re: A bit puzzled about Lets Encrypt and its function?
I did it this way: Create a script /etc/cron.weekly/postfix-cert-update.cron: !/bin/bash # Update the postfix certificates from Apache2 echo Updating Postfix SSL certificate from Apache website echo Checking if Apache certificate is newer than Postfix certificate.... if [[ "$(cp -uv /etc/letsen...
- 23 Oct 2020 20:15
- Forum: 4.x Bugs
- Topic: SA Learn error
- Replies: 27
- Views: 93828
Re: SA Learn error
I had the same issue. I've fixed it with the following steps: 1. Into the file /var/spool/postfix/.razor/razor-agent.conf add the line razorhome = /var/spool/postfix/.razor 2. Into the file /etc/MailScanner/spamassassin.conf add the following section ifplugin Mail::SpamAssassin::Plugin::Razor2 razo...
- 23 Oct 2020 20:11
- Forum: 4.x Bugs
- Topic: SA Learn error
- Replies: 27
- Views: 93828
Re: SA Learn error
@hunter-nl: This solution works!
- 07 Oct 2020 11:51
- Forum: 4.x Bugs
- Topic: SA Learn error
- Replies: 27
- Views: 93828
Re: SA Learn error
I still have this problem, while my EFA version is upgraded: "MailWatch for MailScanner v1.2.15 running on eFa-4.0.3 - © 2006-2020."
How can I remove this error? I tried Henk's steps, but it did not work.
How can I remove this error? I tried Henk's steps, but it did not work.
- 01 May 2020 07:50
- Forum: 4.x Bugs
- Topic: Cron job are not running
- Replies: 18
- Views: 47398
Re: Cron job are not running
I have an equal problem:
/etc/cron.hourly/0yum-hourly.cron:
Could not get metalink https://mirrors.fedoraproject.org/metal ... ent=centos error was
14: curl
/etc/cron.hourly/0yum-hourly.cron:
Could not get metalink https://mirrors.fedoraproject.org/metal ... ent=centos error was
14: curl
- 25 Feb 2020 08:30
- Forum: 4.x Bugs
- Topic: ERROR: eFa4 failed to install
- Replies: 21
- Views: 16697
Re: ERROR: eFa4 failed to install
I have the same error from the cron update job:
/etc/cron.daily/0yum-daily.cron:
Failed to check for updates with the following error message:
Failed to build transaction: 1:eFa-4.0.2-7.eFa.el7.x86_64 requires clamav-server >= 0.101.0-1
/etc/cron.daily/0yum-daily.cron:
Failed to check for updates with the following error message:
Failed to build transaction: 1:eFa-4.0.2-7.eFa.el7.x86_64 requires clamav-server >= 0.101.0-1
- 05 Oct 2017 20:30
- Forum: 3.x Bugs
- Topic: Learn+Report - Razor2 Error (Resolved?)
- Replies: 2
- Views: 4587
Re: Learn+Report - Razor2 Error (Resolved?)
Yes, yes, after trying a lot of other things, this finally did help!
I also have a hyper-v iso.
I also have a hyper-v iso.
- 09 Feb 2017 13:52
- Forum: 3.x Bugs
- Topic: GEOIP download problem sice update to 3.0.1.8
- Replies: 4
- Views: 5526
GEOIP download problem sice update to 3.0.1.8
Since the upgrade to 3.0.1.8, I get this error while updating de GEOIP databases: Downloading file, please wait... Error occurred while downloading GeoIP IPv4 data file: cURL error 7: Failed to connect to 2400:cb00:2048:1::6810:262f: Network is unreachable Error occurred while downloading GeoIP IPv6...
- 10 Sep 2016 13:24
- Forum: 3.x Bugs
- Topic: UNTRUSTED NETWORK: Message not reported as Spam
- Replies: 9
- Views: 8031
Re: UNTRUSTED NETWORK: Message not reported as Spam
I deleted the whole list and was playing with it. After some time I noticed that this is working: 172.16.0.6255.255.255.255 172.16.0.38 IP DOES NOT MATCH SUBNET 192.168.2.254 255.255.255.255 172.16.0.38 IP DOES NOT MATCH SUBNET 172.16.0.0 255.255.255.0 172.16.0.38 IP MATCHES SUBNET 192.168.2.0 255.2...
- 08 Sep 2016 08:35
- Forum: 3.x Bugs
- Topic: UNTRUSTED NETWORK: Message not reported as Spam
- Replies: 9
- Views: 8031
Re: UNTRUSTED NETWORK: Message not reported as Spam
I have the same problem and run the script:
172.16.0.0 255.255.0.0
172.16.0.38
IP DOES NOT MATCH SUBNET
This looks like a bug: it should be trusted but it isn't!
172.16.0.0 255.255.0.0
172.16.0.38
IP DOES NOT MATCH SUBNET
This looks like a bug: it should be trusted but it isn't!