Re: [vps-mail] procmail : about reading info from ASCII files

[Scott Wiersdorf <scott@xxxxxxxxxxxx>]

On Sat, Nov 08, 2003 at 08:57:45PM -0800, Abigail Marshall wrote:
> Am I correct in assuming that this could still be done with
> the  { INCLUDERC=blocklist.rc } syntax above would be
> followed by a delivery line (i.e.:
> 
> :0
> * H ?? ^TO_me@mydomain\.com
> { INCLUDERC=blocklist.rc }
> /path/to/clients_spam_mbox

What procmail sees here is a valid recipe:

    :0
    * H ?? ^TO_me@mydomain\.com
    { INCLUDERC=blocklist.rc }

followed by a stray line:

    /path/to/clients_spam_mbox

If procmail executes the INCLUDERC directive and the mail is delivered
as a result, procmail will never see the /path/to/clients_spam_mbox
line. If the mail continues (e.g., the recipe condition was not met,
or the INCLUDERC file likewise didn't deliver the mail message),
procmail will say something like this when it reaches this stray line:

    procmail: Skipped "/path/to/clients_spam_mbox"

If the stray line doesn't have any slashes (e.g.,
"clients_spam_mbox"), procmail will treat it as a variable assignment
(actually unsets the variable):

    procmail: Assigning "clients_spam_mbox"

which isn't what we want either.

Hth,

Scott
-- 
Scott Wiersdorf
scott@xxxxxxxxxxxx
======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
======================================================================