> 
> spamass-milter isn't part of the Spamassassin project and is
> unmaintained by its upstream [https://github.com/andybalholm/spamass-
> milter], so you may have limited support opportunities here.
> 
> What you're seeing here is that the Fedora/EPEL "spamass-milter" package
> has a strong dependency on the complete "spamassassin" package (and thus
> all of its dependencies).  The package maintainer presumably expects
> that spamassassin is running in the same execution domain as your MTA,
> rather than a separate container.
> 
> You could rebuild the spamass-milter package from source, removing the
> spamassassin dependency from the spec file, to avoid this.  You can also
> submit RFE's against this component via this Bugzilla:
> https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGN
> ED&classification=Fedora&component=spamass-
> milter&product=Fedora&product=Fedora%20EPEL

Hi Jered, thanks, indeed I rebuild from source but had to add the spamc binary.

Reply via email to