As Rosanna Rosannadanna would say, Never mind. ;)
--
You're dating yourself. :-) I'm probably one of only a few that even get
that. :-P
Michael J. Colvin
NorCal Internet Services
www.norcalisp.com
___
spamdyke-users mailing list
I'm not that familiar with splogger but a quick search gave me several
pages that all say it sends its messages to syslog in addition to
passing them through stdout/stderr.
http://www.ezmlm.org/man/man8/splogger.8.html
Of course it's possible this is a spamdyke bug but the way you've
described
Good to hear it's working... I guess there just weren't any good
messages being delivered while you were testing filter-level?
By the way, setting the filter-level option in the global config file
is not really what I had in mind when I created that flag. Since it
overrides all other flags,
Sam Clippinger wrote:
Good to hear it's working... I guess there just weren't any good
messages being delivered while you were testing filter-level?
That's what I'm thinking.
I'm still seeing something a little peculiar though. I would expect every
smtp session to generate a spamdyke message
I think I've taken splogger out of the picture. I have qmail-send messages
going to the (proper) /var/log/qmail/send/current file via multilog.
The qmail logs look ok now. However, the spamdyke messages are still going
to both the smtpd/current log, as well as /var/log/maillog. Any idea how
that
