Applying custom scores kills all connections

[anoniempje]

Hi,

When making a change in de PMG/Spam detector settings such as adding a custom score for a spamassassin rule, as soon as you apply the new rules it will disconnect all connections what makes my mailbox flow over with mail errors,

Is it possible to make to config reload instead of breaking the current active connections?

Kind regards,

W.

Ps. The content of this mail holds this:

Transcript of session follows.

Out: 220 pmg01.*****REDACTED***** ESMTP *****REDACTED*****
In:  EHLO web00*****REDACTED*****
Out: 250-pmg01.*****REDACTED*****
Out: 250-PIPELINING
Out: 250-SIZE 104857600
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250-DSN
Out: 250-SMTPUTF8
Out: 250 CHUNKING
In:  STARTTLS
Out: 220 2.0.0 Ready to start TLS
In:  EHLO web00*****REDACTED*****
Out: 250-pmg01.*****REDACTED*****
Out: 250-PIPELINING
Out: 250-SIZE 104857600
Out: 250-VRFY
Out: 250-ETRN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250-DSN
Out: 250-SMTPUTF8
Out: 250 CHUNKING
In:  MAIL FROM:<*****REDACTED*****@*****REDACTED*****.*****REDACTED*****> SIZE=2218
Out: 250 2.1.0 Ok
In:  RCPT TO:<*****REDACTED*****@*****REDACTED*****.*****REDACTED*****>
Out: 250 2.1.5 Ok
In:  BDAT 2057 LAST
Out: 451 4.3.0 Error: queue file write error
In:  QUIT
Out: 221 2.0.0 Bye


For other details, see the local mail logfile

 

[hata_ph]

Pls show the custom spamassassin score rule.

 

[anoniempje]

It doesn't matter what custom score you enter, once you apply the configuration it will kill these connections.

 

[Stoiko Ivanov]

check your journal - it seems pmg-smtp-filter is not running - this is nothing common - there should be a hint in the journal why it is not working

I hope this helps!

 

[anoniempje]

check your journal - it seems pmg-smtp-filter is not running - this is nothing common - there should be a hint in the journal why it is not working

I hope this helps!

Hi Stoiko,

It is working except when you apply the newly entered spamassassin custom rules and once you hit apply/restart pmg-filter service it will kill all the current active connections throwing the error i gave in my first message.

it would be nice'r if the connections where not killed but kept active and the services reloaded so all active connections can be handled instead of dropping them.

 

[Stoiko Ivanov]

Can you please share the logs - usually this gets handled gracefully

 

[ittk]

Yes, would be interested to know, and which Mail direction is affected? Incoming or Outgoing or both?

 

[anoniempje]

Hi,

Sorry for the delay. We only have this setup as outgoing mail filter. The traffic that is affected is incoming so:
webserver -> proxmox mail gateway -> external receiver.

The connection between the webserver and the proxmox mail gateway gets aborted.
I will try to capture some logs later today or next week.