Bug 1321403 - spf: lookup failed: addr is not a string
Summary: spf: lookup failed: addr is not a string
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: perl-Socket
Version: 7.4
Hardware: All
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: perl-maint-list
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-26 11:01 UTC by cm
Modified: 2017-03-21 12:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 12:37:56 UTC
Target Upstream Version:

Attachments (Terms of Use)
Working patch (423 bytes, patch)
2016-03-26 11:01 UTC, cm 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1200167 0 high CLOSED Socket::getnameinfo() refuses tainted value with "addr is not a string" exception 2021-02-22 00:41:40 UTC

Description cm 2016-03-26 11:01:40 UTC 
Created attachment 1140553 [details]
Working patch

Description of problem:

Using postfix and spamassassin with spf checking, an error message 'spf: lookup failed: addr is not a string at /usr/share/perl5/vendor_perl/IO/Socket/IP.pm line 662. occurs on some DNS servers.

Version-Release number of selected component (if applicable):
perl-Socket-2.010-4.el7

Steps to Reproduce:
1. Install postfix and spamassassin
2. Configure postfix to use spamassassin
3. Receive an incoming mail and spamassassin evaluates it

Actual results:
error message 'spf: lookup failed: addr is not a string at /usr/share/perl5/vendor_perl/IO/Socket/IP.pm line 662. occurs on some DNS servers and SPF checking does not happen

Expected results:
Spamassassin should check SPF results
Comment 2 Petr Pisar 2016-03-29 08:53:13 UTC 
So is this the same issue as bug #1200167? Even the patch is subset of patch for bug #1200167. I feel this is a duplicate of bug #1200167. Do you agree?
Note You need to log in before you can comment on or make changes to this bug.