On Fri, Jul 16, 2004 at 8:52:12AM +0200, Dallman Ross wrote:
[slightly rearranged]
(Also, I don't see why you thought you needed a lock.)
For the case where the delivery is to a file. Sorry to be unclear;
other production environments have things like:
raw-input = raw-stuff #for production
and I assume you'd agree that that needs a lock!
While I must say up-front that I don't really care for this style,
I will nonetheless not get into a discussion about that aspect right
now but will try to help. :-)
I'd like to hear of better suggestions of how to share common code
among several environments. Right now, I've got two PITA files
installed in production, and a third back at the sandbox. The sandbox
can share with the file-name environment. but nobody can share with
the mail-to environment. For that, I've had to simply insert
:0 c:
! $maintainer
all throughout the code, while waiting to tumble onto a better
solution. I REALLY hope I'm done with basic development on this one... :)
MYCMD # unset for development
MYCMD = "$SENDMAIL $SENDMAILFLAGS $maintainer" # for production
:0 c
* conditions
| $MYCMD
*Might* work. Not entirely sure.
Seems problematical with a file delivery, but probably a basis for more
promising experimentation on my part.
Thanks for the thoughts, and sorry to not give a more complete description
of the situation; I thought the file-name delivery would be sort of taken
for granted as part of the delivery set in a general sandbox discussion.
Jim
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail