Net::DNS 1.03 breaks compatibility with SpamAssassin:
DNS lookups no longer work, and warnings like the following pop up:
lookup failed: Can't locate object method "handles" via package
"IO::Socket::IP"
at /usr/local/lib/perl5/site_perl/Net/DNS/Resolver/Base.pm line 735.
There is a CPAN
On 2015-11-12 08:20, Bowie Bailey wrote:
On 11/12/2015 6:31 AM, Christian Jaeger wrote:
Hi
I'm seeing X-Spam-Status headers from some other installation come
with =$x appended to the individual matches, which evidently helps
figuring out why a mail is being classified the way it is. I've spent
On 11/12/2015 6:31 AM, Christian Jaeger wrote:
Hi
I'm seeing X-Spam-Status headers from some other installation come
with =$x appended to the individual matches, which evidently helps
figuring out why a mail is being classified the way it is. I've spent
more than an hour on googling and rtfm but
On Tue, 10 Nov 2015 10:45:03 +
Phil Reynolds wrote:
> On Mon, 9 Nov 2015 13:23:04 +
> Phil Reynolds wrote:
>
> > I have recently transferred all of my email system to a new machine,
> > but spamassassin is not yet fully functional.
> >
> > It seems that it is trying to use /var/mail/.s
On 11/12/2015 12:31 PM, Christian Jaeger wrote:
Hi
I'm seeing X-Spam-Status headers from some other installation come
with =$x appended to the individual matches, which evidently helps
figuring out why a mail is being classified the way it is. I've spent
more than an hour on googling and rtfm bu
Hi
I'm seeing X-Spam-Status headers from some other installation come
with =$x appended to the individual matches, which evidently helps
figuring out why a mail is being classified the way it is. I've spent
more than an hour on googling and rtfm but couldn't figure it
out. Also, grep does not turn
