Topic: Spamassassin

[p-jones]

Have updated a V7.4 to V8 but have the following message in YUM. 

Have done a search of the forums and bug tracker. I understand that fuzzyocr should be dealt to in the update. That doesnt seem to be the case here. I dont know where to go or what to do to resolve this and any help would be appreciated.

Thanks in advance.
Peter


Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package smeserver-spamassassin.noarch 0:2.2.0-13.el5.sme set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package                     Arch        Version               Repository  Size
================================================================================
Installing:
 smeserver-spamassassin      noarch      2.2.0-13.el5.sme      smeos       27 k
     replacing  FuzzyOcr.noarch 3.5.1-3.el4.sme


Transaction Summary
================================================================================
Install       1 Package(s)
Upgrade       0 Package(s)

Total download size: 27 k
Is this ok [y/N]: y
Downloading Packages:
smeserver-spamassassin-2.2.0-13.el5.sme.noarch.rpm       |  27 kB     00:00
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing     : smeserver-spamassassin                                   1/3
Error unpacking rpm package smeserver-spamassassin-2.2.0-13.el5.sme.noarch
error: unpacking of archive failed on file /etc/e-smith/templates/etc/mail/spamassassin/local.cf/50pyzor_timeout: cpio: rename
Migrating existing database mailpatterns
Migrating existing database accounts
Migrating existing database yum_installed
Migrating existing database domains
Migrating existing database yum_updates
Migrating existing database yum_available
Migrating existing database backups
Migrating existing database hosts
Migrating existing database yum_repositories
Migrating existing database configuration
Migrating existing database spamassassin
Migrating existing database networks

Replaced:
  FuzzyOcr.noarch 0:3.5.1-3.el4.sme

Failed:
  smeserver-spamassassin.noarch 0:2.2.0-13.el5.sme

Complete!

==============================================================
WARNING: You now need to run BOTH of the following commands
to ensure consistent system state:

signal-event post-upgrade; signal-event reboot

You should run these commands unless you are certain that
yum made no changes to your system.
==============================================================
[root@server ~]#

[guest22]

Transaction Test Succeeded
Running Transaction
  Installing     : smeserver-spamassassin                                   1/3
Error unpacking rpm package smeserver-spamassassin-2.2.0-13.el5.sme.noarch
error: unpacking of archive failed on file /etc/e-smith/templates/etc/mail/spamassassin/local.cf/50pyzor_timeout: cpio: rename

Failed:
  smeserver-spamassassin.noarch 0:2.2.0-13.el5.sme

That looks like a bad package (maybe a bit fell over) . Can you try installing manually again:

yum install smeserver-spamassasin --enablerepo=smecontribs

OR

download download the package from a different mirror and 'yum localinstall'

[Daniel B.]

Check /etc/e-smith/templates/etc/mail/spamassassin/local.cf/50pyzor_timeout doesn't already exists on your server as a directory

[p-jones]

Yes it does exist as a directory. I renamed it and ran the update again and it went throgh OK but I seem to have created a new issue whereby cannot send out any email via IMAP.

Server refuses to accept the connection from thunderbird. Yes I have checked the theunderbird SMTP settings.

Getting urgent now. it is a show stopper.

[guest22]

Server refuses to accept the connection from thunderbird. Yes I have checked the theunderbird SMTP settings.

What do the various log files say?

[p-jones]

The only error I could find was in qpsmtpd that authentication had failed - something I already knew from the thunderbird client  messages. People were able to logon though.

I found reseting a user password on the server to the same password they had logged on with sorted it.

In the end, I had everyone do a password reset and the issue was resolved.

I dont know if this is a result of removing fuzzyocr or whether it is a seperate issue, maybe something getting corrupted or ??? I was told after the update the email was working. I didnt check it myself and am leaning towards thinking I may have been give some bad info.

What I do know is I upgraded another system a while back using the same Cd and it went like clockwork. No issues at all.