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

John A. Martin jam at jamux.com
Mon Mar 13 23:01:18 UTC 2006


>>>>> "Julian" == Julian Mehnle
>>>>> "Re: libmail-spf-query-perl: Missing newline in log output -
>>>>>   since perl-5.8.8-3" 
>>>>>  Mon, 13 Mar 2006 21:41:55 +0000

    Julian> 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.

    Julian> I cannot rule that out (yet).  What's this
    Julian> "postfix/policy-spf" thing that's mentioned in your logs?
    Julian> Is that a Postfix policy deamon?  Is it the same one
    Julian> that's included in libmail-spf-query-perl as "postfix-
    Julian> policyd-spf"?

Yes, almost the same:

,----[ grep -A 1 '^policy ' /etc/postfix/master.cf ]
policy    unix  -       n       n       -       -       spawn
  user=nobody argv=/usr/bin/perl /usr/local/libexec/postfix/smtpd-policy.pl
`----
,----[ zcat /usr/share/doc/libmail-spf-query-perl/examples/postfix-policyd-spf.gz>/tmp/postfix-policyd-spf ]
`----
,----[ diff /tmp/postfix-policyd-spf /usr/local/libexec/postfix/smtpd-policy.pl ]
19c19
<   push @HANDLERS, "testing";
---
> # push @HANDLERS, "testing";
239a240,241
> 
>   
`----

Close enough? :)

    >> > 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.

    Julian> 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

    Julian> That seems plausible.  However I don't have the slightest
    Julian> 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.)

        jam

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 154 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20060313/32f00f76/attachment.pgp


More information about the pkg-perl-maintainers mailing list