Lloyd Zusman <[EMAIL PROTECTED]> writes:
>>> I think I can't submit that as a patch. I would have to introduce
>>> some means of deleting variables in the maildrop
>>> scriptlanguage.. too hard for me. So I'm going to send a bugreport.
>>
>> Did the maildrop maintainers ever respond to this? I saw your post to
>> the mailing list, but no followups. I'd hate for maildrop to be
>> incompatible with TMDA simply because of this.
>
> I don't understand why one would want to delete variables.
I think Hans mentioned deleting to provide a way to preserve existing
maildrop behavior as to not introduce a backwards compatibility problem.
> Wouldn't it be possible to do this in maildrop? ...
>
> import SENDER
> if ( "X$SENDER" eq "X" )
> {
> SENDER=""
> }
>
> It forces a missing or empty SENDER environment variable to be set with
> a blank value.
>
> Would a blank SENDER be acceptable to TMDA?
A blank SENDER to TMDA means a null envelope sender address (i.e,
<>). So yes, I think you could do this, but it would be nicer if you
didn't have to (if maildrop didn't delete empty variables).
Let us know if it works, and maybe we can write up a FAQ entry or
something.
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
