Re: Net::DNS 0.77 / resolv.conf with comments (was: FreeBSD Port: spamassassin-3.4.0_11)

On 28.06.2014, at 15:50, Michael Grimm wrote: > spamassassin-3.4.0_11 and p5-Net-DNS-0.76 worked as expected. After upgrading > to p5-Net-DNS-0.77 I ran into an issue that looked similar to the one > reported above. spamd couldn't be daemonized at start-up (timed out). After > some investigati

Net::DNS 0.77 / resolv.conf with comments (was: FreeBSD Port: spamassassin-3.4.0_11)

On 25.06.2014, at 17:21, Michael Grimm wrote: > On 24.06.2014, at 12:57, Dirk-Willem van Gulik wrote: >> Op 24 jun. 2014, om 12:07 heeft Kurt Jaeger het volgende >> geschreven: >>> If you still see the problem, can you provide more details ? >>> What did you test ? What was the output ? >> >>

Re: FreeBSD Port: spamassassin-3.4.0_11

Op 27 jun. 2014, om 05:21 heeft Adam Weinberger het volgende geschreven: > Both those ports are outdated. That SpamAssassin patch was applied to the > FreeBSD port a week ago, and p5-Net-DNS has also been updated since. > > [root@apnoea ~] pkg info spamassassin p5-Net-DNS > spamassassin-3.4.0

Re: FreeBSD Port: spamassassin-3.4.0_11

On 26 Jun, 2014, at 11:58, Dirk-Willem van Gulik wrote: > Op 26 jun. 2014, om 16:49 heeft Adam Weinberger het > volgende geschreven: >> On 25 Jun, 2014, at 12:07, Robert Fitzpatrick wrote: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7057 >>> I am setting up a new ser

Re: FreeBSD Port: spamassassin-3.4.0_11

Op 26 jun. 2014, om 16:49 heeft Adam Weinberger het volgende geschreven: > On 25 Jun, 2014, at 12:07, Robert Fitzpatrick wrote: >>> Dirk-Willem van Gulik Tuesday, June 24, 2014 5:51 AM >>> Still trying to get to the bottom of it - but seeing issues after todays >>> pkg update. >>> >>>

Re: FreeBSD Port: spamassassin-3.4.0_11

On 25 Jun, 2014, at 12:07, Robert Fitzpatrick wrote: >> Dirk-Willem van Gulik Tuesday, June 24, 2014 5:51 AM >> Still trying to get to the bottom of it - but seeing issues after todays pkg >> update. >> >> I suspect that the DNS API change >> >> https://issues.apache.org/SpamAssassin/sho

Re: FreeBSD Port: spamassassin-3.4.0_11

Dirk-Willem van Gulik Tuesday, June 24, 2014 5:51 AM Still trying to get to the bottom of it - but seeing issues after todays pkg update. I suspect that the DNS API change https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7057 I am setting up a new server

Re: FreeBSD Port: spamassassin-3.4.0_11

On 24.06.2014, at 12:57, Dirk-Willem van Gulik wrote: > Op 24 jun. 2014, om 12:07 heeft Kurt Jaeger het volgende > geschreven: >> If you still see the problem, can you provide more details ? >> What did you test ? What was the output ? > > > The symptom is all DNS failing within Spam Assassi

Re: FreeBSD Port: spamassassin-3.4.0_11

Hi! > >> Still trying to get to the bottom of it - but seeing issues after > >> todays pkg update. [...] > >> also hits us. > Meanwhile - got to the bottom if it - and it needs indeed said patch. Yes, but 3.4.0_11 should have it, that's the point of 191101 ? -- p...@opsec.eu+49 171

Re: FreeBSD Port: spamassassin-3.4.0_11

Op 24 jun. 2014, om 12:07 heeft Kurt Jaeger het volgende geschreven: > Hi! > >> Still trying to get to the bottom of it - but seeing issues after >> todays pkg update. >> >> I suspect that the DNS API change >> >> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7057 >> >> also h

Re: FreeBSD Port: spamassassin-3.4.0_11

Hi! > Still trying to get to the bottom of it - but seeing issues after > todays pkg update. > > I suspect that the DNS API change > > https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7057 > > also hits us. It's being worked on in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=

FreeBSD Port: spamassassin-3.4.0_11

Still trying to get to the bottom of it - but seeing issues after todays pkg update. I suspect that the DNS API change https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7057 also hits us. Dw. ___ freebsd-ports@freebsd.org mailing list ht