Hi.
I have just reuploaded version 3.22.
This is certainly not the ideal state for this ancient
package, but I believe it's slightly better than keeping
an important regression forever.
If upstream decides to maintain procmail again (which means
addressing regressions, not merely making a new
Hello.
This is what I did today. Maybe someone can follow my steps
and arrive at something.
I'm using this $HOME/.procmailrc file:
-
LOGFILE=$HOME/.cache/procmail.log
VERBOSE=yes
:0 h
SUBJECT=|formail -cXSubject:|cat
MYVAR=$SUBJECT
:0
/dev/null
forwarded 1028356 https://github.com/BuGlessRB/procmail/issues/5
tags 1028356 + help
thanks
Hi. I've forwarded the bug by making a github issue from it.
There is a full git history for procmail at github. If you
feel brave enough you could try a git-bisect on the code
to see where this bug was
El 9/1/23 a las 23:13, Bob Proulx escribió:
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?
I've just set it to serious, which is the
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
5 matches
Mail list logo
