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

[Julian Mehnle]

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

(John, since you reported the issue to the Debian BTS, please CC your 
messages to 356700 at bugs.debian.org so that the bug report there doesn't 
become a dead end.)

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"?

> > What are these "<23>" and "<22>" things?  Are these ASCII characters as
> > displayed (i.e. "\x3c\x32\x33\x3e"/"\x3c\x32\x32\x3e") or some kind of
> > raw ASCII codes (i.e. "\x23"/"\x22")?
>
> Beats me.  The "<23>" and "<22>" things look like they appear somewhere
> in the vicinity where newline characters might be expected.

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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEFeckwL7PKlBZWjsRArKOAJ4mthL0wqsQvwq5MEYekr/0hwfF9ACfcIlI
vqCGhmhhcZH26JpOv/a31W0=
=JtOj
-----END PGP SIGNATURE-----