On Mon, 23 Oct 2000, David W. Tamkin spewed into the bitstream:
DWT>Collin recommended to Chuck,
DWT>
DWT>| One way to check this would be to make sure formail is in your path
DWT>| and change the recipe from
DWT>|
DWT>| | $FORMAIL ... >>$INET
DWT>|
DWT>| to
DWT>|
DWT>| | formail ... >> $INET
DWT>|
DWT>| which I *think* will skip invoking the shell.
DWT>
DWT>No, it will still invoke a shell, because a redirector is present. Procmail
DWT>needs a shell's help for any of the following:
DWT>
DWT>redirecting input from a file or output to a file ("<" and ">")
DWT>globbing filenames ("*", "?", and "[")
DWT>backgrounding ("&")
DWT>anything involving connecting two commands (piping, sequencing, conjunction,
DWT> or disjunction: in other words, "|", ";", "&&", and "||")
DWT>expanding tilde-syntax to user's or another's home directory ("~")
DWT>
DWT>Those characters make up the default value of the SHELLMETAS variable; if
DWT>procmail finds a character from $SHELLMETAS in a command string, it asks
DWT>$SHELL to take care of it. Sometimes those characters have other meanings,
DWT>
DWT>Though a shell is still invoked, I agree with Collin's advice to call pro-
DWT>grams by their basenames. That way procmail (or the shell if a shell is
DWT>invoked) can search all the directories in $PATH for the name. If you use
DWT>a full path or a variable whose value is the full path, you might have it
DWT>wrong, or the sysadmin may have moved the program.
I appreciate the ideas but I'm afraid this was/is something a bit more
serious in nature. FYI I am the sysadmin on this host as it is my
personal workstation and it's running a default (full) install of RH7
and the postfix MTA. Just to ease your minds here is the variable
setting being questioned above:
FORMAIL=/usr/bin/formail
Note that I have "sort of" solved it by "mv'ing" the file in question to
a different filename and touching an empty one... delivery to that file
began again just like normal using the exact same recipe.
What I found out is that there appears to be some sort of an issue with
RH7. I have had to make some changes to postfix to get it to work
properly.
With postfix I was seeing this:
Oct 22 13:06:03 stealth postfix/master[14362]: warning: file size limit
4294967295 < message_size_limit 10240000 -- reset
Oct 22 13:06:03 stealth postfix-script: stopping the Postfix mail
system
Oct 22 13:06:03 stealth postfix/master[25063]: terminating on signal
15
Oct 22 13:06:03 stealth postfix/master[14370]: warning: file size
limit
4294967295 < message_size_limit 10240000 -- reset
Oct 22 13:06:04 stealth postfix-script: starting the Postfix mail
system
Oct 22 13:06:04 stealth postfix/master[14407]: warning: file size
limit
4294967295 < message_size_limit 10240000 -- reset
Oct 22 13:06:04 stealth postfix/master[14407]: daemon started
Which was being caused by a problem with the Linux off_t data type in
RH7. I fixed it by patching $postfix-source/utils/file_limit.c (see
http://www.linuxguru.com/stories.php?story=51 for more info about this).
The problem I was experiencing with procmail did not return after
renaming the file name and creating an empty one and I have not tried to
recreate the issue as I have other things to do right now but I suspect
the problem is still there and is related to the off_t data type issue
and is causing an unintended limit on file sizes.
Your comments on this are appreciated... :-)
--
Chuck Mead, CTO, LinuxMall.com
csm(_at_)LinuxMall(_dot_)com
GnuPG Public Key Available: http://wwwkeys.us.pgp.net
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail