-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Matt Kettler writes: > At 05:26 PM 7/13/2004, Dimitrios wrote: > >I would run to run spamd on a Linux server which also hosts several other > >peoples domains. > > > >Thus, i want to limit spamd use for me only. > > > >1) is it possible to disable spamd from binding to an IP address? even > >127.0.0.1? so that nobody can communicate to it that way. Though spamd > >should still be able to run network tests. > > No, because spamd only supports inet sockets for communication with spamc. > If it did not bind any IP nobody running spamc would be able to communicate > with it, not even you. actually -- I think --listen-ip would do that. Tell it to bind to just one interface with that. > >2) i can force it to use a Unix socket within my home dir, with restricted > >permissions. is there any other way someone could access spamd that i need > >to know? > > No, the spamd/spamc pair doesn't support unix sockets at this time, only > inet socekts. actually, it does too support unix-domain sockets ;) > >3) spamd seems to use syslog for logging. since i dont have root access to > >the machine, i dont have access to syslogd. is there a way i can tell > >spamd to log to a file (and i'd like to avoid runing my own syslogd)? > > No, at present there's no way to defeat spamd's use of syslog. > > Really, spamd is intended to be a system daemon. It's not intended to be a > "restricted to one user" tool. ...and, actually, in 3.0.0 you can log to file or to stderr. (Sorry Matt -- just had to catch you on those ;) - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Exmh CVS iD8DBQFA9GvtQTcbUG5Y7woRAq8OAKCmACubTUbe46mylwd/qYsHWlCyLgCdHVfn RveiQagvg/biFBq3mGFsr9w= =1Uiq -----END PGP SIGNATURE-----
