[ingo] Enable Spam Filter by default (using sieve)?
Jan Schneider
jan at horde.org
Mon Jun 20 18:45:31 UTC 2011
Zitat von Kareem Dana <kareem.dana at gmail.com>:
> On Mon, Jun 20, 2011 at 3:31 AM, Jan Schneider <jan at horde.org> wrote:
>
>>
>> Zitat von Kareem Dana <kareem.dana at gmail.com>:
>>
>>
>> I have ingo setup with the sieve backend. When a new user logs in for the
>>> first time, both Vacation and Spam Filter are disabled. I believe this is
>>> because ingo has to upload the sieve script to the server before it can
>>> enable those rules.
>>>
>>> Is there a way to perform that task when a new user first logs in? I'm
>>> thinking some hook that will execute each time a user logs in and checks
>>> the
>>> last_logged_in value and if its Never then automatically tell ingo to
>>> enable
>>> the spam filter. Does such a horde or ingo hook exist? Maybe
>>> postauthenticate() or appinitialized() and if so, can I direct ingo to
>>> enable the filter from a horde hook? Or if this is the wrong way to go
>>> about
>>> it, please let me know.
>>>
>>
>> To *enable* those rules, you just have to change the default value for the
>> 'rules' preference in ingo/config/prefs.php. What you describe is only
>> necessary if you also want to *activate* the Sieve rules by default.
>>
>> But I suggest you better set default Sieve rules directly on the server for
>> new users, because only then you are sure that those rules are active, even
>> if the user didn't use webmail so far.
>>
>> Jan.
>>
>
> That worked. This is a test setup of Horde, and I had changed ingo to use
> the SQL driver backend, so those prefs values weren't working. It looks like
> the SQL driver has the SPAM filter hard coded to disabled = true when it
> first inserts it into the database. However, I prefer the prefs backend, so
> all is well.
Actually the sql driver should pull in the defaults from the preferences.
Jan.
--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
More information about the ingo
mailing list