Hi Steve, I wonder if in your email (below) you have your lines slightly
out of order:
> My .procmailrc:
> "|/usr/local/bin/procmail -f -"
I am thinking that is your .forward file.
and
> Not sure if this is your problem or not.? But I have quite a large .procmailrc
> file (200 lines) that makes? a historical archive of every incoming email,
I gather that you put all your procmail filtering directly into your
.procmailrc file. I think it was usually the case that
Or is this is a reference to a something.rc file in the ~/Procmail
directory?
My .procmailrc file looks like this:
# Turn off extra words in log file set to yes for debugging
VERBOSE=no
# For debugging uncomment this line
LOGABSTRACT=all
# Tell procmail where to store your mail. This changes depending on
# which Unix mail client you use.
# Pine uses $HOME/mail
# Mutt and Elm use $HOME/Mail
MAILDIR=$HOME/mail #This directory must exist!!!
# Use a seperate directory to store recipes and logs
PMDIR=$HOME/Procmail
# Tell procmail where to put the log file
LOGFILE=$PMDIR/procmail.log
# Add recipe files here
# To add more recipe files just add an INCLUDERC=$PMDIR/filename.rc
# line for each file
#INCLUDERC=$PMDIR/testing.rc
INCLUDERC=$PMDIR/lists.rc
# Finally if the above recipes fail to move your mail put it in your
# inbox
:0:
# Above is a zero (0) not the letter O.
$DEFAULT
Austin
PS: I solved my problem with your help above. Thanks! It has to do with
the differences in how the new smtpd process deals with aliases which are
pipes to programs or scripts. It does not handle complex command line
equivalents with definitions of environment variables preceding the
invocation of the program being called up. I wonder if it even handles
the typical command lines that have the kind of "if this succeds, then do
that also, but if any invoked process fails do the other" -- the usual
&& or || connectors one often sees in major shell scripts.
That kind of usage in the .forward file is what screws up a lot of custom
scripts I wrote for myself years ago.
I haven't had a chance yet to look to see if procmail still recommends
that kind of .forward file. Later I will submit a report to misc@ or
ports@
The .forward file used to recommended by procmail to look like this:
"|IFS=' ' && exec /usr/local/bin/procmail -f- || exit 75 #austin"
That caused an error "cannot expand alias" ( or something like that --
neatly misleading --- as usual in debugging problems... ) :-)
Still have to find time to study the newer replacement folks are
recommending for procmail. I gather most everyone else has left procmail
in the dust....
====================================================
On Wed, 27 Jan 2021, Steve Williams wrote:
> Hi,
>
> I am using procmail under 6.8 successfully.? I did have problems with it when
> upgrading to (I think) 6.4.
>
> If you look for the mail list archives for "OpenBSD 6.4 smtpd local mail
> delivery missing "From " when .forward (procmail)"
>
> My .procmailrc:
>
> "|/usr/local/bin/procmail -f -"
>
> Not sure if this is your problem or not.? But I have quite a large .procmailrc
> file (200 lines) that makes? a historical archive of every incoming email,
> filtering maillist emails, etc.
>
> Thanks,
> Steve W.
>
>
> On 26/01/2021 10:43 a.m., Austin Hook wrote:
> > Wonder if anyone is still using Procmail/Formail under 6.8 for presorting
> > incoming mail before it hits one's main inbox.
> >
> > Also wondering if folks send the remainimg mail, after filtering, to
> > /var/mail/*user*, or to ~/mbox or to ~mail/mbox. Any advantage to be had,
> > or any mere consensus, regardless of advantages?
> >
> > I also use whitelisting extensively, and any such "From: emailaddresses"
> > get priority. Does anyone else?
> >
> > Myself: Having problems with Procmail/formail, after upgrading from 5.3 to
> > a new server running 6.8. Would like to hear of anyone else's experience.
> >
> > Thanks,
> >
> > Austin Hook
> > Milk River, Alberta
>
