[spambayes-bugs] [ spambayes-Bugs-944109 ] notate_to/subject option valid values should be dynamic

SourceForge.net noreply at sourceforge.net
Wed Apr 28 20:52:09 EDT 2004


Bugs item #944109, was opened at 2004-04-29 12:52
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=944109&group_id=61702

Category: pop3proxy
Group: Source code - CVS
Status: Open
Resolution: None
Priority: 1
Submitted By: Tony Meyer (anadelonbrin)
Assigned to: Tony Meyer (anadelonbrin)
Summary: notate_to/subject option valid values should be dynamic

Initial Comment:
The notate_to/notate_subject options are currently
hard-coded to accept "ham", "spam" or "unsure" as valid
values.  This is always the case unless the user has
changed the
header_ham_string/header_spam_string/header_unsure_string
options, in which case the values should be the same as
those.

This means that you can't use the
notate_to/notate_subject option if you have changed
those values.  This isn't a big deal, because changing
those values is almost always unnecessary.  Even for
Outlook Express users - how many times do they get
actual mail that has "spam," in the recipient list? 
Even the simpler "spam," in the subject (note the
comma) should be rare.

As such, I don't want to check this in before 1.0,
because it might break something.  After that, though,
there should be code in Options.py that dynmically sets
(when it's loaded) the appropriate bits of
notate_to/notate_subject to whatever the
header_X_strings are.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=944109&group_id=61702



More information about the Spambayes-bugs mailing list