In article <[EMAIL PROTECTED]>, Stephen Warren <[EMAIL PROTECTED]> wrote:
> The Python module will use HOME directly if it's set. If it is not set, > the standard C library routines will be used to obtain HOME information > from /etc/passwd (or whatever /etc/nsswitch.conf is set to). > > As such, for HOME explicitly, there is no need to have any form of > wrapper at all; Python will just work with sendmail. > > I would guess then that most MTAs simply clear, or never set, the HOME > variable and hence Python always "falls back" to C library routines. > > > The wrapper is only about 25 lines of c code. Very straight forward > > once you know HOME has to be set. That should be included in the > > documentation rather than presuming its set magically by something else. > > There's no need to document anything - when TMDA is run from the > intended environment (sendmail, postfix, qmail, exim, ...) it will just > work. Unfortunately you are presuming a specific sendmail setup which must be exactly that way or tmda does not work. In an ISP environment it may not be possible to use that "specific" sendmail setup. The LDA may have to run as root and not the recipient user's id. Tmda out of the box does not support that. However, its fairly easy to correct that by setting the HOME env. Unless you are going to restrict tmda use to toy environments then it needs to be documented. A number of other interesting facets have show up during testing. Tmda uses sendmail to deliver previously queued messages after the confirmation is received. This incurs a second overhead of all the sendmail processing including any virus filtering etc. Why doesn't it just deliver using the defined MDA or the one that is built into tmda? _____________________________________________ tmda-users mailing list (tmda-users@tmda.net) http://tmda.net/lists/listinfo/tmda-users
