Axigen stops sending & receiving after 10.6.1 - Possible BitDefender Issue

1

Hi,

Since upgrading from 10.6.0 to 10.6.1 Axigen has stopped sending and receiving.

Looking at the log file I see this failure information on an email:

Fail Info
Filter BD(127.0.0.1:1344):[ERROR]: Could not connect to filter

I assume BD is BitDefender. BitDefender is not enabled and greyed out. I’m unable to neither enable it (understandable as I have the free version of Axigen) or disable it. Yet the error message above appears to suggest BitDefender is the issue.

Can I force disable BD using CLI, and if so, what is the command?

Or is there a conf file I need to check?

I recall in the readme notes for 10.6.1. that there was an issue with the enable button for BD in 10.6.0. Have I somehow found myself with an “enabled” BitDefender filter without BitDefender being installed?

Thanks.
A.

2

Excerpt from log file:

PROCESSING:0020177C: Shepherd thread received signal for processing
PROCESSING:0020177C: Set recipient name@example.com state to RECEIVED
PROCESSING:0020177C: Set mail state to PROCESSING
PROCESSING:0020177C: Start processing mail
PROCESSING:0020177C: Set recipient name@example.com state to PROCESSING
PROCESSING:0020177C: Start filter AV:Bitdefender of type socket filter from server
PROCESSING:0020177C: Processing started
PROCESSING:0020177C: Shepherd thread finished processing signal
PROCESSING:0020177C: Filter BD(127.0.0.1:1344):[ERROR]: Could not connect to filter
PROCESSING:0020177C: Error connecting to socket filter: BD(127.0.0.1:1344)
PROCESSING:0020177C: Finished filtering mail object 20177C with filter: AV:Bitdefender of type socket filter from server
PROCESSING:0020177C: Set recipient name@example.com state to PROCESSING ERROR
PROCESSING:0020177C: Set mail state to PROCESSING ERROR
PROCESSING:0020177C: Processing finished

It seems Axigen is trying to use Bitdefender even though Bitdefender is not installed and not enabled.

3

For others who may follow the same path as I have, I may have resolved the issue.

Somewhere along the way the following lines were added to: /var/opt/axigen/run/axigen.cfg …

    {
        filterName = "AV:Bitdefender"
        filterType = socket
        priority = 4
        applyOn = (local relay)
    }

… in the …

serverActiveFilters = (

section of the file.

I stopped Axigen, made a backup of the axigen.cfg file, deleted the Bitdefender section, saved the file and restarted Axigen.

I gave the 100+ emails stuck in the email queue an nudge and they all “left the building”.

I think the issue began in 10.6.0 and somehow the Bitdefender filter was made active even though it wasn’t installed. The problem was made worst since the ‘enable’ button in the GUI was non-funtional in 10.6.0 and greyed out in 10.6.1, so no way to toggle the button.

Fingers crossed the issue is resolved.

Cheers
A.

4

Hello @AdrianW

Bitdefender integration has 2 components, a service and a filter, in your case the issue is the filter that is enable.

To disable the filter from CLI please use the below commands:

<#> config server
<server#> CONFIG FILTERS
<server-filters#> REMOVE ActiveFilter 3
<server-filters#> commit
<server#> save config
<server#> commit
<#> quit

Regards,
Florin

5

Thanks Florin,

I ran the CLI commands above and it actually disabled SpamAssassin. I suspect this is because I had already manually removed the AV:Bitdefender lines in ‘axigen.cfg’. Not a problem. I went back to WebAdmin and re-enabled SpamAssassin.

I sent/received a bunch of test emails and everything seems to be working fine.

Thank you for your assistance.

On a related note, I’m trying to get ClamAV working with Axigen but not having much joy. I’ll post this in a separate thread.