Your message dated Mon, 01 Apr 2024 18:04:18 +0000
with message-id <[email protected]>
and subject line Bug#1028356: fixed in procmail 3.24+really3.22-1
has caused the Debian Bug report #1028356,
regarding procmail: Variable set with stdin pipe action fails leaving empty 
variable
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 [email protected]
immediately.)


-- 
1028356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028356
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: procmail
Version: 3.24-1
Severity: normal

I am very happy to see procmail upstream is now active again!
Excellent news!  I am a long time user and have quite a few mail
filtering rules.

The recent upgrade to 3.24 broke using a pipe action to set a variable
using stdin.  Reverting to 3.22 restores correct functioning.

For example due to UTF-8 subject encoding one might find a subject
with this contrived and constructed example.

    Subject: =?utf-8?q?test-list_post_from_rwp=40proulx=2Ecom_require?=
     =?utf-8?q?s_approval?=

I use the following idiomatic procmail expression to decode that
subject and place it into a SUBJECT variable.  This following from my
.procmailrc file.

    # If the subject is encoded and needs decoding then...
    #   extract the subject, decode it, store in the SUBJECT variable.
    :0h
    * ^Subject:.*=\?
    SUBJECT=|formail -cXSubject: | perl -MEncode -pe 
'Encode::from_to($_,"MIME-Header","UTF-8");'

    # Store all remaining cases of Subject: into $SUBJECT.
    # E - only execute this recipe if previous recipe was not executed.
    :0hE
    SUBJECT=|formail -cXSubject:

    # Here forward SUBJECT contains the decoded text.
    # Match it using the variable ?? syntax.
    # * SUBJECT ?? ^Subject: blah blah blah

Then I use it like this following to handle Mailman messages.

    :0
    * ^X-BeenThere:
    * SUBJECT ?? ^Subject: .*mailing list memberships reminder$
    mailman-reminders/

    :0
    * ^X-List-Administrivia: yes
    {
      :0
      * 1^0 SUBJECT ?? ^Subject: Auto-discard notification
      * 1^0 SUBJECT ?? ^Subject: El envio a [-a-zA-Z0-9]+ 
de.*precisa.*de.*aprobacion
      * 1^0 SUBJECT ?? ^Subject: Uncaught bounce notification
      * 1^0 SUBJECT ?? ^Subject: [-a-zA-Z0-9]+ post from
      * 1^0 SUBJECT ?? ^Subject: [-a-zA-Z0-9]+ subscription notification
      * 1^0 SUBJECT ?? ^Subject: [-a-zA-Z0-9]+ unsubscribe notification
      list-administrivia/
    }

Unfortunately in 3.24 this functionality is broken.  I see in the
Testing migration "excuses" this "Too young, only 4 of 5 days old".
Should severity be "important" in order to keep Testing from breaking?

Some experiments show to try to bound the condition.  It's around the
use of stdin to the sub-process.  This following works.  This does not
use stdin.

    SUBJECT=|echo hello
    SUBJECT=|echo hello | tee /tmp/pt.rwp.debug
    SUBJECT=|sh -c "echo hello | tee /tmp/pt.rwp.debug"

But this fails.  (Using a cat| pipe to ensure $SHELLMETAS are seen.)
This fails to process stdin.

    SUBJECT=|tee /tmp/pt.rwp.debug
    SUBJECT=|cat | tee /tmp/pt.rwp.debug
    SUBJECT=|sh -c "tee /tmp/pt.rwp.debug"
    SUBJECT=|sh -c "cat | tee /tmp/pt.rwp.debug"

Thank you for maintaining procmail! :-)

Bob


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages procmail depends on:
ii  libc6  2.36-8

Versions of packages procmail recommends:
ii  postfix [mail-transport-agent]  3.7.3-2+b1

procmail suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: procmail
Source-Version: 3.24+really3.22-1
Done: Santiago Vila <[email protected]>

We believe that the bug you reported is fixed in the latest version of
procmail, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila <[email protected]> (supplier of updated procmail 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 01 Apr 2024 19:35:00 +0200
Source: procmail
Architecture: source
Version: 3.24+really3.22-1
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <[email protected]>
Changed-By: Santiago Vila <[email protected]>
Closes: 1028356
Changes:
 procmail (3.24+really3.22-1) unstable; urgency=medium
 .
   * Revert to version 3.22. Fixes bug "Variable set with stdin pipe action
     fails leaving empty variable". Thanks a lot to Bob Proulx for the report.
     Closes: #1028356.
   * Most packaging changes from 3.24-1 are kept. The debian patches are taken
     from version 3.22-27 again, but renamed from NN to NN.patch.
   * Strip -Werror=implicit-function-declaration from CFLAGS.
Checksums-Sha1:
 6d9e930694aea1c1b5d7ba371a106f56b1352519 1445 procmail_3.24+really3.22-1.dsc
 cd4e44c15559816453fd60349e5a32289f6f2965 226817 
procmail_3.24+really3.22.orig.tar.gz
 3dcfeb84df77a3f6f8ddc222be7f65d13934fb37 20660 
procmail_3.24+really3.22-1.debian.tar.xz
 e33887d0c76ed1e501109fec0c08d7b1c010d2c5 5266 
procmail_3.24+really3.22-1_source.buildinfo
Checksums-Sha256:
 983de085ebdbb3b05d2f7d4e40825d23742d85b2ac0dc3cf45486cf74c2c0ad2 1445 
procmail_3.24+really3.22-1.dsc
 087c75b34dd33d8b9df5afe9e42801c9395f4bf373a784d9bc97153b0062e117 226817 
procmail_3.24+really3.22.orig.tar.gz
 6ac898a903a6afc2f145604aaddf94e8013f805407d13d446ebe93ad48fec75f 20660 
procmail_3.24+really3.22-1.debian.tar.xz
 33b1b2b36ac86a1c370b914685b72d6063a80d1354377d2da2c8a6eab2bf613d 5266 
procmail_3.24+really3.22-1_source.buildinfo
Files:
 df63a42fe8eb04386c10e2d84e61bd02 1445 mail optional 
procmail_3.24+really3.22-1.dsc
 1678ea99b973eb77eda4ecf6acae53f1 226817 mail optional 
procmail_3.24+really3.22.orig.tar.gz
 1fca977ba9495cef25f9a723448c7eab 20660 mail optional 
procmail_3.24+really3.22-1.debian.tar.xz
 66c0e9ceb41bd9be74d9adaeab7d9fa8 5266 mail optional 
procmail_3.24+really3.22-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmYK8TUACgkQQc5/C58b
izI41wf+PyHox579lozMxF5auNNYJ2FpDD1quuE6CN6Kh028I488yQIDFMbEsHo/
h9IhFEH7U9j1+fIJJMfQrdWs4CDtiCZTo6/K5jjNQWR2kbBKUmx4L0R6Hd/GV96J
45N9yl7r5S94xVBTto1fIAqLNlYg0WTOdUINFEZDhi1beQhumHPnhbfkcnKc/oen
Yy+Cd60Rm6jjimTKENanaF6tpTyX8a1U8bME4dvj2Qnv0Blp66IZ60NNjei9CtHC
8wWayb7w2Imqktee/EDLGj7j4AyX4FQLwuIDig4xKYcI4zzFBE/QMDf3kXtgoqbB
rg1WeufOwKNtQUeH0FaheVHVXXTvDw==
=buWP
-----END PGP SIGNATURE-----

Attachment: pgp1tEYICKi_r.pgp
Description: PGP signature


--- End Message ---

Reply via email to