Dnia 24.01.2022 o godz. 10:21:52 raf pisze:
>
> One last thing, the README.md file recommends
> installing into a venv, but it doesn't then explain the
> steps necessary to run postqf afterwards. This would be
> a mystery to non-Python developers.
Isn't setting up a venv an "overkill" for using o
* Viktor Dukhovni:
> Of course implementing a "jq" script with the same command-line
> interface as "postqf" is not too difficult.
Faced with the choice between doing that or writing Python code, I chose
the latter. ;-)
> The main difference is that the regular expression syntax in JQ is
> somew
* raf:
> I suppose a shell alias or function could take care of that without
> needing to type the extra option (e.g.: alias postqq='postqueue -j |
> postqf').
Indeed. In typical Unix-pipeline fashion, PostQF reads from stdin and
writes to stdout per default, and it is up to the user to provide t
> "Why not use jq?" I hear you ask. While jq is undoubtedly powerful and
> can handle pretty much any JSON data thrown at it, I found jq's syntax
> rather cumbersome. PostQF is specifically designed to make filtering
> Postfix queue data both easier and quicker, by means of simple command
> line
On Sun, Jan 23, 2022 at 11:08:49PM +0100, Ralph Seichter
wrote:
> Hello Postfix users.
>
> Hopefully neither Wietse nor you folks will mind me announcing my latest
> software baby here. ;-)
>
> I have just released version 0.1 of PostQF, a user-friendly Postfix
> queue data filter easily used
Hello Postfix users.
Hopefully neither Wietse nor you folks will mind me announcing my latest
software baby here. ;-)
I have just released version 0.1 of PostQF, a user-friendly Postfix
queue data filter easily used in Unix-like pipes. For example
postqueue -j | postqf -a 90m | wc -l
prints t
