CertaintyTech - Ed Henderson wrote: > > > Somebody else mentioned another perl program that looked like it was > > > perhaps using the /dev/log syslog interface - you might > > investigate that. > > > If you don't need remote logging enabled, it's best to disable it. > > > > > > -- > > > Charlie Watts > > > > > The question that I have is "why does Spamd require remote logging to be > enabled when it is running locally on my server where syslogd resides?" > Does syslogd see the connection from spamd as a network connection rather > than a local socket? Any way that spamd could be modified so as not to act > this way? Or is this a Solaris specific problem?
Personally, I don't care if syslogd allows "network" logging through UDP, because I: 1. Only bind to 127.0.0.1 2. Firewall the syslog port on the local machine for TCP and UDP 3. Firewall the syslog port at the network edge Voila, no openings for DoS from syslog, yet full functionality on the local machine. C _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
