Paul Thomas wrote, cryptically,
| I'm trying to 'nest' INCLUDERC's in my
| /etc/procmailrc file like this:
That should be no problem as long as the depth doesn't exceed your kernel's
limit on the number of file descriptors a process can have open
simultaneously.
| :0
| * ^To:.*somebody
| {
| INCLUDERC=/etc/procmail/rc.script
| >
You open with a left brace and close with a right-side angle-bracket? That
won't work. Could that be causing the problem, or was the angle bracket
just a transcription error in your post for a right brace in your rcfile?
If you do have a right brace there, what is happening instead?
| but the INCLUDERC fails ...
What do you mean when you say that it "fails"? What happens instead? If
you get an error message in your logfile, what does it say?
| ... unless I do:
|
| :0
| * ^To:.*somebody
| {
| INCLUDERC=/etc/procmail/rc.script
| :0
| $DEFAULT
| }
That's strange. There has to be more to it than you've told us. If you
didn't add the dump to $DEFAULT (which should have a second colon for a
local lockfile unless $DEFAULT is a directory), you should get exactly what
you say you want:
| I would like when the condition is met, for rc.script
| to execute then continue to the end of /etc/procmailrc
| before being delivered.
So I'm baffled. What is going on in /etc/procmail/rc.script?
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail