Bug 227996 - perl-Net-DNS 0.48 doesn't support SPF type
perl-Net-DNS 0.48 doesn't support SPF type
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: perl-Net-DNS (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Marcela Mašláňová
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-09 08:11 EST by Peter Bieringer
Modified: 2010-02-22 08:18 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-02-22 08:18:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter Bieringer 2007-02-09 08:11:54 EST
Description of problem:
perl-Net-DNS 0.48 doesn't support SPF, it's too old

Version-Release number of selected component (if applicable):
perl-Net-DNS-0.48-1

How reproducible:
Always

Steps to Reproduce:
1. try to use Mail::SPF on RHEL4 system
  
Actual results:
# spfquery --id account@domain.example --ip 192.0.2.1
Net::DNS::typesbyname() argument (SPF) is not TYPE### at
/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/Net/DNS.pm line 144.


Expected results:
Support of SPF DNS type

Additional info:
SPF is supported since 0.56:

*** 0.56 February 20, 2006

Fix rt.cpan.org 17694
 
   Net::DNS::typesbyval() now confesses on undefined
   args. Acknowledgements to Dean Serenevy.

Feature Implemented SPF (typecode 99).

   The class completely inherits from Net::DNS::RR::TXT (the easiest 
   RR to implement ever).

Please provide an update.
Comment 1 Marcela Mašláňová 2008-08-15 05:53:59 EDT
I'd rather not update to 0.58. There was a lot of changes, features, etc. I'm not sure if this package won't break ABI with other modules.
Comment 2 Marcela Mašláňová 2010-02-22 08:18:01 EST
The last planned update of RHEL-4 will be focused on performance and security bugs only. The next release should solve this issue.

Note You need to log in before you can comment on or make changes to this bug.