Bug#1040006: pflogsumm: fails to count sent emails

[Yvan Masson]

Package: pflogsumm
Version: 1.1.5-7
Severity: normal

Dear maintainer,

I use pflogsumm on a Bullseye system, to analyze Postfix 3.5.17 logs. It
is possible my setup has some oddities, but while pflogsumm is globally
working, it fails to count sent emails:

$ pflogsumm my_log_file
[...]
0 sending hosts/domains
[...]
Host/Domain Summary: Messages Received
---------------------------------------
msg cnt bytes host/domain
-------- ------- -----------

Senders by message count: none
[...]
Senders by message size: none
[...]

A friend of mine suggested a very small change in pflogsumm, which seems
to make it working properly. Here si the diff before and after the fix:

804c805,806
< if($rcvdMsg{$qid}) {
---
> if($rcvdMsg{$qid} == '') {



But it si still not perfect, because now errors are printed before the
actual report:

Argument "" isn't numeric in numeric eq (==) at
/usr/local/sbin/pflogsumm line 806, <> line 56.
Use of uninitialized value within %rcvdMsg in numeric eq (==) at
/usr/local/sbin/pflogsumm line 806, <> line 56.
[...]

Use of uninitialized value $domAddr in hash element at
/usr/local/sbin/pflogsumm line 814, <> line 1272.

[...]

Use of uninitialized value within %rcvdMsg in numeric eq (==) at
/usr/local/sbin/pflogsumm line 806, <> line 1294.


Hope this help.

Regards,
Yvan

[Sven Hoexter]

On Fri, Jun 30, 2023 at 11:47:33PM +0200, Yvan Masson wrote:

Hi,

> I use pflogsumm on a Bullseye system, to analyze Postfix 3.5.17 logs. It is
> possible my setup has some oddities, but while pflogsumm is globally
> working, it fails to count sent emails:

Hi,
I can not reproduce that on my own system, though I'm already working
with bookworm which means postfix 3.7.x. As far as I remember pflogsumm
was in general working fine on bullseye.

Also oldstable aka bullseye already contains postfix 3.5.18, not sure why
you're running 3.5.17.

Since bullseye is now oldstable, there won't be any updates regarding this
issue for bullseye anyway.

What would be of interest is if the issue could be reproduced on current
Debian release. In that case a log sample would be also helpful.

Sven