On Wed, Feb 6, 2013 at 9:41 AM, Steve Jenkins wrote:
> Hey, Mike. It's a cool idea - and almost works on a CentOS 6 box, but I'm
> getting "ambiguous redirect" errors in a couple of cases. When it's first
> run (/tmp/pslogscan does not exist yet) I get:
>
> # ./pslogscan.sh /var/log/maillog
> Scan
On Sun, Feb 3, 2013 at 9:06 AM, Mike. wrote:
> Version 1.4 of the pslogscan.sh script, incorporating the above fixes,
> is available at:
> http://archive.mgm51.com/sources/pslogscan.html
Hey, Mike. It's a cool idea - and almost works on a CentOS 6 box, but I'm
getting "ambiguous redirect" error
On 2/2/2013 at 9:52 AM Sahil Tandon wrote:
|Be careful with grep(1) patterns. You overstate CONNECTs by
|including 'NOQUEUE: reject: CONNECT' in the count.
I tightened up that regex to include only the CONNECT occurrences I
want.
| Meanwhile, the script
| understates total DNSBL rejections
On 2/2/2013 at 9:52 AM Sahil Tandon wrote:
|On Wed, 2013-01-30 at 14:23:19 -0500, Mike. wrote:
|
|> I made some changes to the script based upon the excellent feedback
I
|> received here.
|>
|> The script no longer wanders beyond the postscreen log records in
|> order to gather the information
On Wed, 2013-01-30 at 14:23:19 -0500, Mike. wrote:
> I made some changes to the script based upon the excellent feedback I
> received here.
>
> The script no longer wanders beyond the postscreen log records in
> order to gather the information needed to determine the postscreen
> rejection rate
On 1/30/2013 4:32 PM, Mike. wrote:
=
I've tried it on logs up to 40MB, and it ran to completion in around
five seconds. However, for that test, I copied the log file off the
production mail server and on to a lightly loaded box.
It's a pretty decent speed.
I have wrote a script
I made some changes to the script based upon the excellent feedback I
received here.
The script no longer wanders beyond the postscreen log records in order
to gather the information needed to determine the postscreen rejection
rate. So that removes the problems caused by multiple-recipient
m
On 1/30/2013 at 3:55 AM Eliezer Croitoru wrote:
|On 1/29/2013 8:07 PM, Mike. wrote:
|>
|> I implemented the postscreen capability on a small MTA I run for
|> friends and family. Once I got postscreen configuration producing
the
|> results I wanted, I soon tired of watching the detailed maillog to
On 1/29/2013 8:07 PM, Mike. wrote:
I implemented the postscreen capability on a small MTA I run for
friends and family. Once I got postscreen configuration producing the
results I wanted, I soon tired of watching the detailed maillog to see
how postscreen was operating. So I wrote a quick shel
On 1/29/2013 at 2:06 PM lcon...@go2france.com wrote:
|On Tuesday 29/01/2013 at 1:37 pm, Mike. wrote:
|>
|I suggest you simplify and use only postscreen log lines.
|
|"sent" and "deferred" are not postscreen actions.
|
|and "sent" double counts when postfix sends to content filter AND
|sends to
On Tuesday 29/01/2013 at 1:37 pm, Mike. wrote:
On 1/29/2013 at 2:01 PM Brian Evans wrote:
|On 1/29/2013 1:43 PM, Brian Evans wrote:
|> Because of that, I have skewed numbers:
|> All "incoming" log records: 10187
|> All "status=sent" log records: 7506
|> All "status=deferred" log records:
On 1/29/2013 at 2:01 PM Brian Evans wrote:
|On 1/29/2013 1:43 PM, Brian Evans wrote:
|> Because of that, I have skewed numbers:
|> All "incoming" log records: 10187
|> All "status=sent" log records: 7506
|> All "status=deferred" log records: 3302
|> rejected: -621 (-6%)
|>
|> It is not a simple
On 1/29/2013 1:43 PM, Brian Evans wrote:
Because of that, I have skewed numbers:
All "incoming" log records: 10187
All "status=sent" log records: 7506
All "status=deferred" log records: 3302
rejected: -621 (-6%)
It is not a simple math of "A minus B minus C" to find out how much
postscreen is r
On 1/29/2013 at 1:43 PM Brian Evans wrote:
|On 1/29/2013 1:29 PM, Mike. wrote:
|>
|> On 1/29/2013 at 1:14 PM Brian Evans wrote:
|>
|> |On 1/29/2013 1:07 PM, Mike. wrote:
|> |> I implemented the postscreen capability on a small MTA I run for
|> |> friends and family. Once I got postscreen configur
On 1/29/2013 1:29 PM, Mike. wrote:
On 1/29/2013 at 1:14 PM Brian Evans wrote:
|On 1/29/2013 1:07 PM, Mike. wrote:
|> I implemented the postscreen capability on a small MTA I run for
|> friends and family. Once I got postscreen configuration producing
the
|> results I wanted, I soon tired of wa
On 1/29/2013 at 1:14 PM Brian Evans wrote:
|On 1/29/2013 1:07 PM, Mike. wrote:
|> I implemented the postscreen capability on a small MTA I run for
|> friends and family. Once I got postscreen configuration producing
the
|> results I wanted, I soon tired of watching the detailed maillog to
see
|
On 1/29/2013 1:07 PM, Mike. wrote:
I implemented the postscreen capability on a small MTA I run for
friends and family. Once I got postscreen configuration producing the
results I wanted, I soon tired of watching the detailed maillog to see
how postscreen was operating. So I wrote a quick shell
I implemented the postscreen capability on a small MTA I run for
friends and family. Once I got postscreen configuration producing the
results I wanted, I soon tired of watching the detailed maillog to see
how postscreen was operating. So I wrote a quick shell script to
summarize the log file an
18 matches
Mail list logo
