https://github.com/smtpd/qpsmtpd/
Have a look at the Changes file, and/or the closed issues.
Matt
On Nov 30, 2013, at 7:43 AM, Walt Mankowski <walt...@pobox.com> wrote:
> I installed the new version of Net::DNS last night (version 0.73) and
> that caused qpsmtpd to fail with a fatal error. Here's what I see in
> the logs:
>
> 2013-11-30 10:04:04 *** FATAL PROGRAM ERROR!! Unknown method 'default'
> 2013-11-30 10:04:04 *** which the program has attempted to call for the
> object:
> 2013-11-30 10:04:04 ***
> 2013-11-30 10:04:04 *** ;; EDNS version 0
> 2013-11-30 10:04:04 ;; flags: 0000
> 2013-11-30 10:04:04 ;; rcode: NOERROR
> 2013-11-30 10:04:04 ;; size: 512
> 2013-11-30 10:04:04 ;; option:
> 2013-11-30 10:04:04
> 2013-11-30 10:04:04 ***
> 2013-11-30 10:04:04 *** This object does not have a method 'default'. THIS
> IS A BUG
> 2013-11-30 10:04:04 *** IN THE CALLING SOFTWARE, which incorrectly assumes
> that the
> 2013-11-30 10:04:04 *** object would be of a particular type. The type of
> an object
> 2013-11-30 10:04:04 *** should be checked before calling any of its methods.
> 2013-11-30 10:04:04 at
> /home/waltman/perl5/perlbrew/perls/perl-5.18.1/lib/site_perl/5.18.1/i686-linux-thread-multi/Net/DNS/Packet.pm
> line 183.
> 2013-11-30 10:04:04
> Net::DNS::Packet::data(Net::DNS::Packet=HASH(0x9dd8280)) called at
> /home/waltman/perl5/perlbrew/perls/perl-5.18.1/lib/site_perl/5.18.1/i686-linux-thread-multi/Net/DNS/Resolver/Base.pm
> line 500
> 2013-11-30 10:04:04
> Net::DNS::Resolver::Base::send(Net::DNS::Resolver=HASH(0x928b5a0),
> "66.175.208.152") called at
> /home/waltman/perl5/perlbrew/perls/perl-5.18.1/lib/site_perl/5.18.1/i686-linux-thread-multi/Net/DNS/Resolver/Base.pm
> line 490
> 2013-11-30 10:04:04
> Net::DNS::Resolver::Base::query(Net::DNS::Resolver=HASH(0x928b5a0),
> "66.175.208.152") called at lib/Qpsmtpd/TcpServer.pm line 160
> 2013-11-30 10:04:04 Qpsmtpd::TcpServer::tcpenv("192.168.1.57",
> "66.175.208.152") called at ./qpsmtpd-forkserver line 301
>
> I'm still running qpsmtpd 0.84, so it could very well be something
> that has already been fixed. Is anyone else seeing this?
>
> I've downgraded to Net-DNS-0.72 for now and that seems to have fixed
> my problem.
