B
Bill Jones
I've been using K9 since May. It generally works very well in catching spam
but there are some operational problems. I've written to Robin about them
but they have yet to be addressed. I'm wondering if others are bothered by
these also? If so, maybe that will help Robin address them:
1. K9 has a problem when you have an address in your whitelist and the
spammer has that address embedded in their address.
Here's an example email address from a spammer:
(e-mail address removed)
If I have a whitelist rule:
From :cnet.com
K9 will pass the spam mail as good because it contains cnet.com in the From:
address!
In the current design of K9, there is nothing I can do about this problem
other than not use the whitelist. The few modifiers ("starts", "ends" and
"contains") don't offer enough granularity to address this weakness in K9.
There needs to be a "non-embedded" keyword or whatever you want to call it.
2. If you mistakenly delete an Outlook email, it would be nice to be able to
retrieve it from the K9 storage area and send it back to Outlook.
3. Even after you reclassify an email, it still winds up in the storage area
in the original classification. If you are in the Recent Emails section and
reclassify an email from Spam to Good, then click on the Organize button,
then go to the Storage Area, the email will still be in the Spam area, not
the Good one! And if you are in the Storage Area, reviewing emails there
and reclassify any mail to the opposite (Spam or Good) and hit refresh, they
don't get moved to the opposite storage area like they should. You're stuck
with where they are.
4. On the Advanced tab is a setting to "Do not add whitelisted emails to the
database". This has never worked since it was added some releases back.
5. It would be nice if K9 had the option to not route email to Outlook if
the email achieved some a scoring higher than some user defined threshold.
but there are some operational problems. I've written to Robin about them
but they have yet to be addressed. I'm wondering if others are bothered by
these also? If so, maybe that will help Robin address them:
1. K9 has a problem when you have an address in your whitelist and the
spammer has that address embedded in their address.
Here's an example email address from a spammer:
(e-mail address removed)
If I have a whitelist rule:
From :cnet.com
K9 will pass the spam mail as good because it contains cnet.com in the From:
address!
In the current design of K9, there is nothing I can do about this problem
other than not use the whitelist. The few modifiers ("starts", "ends" and
"contains") don't offer enough granularity to address this weakness in K9.
There needs to be a "non-embedded" keyword or whatever you want to call it.
2. If you mistakenly delete an Outlook email, it would be nice to be able to
retrieve it from the K9 storage area and send it back to Outlook.
3. Even after you reclassify an email, it still winds up in the storage area
in the original classification. If you are in the Recent Emails section and
reclassify an email from Spam to Good, then click on the Organize button,
then go to the Storage Area, the email will still be in the Spam area, not
the Good one! And if you are in the Storage Area, reviewing emails there
and reclassify any mail to the opposite (Spam or Good) and hit refresh, they
don't get moved to the opposite storage area like they should. You're stuck
with where they are.
4. On the Advanced tab is a setting to "Do not add whitelisted emails to the
database". This has never worked since it was added some releases back.
5. It would be nice if K9 had the option to not route email to Outlook if
the email achieved some a scoring higher than some user defined threshold.
cnet.com