On Wed, 4 Jun 2025 23:41:54 +0200 Tom Hendrikx via Postfix-users <postfix-users@postfix.org> wrote:
> On 03-06-2025 21:33, Jim Seymour via Postfix-users wrote: > > Hi All, [snip-a-roo] > > > > Lastly: I'm asking again for log samples. I've been unable to test > > the following RE's: > > > > (BARE NEWLINE) from \[(.+)\]:(\d+) after .+ > > (BDAT without valid RCPT) from \[(.+)\]:(\d+) > > (COMMAND LENGTH LIMIT) from \[(.+)\]:(\d+) after .+ > > (DATA without valid RCPT) from \[(.+)\]:(\d+) > > (NOQUEUE: reject: CONNECT) from \[(.+)\]:(\d+): all server > > ports busy (reject: connect) from \[(.+)\]:(\d+): all screening > > ports busy > > In the project I maintain with Logstash grok patterns for Postfix, > there are also a number of log message examples, including > postscreen ones. See > https://github.com/whyscream/postfix-grok-patterns, all files in > test/postscreen_* Thanks for the pointer, Tom! Along with those and examining the Postfix code I was able to add parsing for a number of additional postscreen log messages... I *think* ;) Regards, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at <http://jimsun.LinxNet.com/contact/scform.php>. _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
