Re: pflogsumm error.
On 30.03.20 14:27, @lbutlr wrote:
When running pflogsumm I am getting many error like this:
Use of uninitialized value $domain in string eq at /usr/local/bin/pflogsumm line
1546, <> line 283375.
Use of uninitialized value $domain in substitution (s///) at /usr/local/bin/pflogsumm
line 1552, <> line 283375.
# awk '{if(NR==283375) print $0}’ mail.log.combined
Mar 29 23:14:45 mail.covisp.net postfix/postscreen[54597] NOQUEUE: reject: RCPT from
[45.155.126.14]:47867: 550 5.7.1 Service unavailable; client [45.155.126.14] blocked using
zen.spamhaus.org; from=, to=<*munged*covisp.net>,
proto=ESMTP, helo=
On 31 Mar 2020, at 07:43, Matus UHLAR - fantomas wrote:
where do you have your pflogsumm version from?
On 03.04.20 09:48, @lbutlr wrote:
FreeBSD ports
which FreeBSD, which perl?
original pflogsumm does not support postscreen.
OK, so postscreen normally logs into mail.log and I use rsyslogd to put it in
its own file. Are these errors normal for pflogsumm on non-Debian systems then?
checked with debian 8 pflogsumm, postscreen rejects are simply ignored.
Since Postscreen blocks most of the mail, not having postscreen in poflogsumm
means I get numbers like “accepted, 1234, delivered 214881, rejected 47” which
is.. well, wrong.
correct. However, original pflogsumm does not process postscreen logs...
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The only substitute for good manners is fast reflexes.
Re: pflogsumm error.
On 31 Mar 2020, at 07:43, Matus UHLAR - fantomas wrote:
> On 30.03.20 14:27, @lbutlr wrote:
>> When running pflogsumm I am getting many error like this:
>>
>> Use of uninitialized value $domain in string eq at /usr/local/bin/pflogsumm
>> line 1546, <> line 283375.
>> Use of uninitialized value $domain in substitution (s///) at
>> /usr/local/bin/pflogsumm line 1552, <> line 283375.
>>
>> # awk '{if(NR==283375) print $0}’ mail.log.combined
>> Mar 29 23:14:45 mail.covisp.net postfix/postscreen[54597] NOQUEUE: reject:
>> RCPT from [45.155.126.14]:47867: 550 5.7.1 Service unavailable; client
>> [45.155.126.14] blocked using zen.spamhaus.org;
>> from=, to=<*munged*covisp.net>, proto=ESMTP,
>> helo=
>
> where do you have your pflogsumm version from?
FreeBSD ports
> original pflogsumm does not support postscreen.
OK, so postscreen normally logs into mail.log and I use rsyslogd to put it in
its own file. Are these errors normal for pflogsumm on non-Debian systems then?
Since Postscreen blocks most of the mail, not having postscreen in poflogsumm
means I get numbers like “accepted, 1234, delivered 214881, rejected 47” which
is.. well, wrong.
--
"Are you pondering what I'm pondering?"
"I think so, Brain, but wouldn't mustard make it sting?”
Re: pflogsumm error.
On 30.03.20 14:27, @lbutlr wrote:
When running pflogsumm I am getting many error like this:
Use of uninitialized value $domain in string eq at /usr/local/bin/pflogsumm line
1546, <> line 283375.
Use of uninitialized value $domain in substitution (s///) at /usr/local/bin/pflogsumm
line 1552, <> line 283375.
# awk '{if(NR==283375) print $0}’ mail.log.combined
Mar 29 23:14:45 mail.covisp.net postfix/postscreen[54597] NOQUEUE: reject: RCPT from
[45.155.126.14]:47867: 550 5.7.1 Service unavailable; client [45.155.126.14] blocked using
zen.spamhaus.org; from=, to=<*munged*covisp.net>,
proto=ESMTP, helo=
where do you have your pflogsumm version from?
original pflogsumm does not support postscreen.
Debian version 1.1.5-3 includes support for it, and should not generate this
kind of errors
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
LSD will make your ECS screen display 16.7 million colors
Re: pflogsumm error.
On 30 Mar 2020, at 15:53, Wietse Venema wrote:
> Does the error change if reverse the file order?
I put then in order {postscreen, delivery, mail} and also {delivery,
postscreen, mail} and no difference, but all the logs are piped to sort before
being redirected to the file that pflogsumm processes.
--
Footnote: The calendar of the Theocracy of Muntab counts down, not
up. No-one knows why, but it might not be a good idea to hang
around and find out.
Re: pflogsumm error.
Does the error change if reverse the file order? Wietse
