Re: [Evolution] How to handle unsolicited e-mails with evolution 2.32.2 ?



On Mon, 2011-11-28 at 09:11 +0100, Andre Klapper wrote:
On Sat, 2011-11-26 at 19:20 -0430, Patrick O'Callaghan wrote:
On Wed, 2011-11-23 at 16:52 +0100, Andre Klapper wrote:
On Wed, 2011-11-23 at 10:47 -0430, Patrick O'Callaghan wrote:
On Wed, 2011-11-23 at 15:00 +0100, Andre Klapper wrote:
http://library.gnome.org/users/evolution/3.2/mail-spam.html

Actually I would dispute that. I know the latter URL is now the official
FAQ, and it certainly looks nice, but I feel the info in the original
FAQ is currently a bit more complete, at least for this specific
question. That's why I referenced it.

I see... Which bits are missing?

For one thing, the new FAQ says nothing about how to train the junk
filters. The old FAQ at least mentioned this as something you need to
do.

Thanks. I've filed https://bugzilla.gnome.org/show_bug.cgi?id=665008 .
If more stuff comes to your mind don't hesitate to file bug reports.

Of course. I'm never happier than when finding fault :-)

If you feel like patching, these files are named mail-spam*.page in
http://git.gnome.org/browse/evolution/tree/help/C/

Also, the new FAQ points the user
to specific SourceForge pages to install Bogofilter or SpamAssassin. Not
a good idea IMHO, as most distros already offer them via their usual
installation mechanisms.

That's the default fallback on the web version. 
On your harddisk (Help > Contents) this will start your package
management application instead (on Fedora 16: gnome-packagekit).

Both the builtin Help and the FAQ refer directly to the Sourceforge
pages.

The SF page is the fallback if the "install:" link is not interpretable
by your version of Yelp (GNOME's help browser). 
It's a feature (I could have also dropped that URL completely, but then
you'd now write that clicking it doesn't do anything :P ).
I'm wondering which distro and Evolution version you use...

Fedora 15, Evo 3.0.3. However my desktop is KDE rather than Gnome, so I
don't see Yelp unless I run it explicitly. That might be the reason.

poc





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]