"Corey Crawford" <[EMAIL PROTECTED]> writes: > What other program than tcpserver/tcprules uses /etc/tcp.smtp?
None. Only the tcpserver which invokes qmail-smtpd uses /etc/tcp.smtp.cdb (not tcp.smtp) /etc/tcp.smtp is only used by tcprules for building the cdb-file. > I still don't see why vpopmail's ebuild can't use > /var/vpopmail/etc/tcp.smtp. vpopmail can (and probably does) use it only for writing the IP-addresses of the pop3'ing clients to it and afterwards invokes tcprules to build the cdb file. > Or, I suppose, it could link to /etc/tcp.smtp but build it's own > tcp.smtp.cdb file in /var/vpopmail/etc/ (since it doesn't actually > edit tcp.smtp but rather updates tcp.smtp.cdb). Yes. And if this tcp.smtp.cdb (*not* tcp.smtp) would be used by the tcpserver which invokes qmail-smtpd SMTP-after-POP would work for a limited period for each IP-address which was recorded by vpopmail. > You yourself say you don't want arbitrary users to be able to write to > config files in /etc, but then why does the now-default ebuild of vpopmail > require this? In this point I agree with Daniel. But I don't understand why the tcpserver which invokes qmail-smtpd should not use the cdb-file which was built by vpopmail. Simply replacing the -x option would archive this. Martin -- [EMAIL PROTECTED] mailing list
