Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 39 replies
  • Subscribers 1 subscriber
  • Views 22374 views
  • Users 0 members are here
Options
Suggested
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

malware acl condition: weed: scanning failed

drees
Just started seeing this along with emails that say "virus scanner aveserver daemon not running - restarted". Email gets stuck as a result.

Disabling the virus scanner gets email flowing again. Looks like an old problem resurfaced? https://community.sophos.com/products/unified-threat-management/astaroorg/f/68/t/61969


This thread was automatically locked due to age.
Parents
  • 0
    You could manually try clearing the exim queue: exim -qff

    As for the bug ... since Astaro licenses Kaspersky obviously the license had expired. I think this has happened before back in 3.2 and 4.0 days.

    Was the Up2Date just purely coincidental or did it trigger the license expiry?

    Also - the patch 5.211 doesn't immediately fix the problem for me. I did this.

    - apply patch
    - re-enable A/V in SMTP Proxy if disabled

    EXIM reloads but still doesn't accept mail. So I:

    - manually ran Up2Date (no change)
    - restart SMTP Proxy (working!!)

     
  • 0 in reply to James Bourne
    Can someone confirms that this works?

    I tried it,but i get errors when i run exim this way:


    ./exim: error while loading shared libraries: libsmtp_helper.so.0: cannot open shared object file: No such file or directory
  • 0 in reply to dayvid
    [ QUOTE ]
    Can someone confirms that this works?

    I tried it,but i get errors when i run exim this way:


    ./exim: error while loading shared libraries: libsmtp_helper.so.0: cannot open shared object file: No such file or directory 

    [/ QUOTE ]
    I get the same errors.... so it seems that is not the correct solution!
  • 0 in reply to SveN_01
    Exim runs in a chroot environment so you have to start it correctly otherwise it won´t work.

    so the correct command would be:

    chroot /var/chroot-smtp exim -qff

    or use

    chroot /var/chroot-smtp exim -d -qff to start exim in debug mode and look what it does
  • 0 in reply to AstaroKult
    I tried chroot /var/chroot-smtp exim -qff, which didn't give any errors, but I've still got a mess of email in both the input and scan directories. 

    Using the -d arguement doesn't show any errors or problems with exim loading up.

    Any other ideas to release these messages?
  • 0 in reply to Mateo
    Actually this is a false alarm. I edited some of the messages to see what they contain, and the user did in fact receive the message. For whatever reason it wasn't removed from the input/scan directories after delivery.

    Is it safe to delete all the files in these directories?
  • 0 in reply to Mateo
    I need to hear from a astaro rep that the mails are send before i delete them.
    Or a way to resend them.
    I tried the above resolution, but nothing changed.
  • 0 in reply to dayvid
    I checked some of them (asked the users),
    and it seems that they were send....
    But why are they stuck???
Reply Children
No Data
Cookie Information Banner