From: Matt Simerson <m...@tnpi.net>
Date: Sat, 6 Jun 2015 20:23:46 -0700
Thanks Matt. Bits below.
> On Jun 6, 2015, at 12:16 PM, postmas...@jrd.org wrote:
>
> Are there any users of the karma plugin out there?
[matt@mail] ~smtpd/smtpd % grep karma config/plugins
karma penalty_box 0 reject 0
Heh, I still qualify. Barely...I have one last host running Qpsmtpd.
> I've been trying
> to set it up, and so far failing. When I enable it in my plugins
> file, qpsmtpd fails to start. The last line in the log, and the only
> thing that looks like it's trying to start up karma is
>
> Sat Jun 06 15:13:24 2015 g2[7780]: karma hooking pre-connection
>
> I've googled around a bit but come up empty. Is there something
> special about karma that I should be doing? Other hints on how to
> debug where it's going off the rails?
Hard to say. Make sure that the QP user can write to ./, so that
karma can write its DB files to disk. Probably best to gist the
output so we can see what other clues might be there.
Pretty sure I'm not failing on write permissions. Also pretty sure
I'm not getting to the point of trying to write.
The entire output of /var/log/qpsmtpd/<date> for a start attempt is:
Sun Jun 07 07:00:23 2015 g2[11405]: Loaded
Qpsmtpd::Plugin::logging::file=HASH(0x86252b8)
Sun Jun 07 07:00:23 2015 g2[11405]: in config(plugins)
Sun Jun 07 07:00:23 2015 g2[11405]: config(plugins): hook returned (0, )
Sun Jun 07 07:00:23 2015 g2[11405]: trying to get config for plugins
Sun Jun 07 07:00:23 2015 g2[11405]: setting _config_cache for plugins to
[jrd_config hosts_allow karma negative 2 penalty_days 1 reject 0 logging 7
db_dir /var/lib/qpsmtpd/karma check_norelay dont_require_anglebrackets
quit_fortune check_earlytalker count_unrecognized_commands 4 check_relay
require_resolvable_fromhost dns_whitelist_soft rhsbl-jrd dnsbl uribl
allow_ellie check_badmailfrom check_badrcptto_jrd badto check_spamhelo spamurl
auth/auth_flat_file rcpt_ok virus/klez_filter spamassassin reject_threshold 25
munge_subject_threshold 6 spamd_socket spamd.jrd.org:783 queue/qmail-queue]
from get_qmail_config and returning it
Sun Jun 07 07:00:23 2015 g2[11405]: in config(plugin_dirs)
Sun Jun 07 07:00:23 2015 g2[11405]: config(plugin_dirs) returning
(/usr/share/qpsmtpd/plugins /etc/jrd/qpsmtpd/plugins /etc/foo/bar) from cache
Sun Jun 07 07:00:23 2015 g2[11405]: Loading jrd_config from
/etc/jrd/qpsmtpd/plugins/jrd_config
Sun Jun 07 07:00:23 2015 g2[11405]: jrd_config hooking config
Sun Jun 07 07:00:23 2015 g2[11405]: in config(plugin_dirs)
Sun Jun 07 07:00:23 2015 g2[11405]: config(plugin_dirs) returning
(/usr/share/qpsmtpd/plugins /etc/jrd/qpsmtpd/plugins /etc/foo/bar) from cache
Sun Jun 07 07:00:23 2015 g2[11405]: Loading hosts_allow from
/usr/share/qpsmtpd/plugins/hosts_allow
Sun Jun 07 07:00:23 2015 g2[11405]: hosts_allow hooking pre-connection
Sun Jun 07 07:00:23 2015 g2[11405]: in config(plugin_dirs)
Sun Jun 07 07:00:23 2015 g2[11405]: config(plugin_dirs) returning
(/usr/share/qpsmtpd/plugins /etc/jrd/qpsmtpd/plugins /etc/foo/bar) from cache
Sun Jun 07 07:00:23 2015 g2[11405]: karma hooking pre-connection
Also, crank up the loglevel by appending 'loglevel 5' to the config file,
causing the karma plugin output to be more verbose.
I have loglevel set to 7 in /etc/qpsmtpd/loglevel
Other tidbits
I'm running on a gentoo system, up to date as of a couple weeks ago.
You can infer from the log output above, I'm augmenting the config
with my own dir of plugins. That's where I've got karma. That config
has never caused problems prior to this.
The line in plugins which loads the karma plugin is
karma negative 2 penalty_days 1 reject 0 logging 7 db_dir /var/lib/qpsmtpd/karma
I've tried a number of variations on the theme, including "karma" with
no parameters, but none of that seems to make any difference.
Any other hints? I guess my next step is to start sprinkling more
logging in the core qpsmtpd code and start figuring it out that way.
