Noah Meyerhans wrote: > Bastian Kleineidam wrote: > > As you can see below, I use sa-update to download a custom > > channel for german spam rules. > > Future versions of spamassassin will store the default gpg key in > /var/lib/spamassassin/sa-update-keys, which will be created during > installation. If you want to import other keys, you can either pass > "--gpghomedir /var/lib/spamassassin/sa-update-keys" (or some other > directory) to sa-update, or you should create > /etc/spamassassin/sa-update-keys yourself. Since this directory will not > be used in the default configuration, it won't be created by the > package.
Now that we have newer versions of spamassassin uploaded to the archive and /var/lib/spamassassin/sa-update-keys is being created and all is looking okay to me is the status of this bug now done? I think it is done and should be closed. Comments? Otherwise I will wait a few days and mark this ticket done. Bob Proulx wrote: > I use sa-update to update the sought rules channel. Since the recent > upload of 3.3.2-3 I have found that the following recipe in > /etc/cron.daily/spamassassin is required to do this successfully > without errors from the cron task. > > I do not claim that this is correct. Only that I could find no other > method to have it work successfully. All other combinations and > permutations that I tried produced various errors. > > # Update > umask 022 > su debian-spamd -c "sa-update --gpghomedir > /var/lib/spamassassin/sa-update-keys" > sa-update --gpgkey 6C6191E3 --channel sought.rules.yerp.org > > Any comments from the maintainer on the new preferred method to update > custom rulesets would be read with attention. I should have updated this ages ago. I am now using this recipe successfully with recent versions of spamassassin including 3.3.2-5 and the later 3.4.0-1. su - debian-spamd -c "sa-update --gpghomedir /var/lib/spamassassin/sa-update-keys --gpgkey 6C6191E3 --channel sought.rules.yerp.org --channel updates.spamassassin.org" Bob
signature.asc
Description: Digital signature
