Drew Raines <[EMAIL PROTECTED]> writes: Thanks for reply Drew > It can only assume that the owner of the controlling Python process > is the rightful UID. So TMDA is not making separation between writing user mail file (as user) - a user specific process, and writing log file - a global process ?
> > Problem is that I see that the log files are also being written > > out with the same uid.gid current at the time of specific message > > delivery, which obviously is always changing. Also I see that the > > mode on log file is 644 so after TMDA writes the log file first > > as one user then second mail delivery process (with different > > uid) cannot write to log. > > > > Can the uid.gid of the log file(s) be specified and can logs > > (optionally) be written with mode 664? > > If the log doesn't need to dynamically created by TMDA, then set > the permissions you want and leave it. As long as TMDA can still > write to it, you should get the behavior you describe. Changed uid.gid to root.tmda and 664 and debug log writes out OK now but I do see this as a work around as shouldn't TMDA be able to write out file in first place with correct rights. What happens when logs get cycled? Same problem over again? Patrick _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
