Lloyd Zusman <[EMAIL PROTECTED]> writes: > The reason I manually set SENDER in cases such as these is because > TMDA throws an exception if there is no sender set.
Right, because $SENDER is how TMDA gleans the envelope sender address of the message. > there are cases where my MTA doesn't get a chance to force the > SENDER variable to be set. You are using Courier and/or maildrop no? > Is there any way that a future version of TMDA might handle the > no-SENDER case gracefully? ... How then would TMDA be able to distinguish between a misconfiguration ($SENDER is not set), and an empty envelope sender address ($SENDER is set, but has a null value)? Another user discovered[1] that maildrop removes variables from the environment if they have an empty value. He reported[2] the problem on the maildrop list, but AFAIK nothing was done about it. I believe this is a bug in maildrop and would like to see it fixed there. Footnotes: [1] http://mla.libertine.org/tmda-users/2003-08/msg00185.html [2] http://www.riverside.org/archive/html/maildrop/2003-08/msg00061.html _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
