According to Andreas Klemm:
> procmail 3.14 bug, or does the new procmail version introduce
> some new features in area where in -current is something wrong.
> Not easy to say for me ...
Check your locking settings on both versions. You may find that you're using
different locking mechanisms...
On Sun, Jan 02, 2000 at 08:00:03PM +0100, Andreas Klemm wrote:
> A few days ago I updated -current and build /usr/local completely new.
> One remaining problem is, that procmail jobs seems to hang.
> First it was a port problem, I installed some (for me) basic services
> in /home/local and procma
Well, found out, that I don't have any problems using the previous
version of procmail 3.13.1.
So it's solved for me now. The remaining question is, is this a
procmail 3.14 bug, or does the new procmail version introduce
some new features in area where in -current is something wrong.
Not easy to
A few days ago I updated -current and build /usr/local completely new.
One remaining problem is, that procmail jobs seems to hang.
First it was a port problem, I installed some (for me) basic services
in /home/local and procmail tried to call /usr/local/bin/formail.
Now I recompiled procmail usin