Your message dated Thu, 27 Apr 2023 12:22:59 +0000 with message-id <e1ps0ej-008eg4...@fasolo.debian.org> and subject line Bug#1034727: fixed in spf-engine 3.0.4-2 has caused the Debian Bug report #1034727, regarding postfix-policyd-spf-python: Update logcheck regex to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: postfix-policyd-spf-python Version: 3.0.4-1 Severity: important Tags: bookworm patch I updated one of my servers from bullseye to bookworm this weekend and discovered a couple of issues with the logcheck regex shipped with postfix-policyd-spf-python: * The "+" at the beginning of the line causes grep 3.8 to emit the message "grep: warning: + at start of expression" every time logcheck is invoked * logcheck in bookworm defaults to checking the systemd journal, which uses high-resolution timestamps; the current pattern will not match those * The format of the message to be ignored has changed sometime before bullseye, so the logcheck rule as-is isn't actually doing anything I have attached a patch to update the rule, and tested it with rsyslog output (from bullseye and bookworm), as well as journald output from bookworm, and it appears to work correctly. Please consider applying the patch and uploading a new version of postfix-policyd-spf- python so this fix can be included in the bookworm release. Thanks, Mathiasdiff --git a/debian/logcheck/postfix-policyd-spf-python b/debian/logcheck/postfix-policyd-spf-python index 7abdccf..07a87b1 100644 --- a/debian/logcheck/postfix-policyd-spf-python +++ b/debian/logcheck/postfix-policyd-spf-python @@ -1,2 +1 @@ -+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ policyd-spf\[[0-9]+\]: (Pass|Neutral|None|Softfail|Fail|Temperror|Permerror); identity=(helo|mailfrom); client-ip=[0-9a-f.:]+; helo=.*; envelope-from=.*; receiver= - +^(\w{3} [ :[:digit:]]{11}|[0-9T:.+-]{32}) [._[:alnum:]-]+ policyd-spf\[[0-9]+\]:( :)? prepend Received-SPF: (Pass|Neutral|None|Softfail|Fail|Temperror|Permerror) \((helo|mailfrom)\) identity=(helo|mailfrom); client-ip=[0-9a-f.:]+; helo=.*; envelope-from=.*; receiver=
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---Source: spf-engine Source-Version: 3.0.4-2 Done: Scott Kitterman <sc...@kitterman.com> We believe that the bug you reported is fixed in the latest version of spf-engine, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman <sc...@kitterman.com> (supplier of updated spf-engine package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Thu, 27 Apr 2023 07:47:47 -0400 Source: spf-engine Architecture: source Version: 3.0.4-2 Distribution: unstable Urgency: medium Maintainer: Scott Kitterman <sc...@kitterman.com> Changed-By: Scott Kitterman <sc...@kitterman.com> Closes: 1034727 Changes: spf-engine (3.0.4-2) unstable; urgency=medium . * Upload to unstable . spf-engine (3.0.4-2~exp1) experimental; urgency=medium . * Update logcheck rule for postfix-policyd-spf-python to account for logging changes in Bookworm (Closes: #1034727) - Thanks to Mathias Gibbens for the report and the fix Checksums-Sha1: 889dc93ce48be60fe87e2e0fff93c64ea377f35e 2443 spf-engine_3.0.4-2.dsc 51a078f83e8fbcf743ee9f8b9f4329b13fb454ac 14328 spf-engine_3.0.4-2.debian.tar.xz 0c4e5151a6bea8c570695efbe90d0377c229ddb9 6387 spf-engine_3.0.4-2_source.buildinfo Checksums-Sha256: 3c604014d1319001379726673a7d6080ff4b6221f3dfb4432f884a9730f99722 2443 spf-engine_3.0.4-2.dsc 0efcbb96dc7be4a0a2a6d1e66862ed0594317038854c7991b8ba683437893dd3 14328 spf-engine_3.0.4-2.debian.tar.xz aa18fc7171546e6ca95c422a46cf3f9cfddfac1abfb73c68ef780188059e93f2 6387 spf-engine_3.0.4-2_source.buildinfo Files: 0918fdf142f21c09d5b1b2b4376091cd 2443 mail optional spf-engine_3.0.4-2.dsc 7faee8e89af5056c2382e06812de96b2 14328 mail optional spf-engine_3.0.4-2.debian.tar.xz 6ef90ecd6f357f5121bdeb650745d588 6387 mail optional spf-engine_3.0.4-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAmRKYXwACgkQeNfe+5rV mvHN0Q//bwiNe5bgDg5QeFeZ/jdkur+Yq2b4TKGw37XbMYtQ8UYSUG57fKgWa00b tpt9D8ToLelmZnUsddUyOL0ifQxs/TtNHr94MGJsLW9myDPPteL41WXeBJ0LRjr8 pStsg4gXk/URM/yqajMMPICtfNOfIfke/ABjfCR+d6fRkY4yVL9pI+nUC+45lDU7 l3+zGEXHl0Bs4bRiKzq9gELpuNICffJZp5fK0poytVRRR4p2remLpVzixSTiclgY k3qEH48iJFcrqPSpFX6fcK4psQ5PNBPwBu+V5JkiJCO79ARNWfSoqn+KZaJ7hlPe qVOg0R8niVfpwBDSXXhXC7iltrMA2EebjTGzdAz/l844p6tXj3BQhcCSXeVIdIwj G8KvTapy44MAMgzSyU7N7Jmgxz+1JAqBk/xUP0mavt6q8B1HgAS+zXgGMFedWuFE 5pZxrpIuQFfVcp6sfH/OiDLpx/ICPEqmPAZ7E0uhW6XWer5ZiLKmaPHJPpGM8M5P iZLQzBVeqtS7ugPBM2uOohds4Wjy5BB4nUKHwZhU6u3yCEYe/W943zTaeEWbDixR PfuvORS3tRawmJ7o80+AaQLIuYczulMV+u7dctPjueqQ1o5kuw0Ti7ALVdWezwYs NjVlvtm6AGwAl5mk8IfvzoIyto2C4MHxJlMWvdzM7vnScDlkbfM= =BCY5 -----END PGP SIGNATURE-----
--- End Message ---
