In article <[EMAIL PROTECTED]>, Doug Hardie <[EMAIL PROTECTED]> wrote:
> I am doing the initial testing of tmda and installed it with minimal > configuration. I setenv for RECIPIENT, SENDER, and EXTENSION and > manually cat'd a message to tmda. It recognized that it needed to send > a confirmation which it did, but then it put the incoming message in > root's pending directory, not the user's. The .tmda directories exist > for both root and the user. Keygen was run for both. The config file > is basically the one in examples. A ktrace of tmda shows that it never > accesses anything for the user, just root. I have run the cat as both > the user and root with the same results (except when run as the user it > can't actually write to root's pending directory). What am I missing? The problem is that os.path does not properly resolve ~ if the user is defined via NIS. It only works for users defined in /etc/passwd. I think that needs to be pointed out as a limitation of tmda. _____________________________________________ tmda-users mailing list (tmda-users@tmda.net) http://tmda.net/lists/listinfo/tmda-users
