On Tue, Jul 04, 2017 at 09:38:35PM +0200, Julien Cristau wrote: > Control: severity -1 normal > > On Tue, Jul 4, 2017 at 19:27:09 +0200, Julien Cristau wrote: > > > Source: postgrey > > Version: 1.36-3 > > Severity: grave > > User: debian-ad...@lists.debian.org > > Usertags: needed-by-DSA-Team > > X-Debbugs-Cc: debian-ad...@lists.debian.org > > > > After upgrading one of our mail relays to stretch, postgrey regularly > > crashes with the error is $subject. > > > > This might or might not be fixed upstream with > > https://github.com/schweikert/postgrey/commit/95a2cd8f7f132aae8c62e9706dd9459afca84a5c > > which changed the relevant code and among other things added checks for > > NetAddr::IP->new returning undef. > > > Turns out this was most likely due to the recently-added ipv6 support in > postgrey [0], and our exim config [1] using the ${mask:...} operator, > which would return addresses such as > "2a02.1600.0000.0000.0000.0000.0000.0000" [2]. NetAddr::IP would then > parse that as an ipv4 address and fail, and postgrey doesn't check for > that condition. >
This is unfortunate, I will have a patch for stable-proposed-updates on Saturday, sorry for the inconvenience :(
