On Thu, 05 Mar 2015 10:35:54 + Ralph Corderoy sez:
> > find_draftmessage() {
> > skip_next=0
> >
> > for arg; do
> > case "$arg" in
> > -al* | -filt* | -wi* | -client | -idanno | -server | \
> > -partno | -saslmaxssf | -saslmech
Thanks for the proposed localpostproc, Ken!
Unfortunately, I don't think I can use it, due to a lack of a
looping mechanism -- or, at least, a "there-exists" mechanism.
I need something that checks the recipients' host(s), which
means potentially checking more than 1 string. The pseudo-code
would
On Thu, 05 Mar 2015 22:47:34 -0500 David Levine sez:
> Ken wrote:
>
> > >Have the interface to post(8), and thus postproc, include the
> > >`file' parameter as an environment variable as well. True, this
> > >means post has two places to get the data, but it also keeps simple
> > >filter script
On Fri, 06 Mar 2015 11:49:12 + Ralph Corderoy sez:
> Hi Ken,
>
> > > Though I still think it should be the last argument,
> > > otherwise every postproc author has to solve the same
> > > problem.
> >
> > I don't have strong feelings about this one; thoughts from
> > others? Fixing it is a
On Tue, 03 Mar 2015 20:56:11 -0500 David Levine sez:
> Bob wrote:
>
> > Funnily enough I was just starting to think about how to deal
> > with this. My first thought was to maintain 2 .mh_profile files
> > and alias commands to set a soft link to the appropriate
> > depending on the recipient.
