Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. SPF>
  3. Devel
libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3
jam at jamux
Mar 13, 2006, 8:29 AM
Post #1 of 11 (6175 views)
Permalink
Package: libmail-spf-query-perl
Version: 1:1.999.1-1
Severity: normal

Apparently immediately after upgrading to perl-5.8.8-3 and since,
successive lines in mail.log from postfix/policy-spf are no longer
separated by newlines as below:

,----[ One Line from /var/log/mail.log ]
Mar 12 18:46:48 athene postfix/policy-spf[23441]: : SPF none: smtp_comment=SPF: domain of sender bounce-debian-user=jam=jamux.com@lists.debian.org does not designate mailers, header_comment=athene.jamux.com: domain of bounce-debian-user=jam=jamux.com@lists.debian.org does not designate permitted sender hosts<23>Mar 12 18:46:48 postfix/policy-spf[23441]: handler sender_permitted_from: PREPEND Received-SPF: none (athene.jamux.com: domain of bounce-debian-user=jam=jamux.com@lists.debian.org does not designate permitted sender hosts)<22>Mar 12 18:46:48 postfix/policy-spf[23441]: handler sender_permitted_from: PREPEND Received-SPF: none (athene.jamux.com: domain of bounce-debian-user=jam=jamux.com@lists.debian.org does not designate permitted sender hosts) is decisive.<22>Mar 12 18:46:48 postfix/policy-spf[23441]: decided action=PREPEND Received-SPF: none (athene.jamux.com: domain of bounce-debian-user=jam=jamux.com@lists.debian.org does not designate permitted sender hosts)
`----

Earlier:

,----[ Four Lines from /var/log/mail.log ]
Mar 12 18:43:04 athene postfix/policy-spf[22325]: : SPF none: smtp_comment=SPF: domain of sender bounce-debian-user=jam=jamux.com@lists.debian.org does not designate mailers, header_comment=athene.jamux.com: domain of bounce-debian-user=jam=jamux.com@lists.debian.org does not designate permitted sender hosts
Mar 12 18:43:04 athene postfix/policy-spf[22325]: handler sender_permitted_from: PREPEND Received-SPF: none (athene.jamux.com: domain of bounce-debian-user=jam=jamux.com@lists.debian.org does not designate permitted sender hosts)
Mar 12 18:43:04 athene postfix/policy-spf[22325]: handler sender_permitted_from: PREPEND Received-SPF: none (athene.jamux.com: domain of bounce-debian-user=jam=jamux.com@lists.debian.org does not designate permitted sender hosts) is decisive.
Mar 12 18:43:04 athene postfix/policy-spf[22325]: decided action=PREPEND Received-SPF: none (athene.jamux.com: domain of bounce-debian-user=jam=jamux.com@lists.debian.org does not designate permitted sender hosts)
`----

-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages libmail-spf-query-perl depends on:
ii libnet-cidr-lite-perl 0.15-1 Merge IPv4 or IPv6 CIDR address ra
ii libnet-dns-perl 0.53-2 Perform DNS queries from a Perl sc
ii libsys-hostname-long-perl 1.2-1 Figure out the long (fully-qualifi
ii liburi-perl 1.35-2 Manipulates and accesses URI strin
ii perl 5.8.8-3 Larry Wall's Practical Extraction

libmail-spf-query-perl recommends no packages.

-- no debconf information

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Re: libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3 [ In reply to ]
julian at mehnle
Mar 13, 2006, 9:52 AM
Post #2 of 11 (6058 views)
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John A. Martin wrote:
> Package: libmail-spf-query-perl
> Version: 1:1.999.1-1
> Severity: normal
>
> Apparently immediately after upgrading to perl-5.8.8-3 and since,
> successive lines in mail.log from postfix/policy-spf are no longer
> separated by newlines as below:
>
> ,----[ One Line from /var/log/mail.log ]
> Mar 12 18:46:48 athene postfix/policy-spf[23441]: : SPF none:
> smtp_comment=SPF: domain of sender
> bounce-debian-user=jam=jamux.com@lists.debian.org does not designate
> mailers, header_comment=athene.jamux.com: domain of
> bounce-debian-user=jam=jamux.com@lists.debian.org does not designate
> permitted sender hosts<23>Mar 12 18:46:48 postfix/policy-spf[23441]:
> handler sender_permitted_from: PREPEND Received-SPF: none
> (athene.jamux.com: domain of
> bounce-debian-user=jam=jamux.com@lists.debian.org does not designate
> permitted sender hosts)<22>Mar 12 18:46:48 postfix/policy-spf[23441]:
> handler sender_permitted_from: PREPEND Received-SPF: none
> (athene.jamux.com: domain of
> bounce-debian-user=jam=jamux.com@lists.debian.org does not designate
> permitted sender hosts) is decisive.<22>Mar 12 18:46:48
> postfix/policy-spf[23441]: decided action=PREPEND Received-SPF: none
> (athene.jamux.com: domain of
> bounce-debian-user=jam=jamux.com@lists.debian.org does not designate
> permitted sender hosts)
> `----

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

Has the behavior changed when you upgraded libmail-spf-query-perl to 1.999
(.1) or when you upgraded perl to 5.8.8-3? Or did you upgrade both at the
same time?

What makes you think this is a bug in libmail-spf-query-perl?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEFbFdwL7PKlBZWjsRAjYxAJoD9rI975QtI6g/nMRjDeLSXQqeoACeMcXT
b4IMSKg/knsMTMv3OsSIyNA=
=jtDo
-----END PGP SIGNATURE-----

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Re: Re: libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3 [ In reply to ]
darryl at netbauds
Mar 13, 2006, 11:30 AM
Post #3 of 11 (6032 views)
Permalink
John A. Martin wrote:
> Julian> characters as displayed
> Julian> (i.e. "\x3c\x32\x33\x3e"/"\x3c\x32\x32\x3e") or some kind
> Julian> 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> What are these "<23>" and "<22>" things? Are these ASCII

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

HTH


--
Darryl L. Miles


-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Re: libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3 [ In reply to ]
jam at jamux
Mar 13, 2006, 12:21 PM
Post #4 of 11 (6038 views)
Permalink
>>>>> "Julian" == Julian Mehnle
>>>>> "Re: libmail-spf-query-perl: Missing newline in log output -
>>>>> since perl-5.8.8-3"
>>>>> Mon, 13 Mar 2006 17:52:28 +0000

Julian> John A. Martin wrote:
>> Package: libmail-spf-query-perl Version: 1:1.999.1-1 Severity:
>> normal
>>
>> Apparently immediately after upgrading to perl-5.8.8-3 and
>> since, successive lines in mail.log from postfix/policy-spf are
>> no longer separated by newlines as below:
>>
>> ,----[ One Line from /var/log/mail.log ]
>> Mar 12 18:46:48 athene postfix/policy-spf[23441]: : SPF none:
>> smtp_comment=SPF: domain of sender
>> bounce-debian-user=jam=jamux.com@lists.debian.org does not designate
>> mailers, header_comment=athene.jamux.com: domain of
>> bounce-debian-user=jam=jamux.com@lists.debian.org does not designate
>> permitted sender hosts<23>Mar 12 18:46:48 postfix/policy-spf[23441]:
>> handler sender_permitted_from: PREPEND Received-SPF: none
>> (athene.jamux.com: domain of
>> bounce-debian-user=jam=jamux.com@lists.debian.org does not designate
>> permitted sender hosts)<22>Mar 12 18:46:48 postfix/policy-spf[23441]:
>> handler sender_permitted_from: PREPEND Received-SPF: none
>> (athene.jamux.com: domain of
>> bounce-debian-user=jam=jamux.com@lists.debian.org does not designate
>> permitted sender hosts) is decisive.<22>Mar 12 18:46:48
>> postfix/policy-spf[23441]: decided action=PREPEND Received-SPF: none
>> (athene.jamux.com: domain of
>> bounce-debian-user=jam=jamux.com@lists.debian.org does not designate
>> permitted sender hosts)
>> `----

Julian> What are these "<23>" and "<22>" things? Are these ASCII
Julian> characters as displayed
Julian> (i.e. "\x3c\x32\x33\x3e"/"\x3c\x32\x32\x3e") or some kind
Julian> 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> Has the behavior changed when you upgraded
Julian> libmail-spf-query-perl to 1.999 (.1) or when you upgraded
Julian> perl to 5.8.8-3? Or did you upgrade both at the same
Julian> time?

The "After" and "Before" examples were separated by less than 4
minutes during which yaird, ucf, udev, libsnmp9, read-edid, snmp,
cpio, and perl were upgraded. libmail-spf-query-perl was upgraded to
1.999.1-1 on (and used continuously since) 2006-02-27 18:36 EST.

Julian> What makes you think this is a bug in
Julian> 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.

FWIW though they are not dependencies of libmail-spf-query-perl the
main other players are syslog-ng-1.9.9-1 (since 2006-03-01) and
postfix-2.2.9-1 (2006-02-24).

Thank you for looking into this.

jam

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Re: libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3 [ In reply to ]
julian at mehnle
Mar 13, 2006, 1:41 PM
Post #5 of 11 (6046 views)
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

(John, since you reported the issue to the Debian BTS, please CC your
messages to 356700@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-----

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Re: libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3 [ In reply to ]
julian at mehnle
Mar 13, 2006, 3:48 PM
Post #6 of 11 (6027 views)
Permalink
-----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-----

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Re: libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3 [ In reply to ]
jam at jamux
Mar 13, 2006, 4:20 PM
Post #7 of 11 (6038 views)
Permalink
>>>>> "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 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.


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

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Re: Re: libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3 [ In reply to ]
spf2 at kitterman
Mar 13, 2006, 7:17 PM
Post #8 of 11 (6039 views)
Permalink
On 03/13/2006 18:48, Julian Mehnle wrote:
> John A. Martin wrote:
> > Julian Mehnle wrote:
> > > 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-po
>licyd-spf
>
I know a, very, little about Postfix policy daemons. I didn't see anything
obvious. I did note that some earlier versions had $VERBOSE = 1; instead of
the current $VERBOSE = 0;. Other than that I didn't see any logging related
differences. I looked in M:S:Q also and didn't see any there.

I can see from the two samples you provided that in neither case are you doing
verbose logging, so that's not it....

I currently have PERL v5.8.4 installed and I don't have time to fiddle with
upgrading and downgrading just now...

I did some searching and there have been a number of Sys::Syslog changes in
the 5.8 series. You didn't (that I noticed) say what version you upgraded
from. One thing I noticed in looking at the code is that there is a slight
difference in the lines of code that cause the <22> and <23> and those that
don't:

It looks like the codes come at the start of the log line and perhaps they are
eating the newline:

syslog(debug=> "handler %s: %s", $handler, $response);
syslog(info=> "handler %s: %s is decisive.", $handler, $response);
syslog(info=> "decided action=%s", $action);

This one, I think was right:

syslog(info=>"%s: SPF %s: smtp_comment=%s, header_comment=%s",
$attr{queue_id}, $result, $smtp_comment, $header_comment);

The difference I see is that the lines I think are causing the problem have a
space after => and the one that doesn't, I think, cause a problem, doesn't
have the space.

I find it hard to believe that such a trivial difference would cause a problem
like this (I certainly don't know, I don't do much PERL. Python's more my
cup of tea), but all the examples for Sys::Syslog on perl.org did not have a
space there.

So, I am theorizing that there may have been a change in Sys::Syslog between
your old version and the new one that caused this (slightly) deviant syntax
to now cause a problem.

My suggestion would be to go into all the syslog lines in the file and remove
the extraneous space and see if that works better. I haven't tested this, so
it's just a theory.

Good luck,

Scott K

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Re: libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3 [ In reply to ]
julian at mehnle
Mar 14, 2006, 4:25 AM
Post #9 of 11 (6039 views)
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Scott Kitterman wrote:
> I know a, very, little about Postfix policy daemons. I didn't see
> anything obvious. I did note that some earlier versions had $VERBOSE =
> 1; instead of the current $VERBOSE = 0;. Other than that I didn't see
> any logging related differences. I looked in M:S:Q also and didn't see
> any there.

Neither do I.

> I did some searching and there have been a number of Sys::Syslog changes
> in the 5.8 series.

I noticed that, too. There is a line in Sys::Syslog that adds a newline to
the message before sending it to the syslog socket, but it hasn't changed
in Perl 5.8.8, so I'm at a loss why the new Sys::Syslog in Perl 5.8.8
would change the behavior in the way John observed. I cannot rule it out,
though.

In any event however I am pretty sure that his problem has something to do
with his use of syslog-ng vs. the standard sysklogd. The new Sys::Syslog
probably hasn't been tested with syslog-ng.

> One thing I noticed in looking at the code is that there is a slight
> difference in the lines of code that cause the <22> and <23> and those
> that don't:
> [...]
> The difference I see is that the lines I think are causing the problem
> have a space after => and the one that doesn't, I think, cause a
> problem, doesn't have the space.
>
> I find it hard to believe that such a trivial difference would cause a
> problem like this (I certainly don't know, I don't do much PERL.
> Python's more my cup of tea), but all the examples for Sys::Syslog on
> perl.org did not have a space there.

That's definitely NOT the cause.

What really should be done now is downgrading libmail-spf-query-perl to see
if the problem goes away then. If it doesn't then it is almost certainly
a change in Sys::Syslog or syslog-ng that causes the problem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEFrZVwL7PKlBZWjsRAo72AKCMq+KUvY77dEPmfGGOCrZqE9f4FwCg7qhT
1HQdR1dKUKgGtGJ7qb0zWsw=
=+Qhi
-----END PGP SIGNATURE-----

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Re: libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3 [ In reply to ]
jam at jamux
Mar 14, 2006, 6:20 AM
Post #10 of 11 (6038 views)
Permalink
>>>>> "Julian" == Julian Mehnle
>>>>> "Re: libmail-spf-query-perl: Missing newline in log output -
>>>>> since perl-5.8.8-3"
>>>>> Mon, 13 Mar 2006 23:48:52 +0000

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

The same libmail-spf-query-perl-1.999.1-1 was used before and after
the log lines were run together. The problem arose when the perl and
perl-base packages were upgraded from 5.8.8-2 to 5.8.8-3.

Now when downgrading perl and perl-base to 5.8.8-2 the problem
disappears. When upgrading perl and perl-base to 5.8.8-3 the problem
appears again. The problem in reproducible.

,----[. From: owner@bugs.debian.org (Debian Bug Tracking System)
Subject: Bug#356700: Acknowledgement
Date: Mon, 13 Mar 2006 08:33:10 -0800 ]
[[....]]
Your message has been sent to the package maintainer(s):
Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
`----

That includes you, right? Package maintainers can move bugs from one
package to another, no?

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

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

http://www.postfix.org/SMTPD_POLICY_README.html

HTH

jam

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Re: libmail-spf-query-perl: Missing newline in log output - since perl-5.8.8-3 [ In reply to ]
julian at mehnle
Mar 14, 2006, 6:27 AM
Post #11 of 11 (6029 views)
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John A. Martin wrote:
> The same libmail-spf-query-perl-1.999.1-1 was used before and after
> the log lines were run together. The problem arose when the perl and
> perl-base packages were upgraded from 5.8.8-2 to 5.8.8-3.
>
> Now when downgrading perl and perl-base to 5.8.8-2 the problem
> disappears. When upgrading perl and perl-base to 5.8.8-3 the problem
> appears again. The problem in reproducible.

Julian Mehnle wrote:
> There is a line in Sys::Syslog that adds a newline to the message before
> sending it to the syslog socket, but it hasn't changed in Perl 5.8.8

Oh, it _has_ changed! See the attached diff of the Sys::Syslog changes in
perl 5.8.8-3 vs. perl 5.8.8-2. Apparently the Sys::Syslog in perl 5.8.8-3
does no longer append a newline (\n) to syslog messages. Since RFC 3164
[1],
"The BSD syslog Protocol", does not require a newline terminator in syslog
messages, I think this change is valid and appropriate.

However it seems syslog-ng does not add its own newline when writing the
received messages to the log file, so it relies on the generator of the
message to add the newline. This is a bug in syslog-ng, so I'll reassign
the bug there.

There's probably another, similar issue with regard to adding NULL byte
(\0) terminators to log messages. RFC 3164 does not require such \0
terminators either, and the changed Sys::Syslog in perl 5.8.8-3, which also
stops appending \0 bytes to syslog messages, seems not to cause problems
with sysklogd.

Although there seems to have been some reluctance by the Perl folks to omit
the \0 terminators due to potential problems with UNIX domain sockets[2], I
don't see why such terminators would be required with UNIX domain sockets
but not with UDP sockets. I am not a sockets expert, though.

If \0 terminators are indeed required with UNIX domain sockets (which I
don't believe to be true), then their omittance in the Sys::Syslog in perl
5.8.8-3 is inappropriate and should be reverted. Otherwise, this is
another bug in syslog-ng.

In any case, those are not bugs in libmail-spf-query-perl AKA Mail::SPF::
Query.

Julian.

References:
1. http://www.rfc-editor.org/rfc/rfc3164.txt
2. http://rt.perl.org/rt3/Ticket/Display.html?id=28019#txn-83160
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEFtLxwL7PKlBZWjsRAthtAKDyadycSPixOn0xDEoxySbBmKWLOQCbBXBn
oKcBmMYzDsT9H9R6ul+vNO4=
=DtRp
-----END PGP SIGNATURE-----

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com

Attached Files:

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal