** Changed in: evolution
Status: Invalid = Expired
** Changed in: evolution
Importance: Unknown = Wishlist
--
Junk mail not being identified by spamassassin plugin (daemon is disabled)
https://bugs.launchpad.net/bugs/4472
You received this bug notification because you are a member of
the upstream comment:
Closing as incomplete. Junk filtering with Bogofilter works fine in 2.30.
evolution 2.30 is in Maverick
** Changed in: evolution (Ubuntu)
Status: Triaged = Invalid
--
Junk mail not being identified by spamassassin plugin (daemon is disabled)
** Changed in: evolution
Status: Confirmed = Invalid
--
Junk mail not being identified by spamassassin plugin (daemon is disabled)
https://bugs.launchpad.net/bugs/4472
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I guess your problem is not with spamassassin, but with evolution only.
Not the same bug, thus.
--
Junk mail not being identified by spamassassin plugin (daemon is disabled)
https://bugs.launchpad.net/bugs/4472
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I am using Hardy Heron (64 bit) and the bogofilter plugin. The plugin
is enabled and the binaries are installed. Despite this, Evolution
never tags incoming mail on its own. I run an IMAP server that provides
header tagging of all incoming email. It almost unerringly places the
correct spam
** Changed in: evolution (Ubuntu)
Status: Confirmed = Triaged
--
Junk mail not being identified by spamassassin plugin (daemon is disabled)
https://bugs.launchpad.net/bugs/4472
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
** Summary changed:
- Junk mail not being identified
+ Junk mail not being identified by spamassassin plugin
--
Junk mail not being identified by spamassassin plugin
https://bugs.launchpad.net/bugs/4472
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
In Hardy bogofilter is the default plugin and the package is installed.
So this bug only affects users that change to spamassassin *and*
override the warning telling them that the spamassassin binaries are not
installed.
Should the bug be closed consequently?
** Summary changed:
- Junk mail not
