Topic: How to turn on filters in webmail?

[jeffco01]

Hello,
  I've ran all the searches I could think of, but found no answers. Hopefully someone here can help?

I'm running V7-rc2. Once in webmail, under options for mail, there is a link to set up "filters". Once I select it, I receive a message "Filter Not Active" and "Filter support is disabled on this system".

How do I activate this filter? I'm looking for a way to let customers have black/white filters. this sounded like it would be it. (?)

Is there any other way to have black/white filters on the server?

Thank you for any help!
Jeffrey

[crazybob]

take a look at this thread on adding to spamassassins white and black lists.
http://forums.contribs.org/index.php?topic=31227.0

I use this ad it seems to work well

Bob

[mrjhb3]

Hello,
  I've ran all the searches I could think of, but found no answers. Hopefully someone here can help?

I'm running V7-rc2. Once in webmail, under options for mail, there is a link to set up "filters". Once I select it, I receive a message "Filter Not Active" and "Filter support is disabled on this system".

How do I activate this filter? I'm looking for a way to let customers have black/white filters. this sounded like it would be it. (?)

Is there any other way to have black/white filters on the server?

Thank you for any help!
Jeffrey

Is this a new install, or an upgrade? When I click on options/mail/filters, I get a screen to set my filters.  In horde 3.x ingo is the component that provides filter support.  Is ingo installed or did you happen to remove it for some reason?

[root@www ~]# rpm -qa | grep ingo
e-smith-ingo-1.0.0-01
ingo-h3-1.0.2-02sme01

OK, I can duplicate this, by editing horde/registry.php and setting line 109 to inactive.  

So, from what I can gather, either you have uninstalled ingo, manually set ingo to inactive, or may have a custom-template for ingo that sets it to inactive.  The file to check is /home/httpd/html/horde/config/registry.php, then check your templates and templates-custom directories.

JB

[JonB]

jeffco01,

These are not systemwide filters. They only filter mail when you log into webmail.

There is no way currently of having per user whitelist/blacklists on a system basis.

Jon

[jeffco01]

Is this a new install, or an upgrade? When I click on options/mail/filters, I get a screen to set my filters.  In horde 3.x ingo is the component that provides filter support.  Is ingo installed or did you happen to remove it for some reason?

[root@www ~]# rpm -qa | grep ingo
e-smith-ingo-1.0.0-01
ingo-h3-1.0.2-02sme01

Hi JB,
  Thanks for the help. This is a new install. Since I am a "Windows user that's seen the errors of my ways (!)" I try not to mess around with adding/removing things unless I've been told to by one of you guru's.

When I type "rpm -qa | grep ingo", all get as an output is returned to the prompt. It doesn't say anything about ingo... installed or not.

OK, I can duplicate this, by editing horde/registry.php and setting line 109 to inactive.

In registry.php, ingo is "active" (although I noticed that it is not at line 109, would that make a difference? I wouldn't think so)  

So, from what I can gather, either you have uninstalled ingo, manually set ingo to inactive, or may have a custom-template for ingo that sets it to inactive.  The file to check is /home/httpd/html/horde/config/registry.php, then check your templates and templates-custom directories.

I don't know what I'm doing wrong? I have done a fresh install on three test servers, haven't removed anything and, when running "fresh out of the box" I get the bit about "Filter support is disabled on this system" on all three installs.

It doesn't look like ingo is installed.(?) Could you give me a quick "howto" on getting it in there?

Just to be sure we're using the same versions... in webmail, if I select "help/about" (after selecting horde and then mail, respectively) I get "Imp H3 (4.03)" and "Horde (3.04)". Is this current?

If I keep at this long enough, maybe I can eventually call myself a "Linux Guy"!
Thank you for all the help!
Jeffrey

[jeffco01]

take a look at this thread on adding to spamassassins white and black lists.
http://forums.contribs.org/index.php?topic=31227.0

I use this ad it seems to work well

Bob

Hi Bob.
Thanks for the link. I had looked at this earlier, and I'm sure I'll end up using this. For now, though, I'm trying to get the filters in Webmail functional. It's weird that it isn't working already.

Thanks, again,
Jeffrey

[mrjhb3]

Hi JB,
  Thanks for the help. This is a new install. Since I am a "Windows user that's seen the errors of my ways (!)" I try not to mess around with adding/removing things unless I've been told to by one of you guru's.

When I type "rpm -qa | grep ingo", all get as an output is returned to the prompt. It doesn't say anything about ingo... installed or not.

...
I don't know what I'm doing wrong? I have done a fresh install on three test servers, haven't removed anything and, when running "fresh out of the box" I get the bit about "Filter support is disabled on this system" on all three installs.

Jeffrey,

If you get the same results after installing on three different test servers, I'd check the MD5SUM of the ISO on http://mirror.contribs.org/smeserver/releases/7/iso/ versus what you downloaded.  Ingo is part of the core install on SME7.  I believe you could also check your install.log on your server and see if there are any errors related to trying to install ingo.  In either case, I'd download the ISO again and re-install.

JB

[jeffco01]

 you get the same results after installing on three different test servers, I'd check the MD5SUM of the ISO on http://mirror.contribs.org/smeserver/releases/7/iso/ versus what you downloaded.  Ingo is part of the core install on SME7.  I believe you could also check your install.log on your server and see if there are any errors related to trying to install ingo.  In either case, I'd download the ISO again and re-install.JB

JB,
  I checked the MD5sum, and they match! I also checked the install.log and, even though I see no errors, I also don't see any mention of Ingo. I even used Midnight Commander, opened the log, and ran a search just to make sure I didn't miss it somewhere along the way. This gets stranger by the minute!

Could you give me some instruction on installing Ingo? Maybe I can get it done that way. I'm farely new to Linux, so I'm learning command-line commands as I go.

Installing it again, with the same copy I have won't do me any good. And I'm not where I have a fast enough connection right now to download another. Looks like my choices are slim. If I could do an yum upgrade for the whole server, or just manually install Ingo, I might salvage this. But I'm just not sure how to do either.

As always, any help would be appreciated... thanks for the help so far, too!

Jeffrey

[mrjhb3]

JB,
  I checked the MD5sum, and they match! I also checked the install.log and, even though I see no errors, I also don't see any mention of Ingo. I even used Midnight Commander, opened the log, and ran a search just to make sure I didn't miss it somewhere along the way. This gets stranger by the minute!

Could you give me some instruction on installing Ingo? Maybe I can get it done that way. I'm farely new to Linux, so I'm learning command-line commands as I go.

Jeffrey

That is so odd, my install.log shows:
Installing ingo-h3-0:1.0.2-02sme01.noarch.
Installing e-smith-ingo-0:1.0.0-01.noarch.

Anyway, on my test server, I did this:
mkdir -p /mnt/cdrom
mount /dev/cdrom /mnt/cdrom
mount: block device /dev/cdrom is write-protected, mounting read-only

cd /mnt/cdrom
cd CentOS/
cd RPMS/
ls * | grep ingo
e-smith-ingo-1.0.0-01.noarch.rpm
ingo-h3-1.0.2-02sme01.noarch.rpm

rpm -Uvh e-smith-ingo-1.0.0-01.noarch.rpm
rpm -Uvh ingo-h3-1.0.2-02sme01.noarch.rpm

yum update   <-- Doesn't have to be done, but if you're going to do the post-upgrade might as well be as current as possible.

signal-event post-upgrade ; signal-event reboot

[jeffco01]

JB,

Oohh Yea!!! That did it!  I have no idea why this didn't install in the first place (?) but, with your help, it's running now!

Thank you for taking the time with me.

Jeffrey