Sorry, Correction to typo on my previous notes:
There are spamdyke entries being captured in the /var/log/qmail/send/<current> to There are spamdyke entries being capture in the /var/log/qmail/smtp/<current> file. tim On Mon, July 27, 2009 12:15 pm, Tim Pleiman wrote: > Ok, > > So, tested and cannot get spamdyke logs to work (or they're going some > other place that I can't find or into nothing): > > SPAMDYKE="/usr/local/bin/spamdyke -lverbose" > SPAMDYKE="/usr/local/bin/spamdyke --log-level=verbose" > SPAMDYKE="/usr/local/bin/spamdyke -ldebug" > SPAMDYKE="/usr/local/bin/spamdyke --log-level=debug" > > Should be going into maillog as the default. > > Must be something I'm missing. Must something be done differently/peculiar > to the QMT integration to get these logs? > > There are spamdyke entries being captured in the > /var/log/qmail/send/<current> file, but no matter what I do with the > loglevel specifcation on the spamdyke line, it doesn't output them to > maillog on its own and it doesn't increase the level of logging in > /var/log/qmail/send/<current> > > Would like to get those more detailed logs from spamdyke. > > Any ideas? > > Thanks, > Tim > > > On Mon, July 27, 2009 11:55 am, Tim Pleiman wrote: >> Actually, >> >> I missed it. It's earlier in the documentation at spamdyke.org where the >> logs typically go: >> >> "When spamdyke logs to syslog, it uses the LOG_MAIL facility, which >> typically puts the messages in /var/log/maillog." >> >> So, presuming this is true, so I presume that adding the logging options >> to the SPAMDYKE line in "run.spamdyke" file will then log spamdyke >> messages to /var/log/maillog? >> >> Everything correct? Will try. >> >> Thanks, >> Tim >> >> On Mon, July 27, 2009 11:35 am, Tim Pleiman wrote: >>> Hi all, >>> >>> Presumably, if I want to capture a spamdyke log, I would modify the >>> following in the /var/run/qmail/supervise/run file (which with spamdyke >>> installed with QMT is a symlink to run.spamdyke, so I would modify >>> run.spamdyke): >>> >>> SPAMDYKE="/usr/local/bin/spamdyke" >>> >>> to be >>> >>> SPAMDYKE="/usr/local/bin/spamdyke -lverbose" >>> >>> or SPAMDYKE="/usr/local/bin/spamdyke --log-level=verbose" >>> >>> Is this correct? >>> >>> If so, where do the logs go? Do they go to a default location? Or must >>> that be specified? If it must be specified, is the log location to be >>> added after "-lverbose" or "--log-level=verbose" as in: >>> >>> SPAMDYKE="/usr/local/bin/spamdyke -lverbose /var/log/spamdyke.log" >>> >>> I'm not clear from the documentation at spamdyke.org as they simply >>> indicate the following: >>> >>> "/usr/local/bin/spamdyke --log-level=verbose ..." >>> >>> The 3 "dots" being something that I'm not clear on as to what else >>> should >>> be placed there. >>> >>> Thanks, >>> Tim >>> >>> -- >>> Tim Pleiman >>> Bravo Systems Technologies >>> "Advanced Open Source Solutions for Business" >>> Chicago, IL USA >>> >>> >>> --------------------------------------------------------------------------------- >>> Qmailtoaster is sponsored by Vickers Consulting Group >>> (www.vickersconsulting.com) >>> Vickers Consulting Group offers Qmailtoaster support and >>> installations. >>> If you need professional help with your setup, contact them >>> today! >>> --------------------------------------------------------------------------------- >>> Please visit qmailtoaster.com for the latest news, updates, and >>> packages. >>> >>> To unsubscribe, e-mail: >>> [email protected] >>> For additional commands, e-mail: >>> [email protected] >>> >>> >>> >> >> >> -- >> Tim Pleiman >> Bravo Systems Technologies >> "Advanced Open Source Solutions for Business" >> Chicago, IL USA >> >> >> --------------------------------------------------------------------------------- >> Qmailtoaster is sponsored by Vickers Consulting Group >> (www.vickersconsulting.com) >> Vickers Consulting Group offers Qmailtoaster support and >> installations. >> If you need professional help with your setup, contact them today! >> --------------------------------------------------------------------------------- >> Please visit qmailtoaster.com for the latest news, updates, and >> packages. >> >> To unsubscribe, e-mail: >> [email protected] >> For additional commands, e-mail: >> [email protected] >> >> >> > > > -- > Tim Pleiman > Bravo Systems Technologies > "Advanced Open Source Solutions for Business" > Chicago, IL USA > > > --------------------------------------------------------------------------------- > Qmailtoaster is sponsored by Vickers Consulting Group > (www.vickersconsulting.com) > Vickers Consulting Group offers Qmailtoaster support and > installations. > If you need professional help with your setup, contact them today! > --------------------------------------------------------------------------------- > Please visit qmailtoaster.com for the latest news, updates, and > packages. > > To unsubscribe, e-mail: > [email protected] > For additional commands, e-mail: > [email protected] > > > -- Tim Pleiman Bravo Systems Technologies "Advanced Open Source Solutions for Business" Chicago, IL USA --------------------------------------------------------------------------------- Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! --------------------------------------------------------------------------------- Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
