https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7265
--- Comment #18 from Kevin A. McGrail <[email protected]> --- (In reply to Kevin A. McGrail from comment #17) > On a similar note, Mark, based on comment 7, is the SPF plugin also affected > by this? Mark's comment from the list: Not sure about SPF. It's supposed to be fixed in the current 3.4 branch and in trunk, which is why I'm not seeing a problem with Net::DNS 1.03 or Net::DNS 1.04. Will check how the released version of 3.4.1 fares with Net::DNS 1.04 regarding SPF. The emergency patches were applied to FreeBSD ports, don't know about other distributions. Here are the relevant bug entries: https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7231 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7265 There were three changes in New::DNS that affected SpamAssassin. The change in 1.01 affected SpamAssassin due to our sloppy parsing of Net::DNS results. The changes brought by 1.03 affected SpamAssassin on two fronts, both are due to an incompoatible API change in Net::DNS: different object class expected by bgread (which affected a handful of other Perl modules too), and a change in semantics of "retry" and "retrans" options, which affected DKIM plugin. Mark -- You are receiving this mail because: You are the assignee for the bug.
