This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Update 9.706 spamd error

spam acl condition: warning - spamd connection to 127.0.0.1, port 25315 failed: Connection refused

spam acl condition: all spamd servers failed



This thread was automatically locked due to age.
Parents
  • If this is a paid license, you should open a Support case.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Well, home license. So i guess no one cares. This problem appeared after the update to 9.706 . 

    So maybe someone will keep an eye on it.

    Man, i miss the good old Astaro times....

  • Error still exists:

    2021:05:14-17:30:59 hostname exim-in[24846]: 2021-05-14 17:30:59 1lhZlv-0006Sk-0L spam acl condition: spamd: failed to connect to any address for 127.0.0.1: Connection refused
    2021:05:14-17:30:59 hostname exim-in[24846]: 2021-05-14 17:30:59 1lhZlv-0006Sk-0L spam acl condition: all spamd servers failed

  • Hello WolfgangS,

    Thank you for contacting the Sophos Community.

    I have created a case on your behalf and send it to GES for feedback, once I hear back from them I will update you via PM.

    Regards


     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support VideosProduct Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
  • Well they simply changed the hyperscan to a new version, so the solution for the "customer" is: buy new hardware, we don't support AMD .

    well... not mutch to say about this ...

    This is the update from GES.

    Looks like the customer's gonna need a new CPU.

    Having a hard time finding the HCL, we only support Intel CPUs (maybe this is old/outdated).

    As per the log (also shows up when trying to manually start sasi):

    --------------------------------

    2021-05-25.22:20:24 ERROR [9999] [ laseserver.cpp:159] Could not fetch new signatures: Unable to load database :Database exception: Hyperscan Platform Validation Error : System Does Not Support SSSE3 Instruction Set , Hyperscan can not run:/var/pattern/sasi/asdb.antispam Exiting..

    --------------------------------

    Checking the features the customer's CPU supports (no ssse3):

    AMD Athlon(tm) II X2 270 Processor

Reply
  • Well they simply changed the hyperscan to a new version, so the solution for the "customer" is: buy new hardware, we don't support AMD .

    well... not mutch to say about this ...

    This is the update from GES.

    Looks like the customer's gonna need a new CPU.

    Having a hard time finding the HCL, we only support Intel CPUs (maybe this is old/outdated).

    As per the log (also shows up when trying to manually start sasi):

    --------------------------------

    2021-05-25.22:20:24 ERROR [9999] [ laseserver.cpp:159] Could not fetch new signatures: Unable to load database :Database exception: Hyperscan Platform Validation Error : System Does Not Support SSSE3 Instruction Set , Hyperscan can not run:/var/pattern/sasi/asdb.antispam Exiting..

    --------------------------------

    Checking the features the customer's CPU supports (no ssse3):

    AMD Athlon(tm) II X2 270 Processor

Children
No Data