I didn't notice your answer to this Lloyd - maybe I missed it? I was thinking you were just being safe - in case somethign left SENDER unset - or unset it on purpose - and you didn't want tmda to break - yes?
m/ > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Jason R. Mastaler > Sent: Thursday, January 15, 2004 10:11 PM > To: [EMAIL PROTECTED]; Lloyd Zusman > Subject: Re: Newbie with difficult config and partial success... > > > Lloyd Zusman <[EMAIL PROTECTED]> writes: > > > The maildrop change works like this: > > > > - The following construct no longer deletes the enviroment variable: > > > > SENDER="" > > > > Rather, this variable now properly contains an empty string. > > [...] > > > import SENDER # causes maildrop to notice SENDER, if it's set > > SENDER="$SENDER" # forces null string, even if SENDER was unset > > xfilter "/usr/local/tmda/bin/tmda-filter -p" > > Is the SENDER="$SENDER" line really necessary? It seems like it > shouldn't be with the new maildrop behavior. > _____________________________________________ > tmda-users mailing list ([EMAIL PROTECTED]) > http://tmda.net/lists/listinfo/tmda-users > _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
