http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5782
Summary: sa-update should warn if a nonexistent channel is used
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P5
Component: sa-update
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
from users list:
'[no rules are firing after upgrade to 3.2.4.] I use sa-update, and multiple
channels.
/usr/bin/sa-update --allowplugins --channelfile /etc/spamassassin/channels.txt
--nogpg
My /etc/spamassassin/channels.txt:
--------------------------------------(8<)------------------------------------------
update.spamassassin.org
72_sare_redirect_post3.0.0.cf.sare.sa-update.dostech.net
70_sare_evilnum0.cf.sare.sa-update.dostech.net
70_sare_bayes_poison_nxm.cf.sare.sa-update.dostech.net
70_sare_html0.cf.sare.sa-update.dostech.net'
Note that update.spamassassin.org should be updates.spamassassin.org;
the reporter fixed this and the problem went away.
Right now, if a nonexistent channel name is used (like
'update.spamassassin.org'), sa-update will attempt to lookup
4.2.3.update.spamassassin.org, find no records, and assume there's
no updates published yet. In fact however there's no update channel there at
all!
We could detect this by adding a record which must exist for a channel to be
valid: _validchannel.updates.spamassassin.org or whatever. if that record
doesn't exist, sa-update issues a warning.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.