Bug#356700: libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3

Julian Mehnle julian at mehnle.net
Mon Mar 13 23:48:52 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John A. Martin wrote:
> Julian Mehnle wrote:
> > John A. Martin wrote:
> > > Julian Mehnle wrote:
> > > > What makes you think this is a bug in libmail-spf-query-perl?
> > >
> > > My prime suspects seemed to be libmail-spf-query-perl or perl.  Since
> > > there are likely a few more perl users but no Debian Bug reports on
> > > perl since the upgrade became available on 2006-02-12 it seemed as if
> > > perhaps libmail-spf-query-perl and perl may not be playing nicely
> > > together since the perl upgrade. 
> > 
> > I cannot rule that out (yet).  What's this "postfix/policy-spf" thing
> > that's mentioned in your logs?  Is that a Postfix policy deamon?  Is it
> > the same one that's included in libmail-spf-query-perl as "postfix-
> > policyd-spf"?
>
> Yes, almost the same:
>
> [...]
> ,----[ diff /tmp/postfix-policyd-spf /usr/local/libexec/postfix/smtpd-policy.pl ]
> 19c19 
> <   push @HANDLERS, "testing";
> ---
> > # push @HANDLERS, "testing";
> 239a240,241
> >
> >
> `----
>
> Close enough? :)

I asked whether you were using the policy daemon from libmail-spf-query-
perl because I wanted to know if that could have been the source of the
change in behavior.  However examples/postfix-policyd-spf hasn't been
changed significantly since 1.997 and not at all since 1.998[1], so I doubt
it is the culprit.

Could you, for testing purposes, try downgrading libmail-spf-query-perl to
the last version you were using before the problem occurred and see if the
problem goes away?  That should be the definite indicator for whether the
problem is rooted anywhere in libmail-spf-query-perl.

> > Darryl L. Miles wrote:
> > > Your post caught my eye.  I would guess UNIX Syslog selectors.
> > >
> > > Looking at sys/syslog.h on Linux I would make the most obvious
> > > decoding of the value to mean:
> > >
> > > <22> into 0x16, which is (2<<3) | 6 or LOG_MAIL | LOG_INFO
> > > <23> into 0x17, which is (2<<3) | 7 or LOG_MAIL | LOG_DEBUG
> > 
> > That seems plausible.  However I don't have the slightest idea why
> > those would show up in raw form in the log.
>
> What are the intended log levels?  I don't make much sense of what is
> logged even before the mishap.  (I normally just grep what I want from
> a catch-all log.)

Unfortunately, I don't have a clue either.  I know little about Postfix and
the Postfix SPF policy daemon.

References:
 1. http://www.openspf.org/source/mail-spf-query-perl/trunk/examples/postfix-policyd-spf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEFgTlwL7PKlBZWjsRArk5AKDLS7YX+r4sdDMNe4/U4XroQUEcCwCgkX6O
IbH/0rWFfIbXJv1MNRexiwE=
=lwhK
-----END PGP SIGNATURE-----




More information about the pkg-perl-maintainers mailing list