Hi
I'm try to configure this plugin.
The plugin works fine in the sense from the logs i can see the associated rule is correctly matched
What i'm expecting from this plugin once matched is that the offending uri will be removed by the message with a customized replacement url.
Of course this...
There is no need to patch che cose in order to implement new av engine.
The dev team has done a good job in creating support for external scanner by using an external script interface
Sorry but this is only yours as a problem.
Technicaly speaking pmg-smtp-filter is a content filter and opendkim is a milter which should work together by design. I suggest to analyze in deep your issue,maybe with the help of proxmox support. I've both pmg-smtp-filter and a lot of milters running...
For outgoing traffic is supposed that pmgpolicy is not enabled at all, or at least you could disable it. Anyway you could decide to use postfwd you after pmgpolicy so traffic not blocked by pmgpolicy could be evaluated by postfwd.
SpamAssassin runs embedded in pmg-smtp-filter so, in order to refresh spamassassin conf you need to restart this service. Do a 'systemctl restart pmg-smtp-filter' and you should be fine.
There's no a native way to convert tnef/wimail.dat in txt file built in in pmg stuff.
One (not so simple) way to implement it is via mimedefang, which is btw a milter which will be plugged in postfix and come just before the pmg filtering engine (pmg-smtp-filter service).
Here a link to...
The initial implementation of avast support was suggested by me so what I would suggest to you is to move the discussion on pmg-devel mailing list.
Adding av support to pmg-smtp-filter is always tricky because it didn't have a general interface to plug external scanners like amavis have.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.