Update to 4.0.2
Update to 4.0.2
Hello.
I tried and failed:
Error: Package: 1:eFa-4.0.2-5.eFa.el7.x86_64 (eFa4)
Requires: MailScanner >= 5.2.2-1
Available: MailScanner-5.1.4-1.efa.3.rhel.noarch (eFa4)
MailScanner = 5.1.4-1.efa.3.rhel
Error: Package: 1:eFa-4.0.2-5.eFa.el7.x86_64 (eFa4)
Requires: MailScanner >= 5.2.2-1
Installing: MailScanner-5.1.4-1.efa.3.rhel.noarch (eFa4)
MailScanner = 5.1.4-1.efa.3.rhel
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
I tried and failed:
Error: Package: 1:eFa-4.0.2-5.eFa.el7.x86_64 (eFa4)
Requires: MailScanner >= 5.2.2-1
Available: MailScanner-5.1.4-1.efa.3.rhel.noarch (eFa4)
MailScanner = 5.1.4-1.efa.3.rhel
Error: Package: 1:eFa-4.0.2-5.eFa.el7.x86_64 (eFa4)
Requires: MailScanner >= 5.2.2-1
Installing: MailScanner-5.1.4-1.efa.3.rhel.noarch (eFa4)
MailScanner = 5.1.4-1.efa.3.rhel
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Update to 4.0.2
Try again in a bit, the mirrors are replicating.
- bikertrash
- Posts: 49
- Joined: 03 Feb 2016 12:53
- Location: San Diego, CA
- Contact:
Re: Update to 4.0.2
Getting the same error this morning since 04:30 PST and still at 08:15 PST... will let it ride until tomorrow morning and see what happens.
Not too worried about though... I'm sure it'll catch up at some point.
Not too worried about though... I'm sure it'll catch up at some point.
"If it ain't broke, it needs a lot more fix'n."
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Update to 4.0.2
yeah the US/Canada mirror is lagging behind. It'll catch up sometime today.
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Update to 4.0.2
I forced an rsync. They should be in sync now. Stupid cron job...
Re: Update to 4.0.2
Hello.
I just removed mirrors from repo and it went OK.
Now I have problem that bayes score is not displayed in mailwatch gui.
Bayes DB seems OK, SA lint test went trough OK, but bayes score is not displayed at all.
Any idea?
I just removed mirrors from repo and it went OK.
Now I have problem that bayes score is not displayed in mailwatch gui.
Bayes DB seems OK, SA lint test went trough OK, but bayes score is not displayed at all.
Any idea?
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Update to 4.0.2
Can you run an SA Lint for me and post the output?
Re: Update to 4.0.2
Bayes is missing.
Also I have SPF_FAIL custom score set to add 5.0 points.
And in other case where I actually got mail with failed SPF it was scored + 0.95 points.
It`s like the prefs file was not evaluated or used at all.
Lint tests: Also byes DB seems quite OK:
I really don`t know what went wrong here
Also I have SPF_FAIL custom score set to add 5.0 points.
And in other case where I actually got mail with failed SPF it was scored + 0.95 points.
It`s like the prefs file was not evaluated or used at all.
Lint tests: Also byes DB seems quite OK:
I really don`t know what went wrong here
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Update to 4.0.2
Can you post the path to your prefs file for me please?
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Update to 4.0.2
Also, can you verify that /etc/mail/spamassassin/MailScanner.conf is symlinked to /etc/MailScanner/spamassassin.conf?
Re: Update to 4.0.2
Prefs are here, default ones:
I have no such file in spamassassin folder:
Code: Select all
[root@as MailScanner]# ls -l
total 724
-rw-r--r-- 1 root root 200 Feb 8 16:52 archives.filename.rules
-rw-r--r-- 1 root root 13 Feb 8 16:52 archives.filename.rules.allowall.conf
-rw-r--r-- 1 root root 7337 Jan 20 00:44 archives.filename.rules.conf
-rw-r--r-- 1 root root 200 Feb 8 16:52 archives.filetype.rules
-rw-r--r-- 1 root root 15 Feb 8 16:52 archives.filetype.rules.allowall.conf
-rw-r--r-- 1 root root 1398 Jan 20 00:44 archives.filetype.rules.conf
drwxr-xr-x. 2 root root 20 Feb 9 12:41 conf.d
-rw-r--r-- 1 root root 44134 Jan 20 00:44 country.domains.conf
lrwxrwxrwx. 1 root root 34 Nov 21 10:41 custom -> /usr/share/MailScanner/perl/custom
-rw-r--r-- 1 root root 4331 Nov 22 17:13 defaults
-rw-r--r--. 1 root root 4330 Nov 21 10:41 defaults.v3
-rw-r--r--. 1 root root 251 Nov 21 10:41 filename.rules
-rw-r--r--. 1 root root 13 Nov 21 10:41 filename.rules.allowall.conf
-rw-r--r--. 1 root root 46 Nov 21 10:41 filename.rules-allow.conf
-rw-r--r-- 1 root root 8120 Jan 18 11:08 filename.rules.conf
-rw-r--r--. 1 root root 45 Nov 21 10:41 filename.rules-deny.conf
-rw-r--r--. 1 root root 117 Nov 21 10:41 filetype.rules
-rw-r--r--. 1 root root 13 Nov 21 10:41 filetype.rules.allowall.conf
-rw-r--r--. 1 root root 1608 Nov 21 10:41 filetype.rules.conf
-rw-r--r-- 1 root root 151284 Feb 8 17:25 MailScanner.conf
drwxr-xr-x. 2 root root 184 Feb 8 16:51 mcp
-rw-r--r--. 1 root root 41 Nov 21 10:41 numeric.phishing.rules
-rw-r--r-- 1 root root 102413 Feb 9 08:05 phishing.bad.sites.conf
-rw-r--r-- 1 root root 102213 Feb 9 08:05 phishing.bad.sites.conf.master
-rw-r--r--. 1 root root 102213 Feb 9 08:05 phishing.bad.sites.conf.master.backup
-rw-r--r--. 1 root root 200 Nov 21 10:41 phishing.bad.sites.custom
-rw-r--r-- 1 root root 22249 Feb 9 08:05 phishing.safe.sites.conf
-rw-r--r-- 1 root root 22046 Feb 9 08:05 phishing.safe.sites.conf.master
-rw-r--r--. 1 root root 22046 Feb 9 08:05 phishing.safe.sites.conf.master.backup
-rw-r--r--. 1 root root 203 Nov 21 10:41 phishing.safe.sites.custom
lrwxrwxrwx 1 root root 30 Feb 8 16:52 reports -> /usr/share/MailScanner/reports
drwxr-xr-x. 2 root root 4096 Feb 8 16:52 rules
-rw-r--r-- 1 root root 12720 Feb 8 16:52 spamassassin.conf
-rw-r--r--. 1 root root 12366 Nov 21 10:37 spamassassin.conf.bak
-rw-r--r--. 1 root root 12370 Nov 21 10:41 spamassassin.conf.v3
lrwxrwxrwx. 1 root root 34 Nov 21 10:41 spam.assassin.prefs.conf -> /etc/MailScanner/spamassassin.conf
-rw-r--r-- 1 root root 1129 Jan 20 00:44 spam.lists.conf
-rw-r--r-- 1 root root 1684 Jan 20 00:44 virus.scanners.conf
-rw-r--r--. 1 root root 1488 Nov 21 10:41 virus.scanners.conf.v3
Code: Select all
[root@as spamassassin]# ls -l
total 44
-rw-r--r-- 1 root root 1287 Feb 8 16:52 init.pre
-rw-r--r--. 1 root root 2379 Nov 4 11:51 local.cf
-rw-r--r--. 1 root root 2380 Nov 21 10:41 local.cf.v3
drwx------. 2 root root 83 Feb 9 08:05 sa-update-keys
-rw-r--r--. 1 root root 2523 Nov 21 10:11 v310.pre
-rw-r--r--. 1 root root 1194 Nov 4 11:51 v312.pre
-rw-r--r--. 1 root root 2412 Nov 21 10:11 v320.pre
-rw-r--r--. 1 root root 1237 Nov 4 11:51 v330.pre
-rw-r--r--. 1 root root 1020 Nov 4 11:51 v340.pre
-rw-r--r--. 1 root root 1303 Nov 21 10:11 v341.pre
-rw-r--r--. 1 root root 1499 Nov 21 10:11 v342.pre
-rw-r--r-- 1 root root 1262 Feb 8 16:52 v343.pre
Re: Update to 4.0.2
Fixed by doing:
Why symlink dissapeared?
Code: Select all
cd /etc/mail/spamassassin/
ln -s /etc/MailScanner/spamassassin.conf mailscanner.cf
systemctl restart mailscanner
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Update to 4.0.2
I see you migrated from v3. It looks like you have the old symlink still as well. Interesting.
Re: Update to 4.0.2
Yeah I did migrate.
So what is the correct symlink?
The one I just created works just fine.
So what is the correct symlink?
The one I just created works just fine.
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Update to 4.0.2
Yeah, the one you created is correct. The other one isn't hurting anything. Not sure why it disappeared, but I will migrate a v3 and update it to try to find out why.
Re: Update to 4.0.2
OK thanks.
But for info, I migrated to V4 and everything was OK.
After 4.0.1 to 4.0.2 bayes stopped working, the rest is OK.
But for info, I migrated to V4 and everything was OK.
After 4.0.1 to 4.0.2 bayes stopped working, the rest is OK.
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Update to 4.0.2
In that case I am going to add a condition to check for this symlink after the update. Hope this helps.
Re: Update to 4.0.2
Yeah, that should do the trick
Re: Update to 4.0.2
Hi.
Updated to new mailscanner and efa and had to this again.
bayes was not working.
Updated to new mailscanner and efa and had to this again.
bayes was not working.
Re: Update to 4.0.2
I had to do this on a brand new install of 4.0.2.
Re: Update to 4.0.2
After the upgrade today
I noticed that the following symbolic link was still missing:
The summary showed the following text:
The /usr/sbin/ms-configure --update will also check for the missing symlink and create it when missing.
It will take some time to complete. After that everything worked fine.
Code: Select all
eFa-4.0.2-13.eFa.el7.x86_64.rpm
MailScanner-5.3.1-1.eFa.3.rhel.noarch.rpm
python2-josepy-1.3.0-2.el7.noarch.rpm
Code: Select all
etc/MailScanner/spamassassin.conf mailscanner.cf
The summary showed the following text:
Code: Select all
To update MailScanner and necessary modules run:
/usr/sbin/ms-configure --update
It will take some time to complete. After that everything worked fine.
“We are stuck with technology when what we really want is just stuff that works.” -Douglas Adams
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Update to 4.0.2
Fixed. Next update will ensure this symlink remains present.
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Update to 4.0.2
Also just FYI, shouldn't need to run ms-configure. eFa dependencies are managed. If you were building your own mailscanner from scratch, then yes. I'll make a note to remove that message from the update package from upstream.