Jan Schneider | 5 Jan 02:34 2006

Ingo H3 (1.1-RC1)

The Horde Team is pleased to announce the first release candidate of the Ingo
Email Filter Rules Manager version H3 (1.1).

Ingo is an email-filter management application. It is fully internationalized,
integrated with Horde and the IMP Webmail client, and supports both
server-side (Sieve, procmail) and client-side (IMAP) rule creation.

This is a preview version that should not be used on production systems.  This
version is considered feature complete but a few bugs may still exist in the
code.

Testing is requested and comments are encouraged.
Updated translations would also be great.

Major changes compared to the Ingo H3 (1.0) versions are:
    * Maildrop script driver.
    * Flag-only and notify rules.
    * Moving rules by specifying their positions.
    * Portal block.
    * Compatible with PHP 5.1.
    * Support for storing Sieve rules in LDAP (Sun JES/ONE and iPlanet
      messaging servers).
    * Permissions to restrict filter rule creation.
    * Support for '^TO_' procmail rule matching.
    * New translations: Danish, Portuguese, Turkish.

The full list of changes (from version H3 (1.0.2)) can be viewed here:

http://cvs.horde.org/diff.php/ingo/docs/CHANGES?r1=1.55.2.23&r2=1.55.2.34&ty=h

(Continue reading)

garnier | 9 Jan 16:30 2006
Picon

Disabling edition of whitelist/blacklist

Hi everybody. I´ve installed Horde 3.0.5, IMP 4.0.3, Turba 2.0.3 and Ingo 1.0.2.
I would like to disable whitelist and blacklist edition for every user, but
still use them. I mean, I would like to automatically add every Turba contact
to the whitelist, but without enabling users to edit their whitelists. Is that
possible?

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

--

-- 
Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: ingo-unsubscribe@...

Jan Schneider | 9 Jan 16:53 2006

Re: Disabling edition of whitelist/blacklist

Zitat von garnier <at> hmg.click21.com.br:

> Hi everybody. I´ve installed Horde 3.0.5, IMP 4.0.3, Turba 2.0.3 and  
>  Ingo 1.0.2.
> I would like to disable whitelist and blacklist edition for every user, but
> still use them. I mean, I would like to automatically add every Turba contact
> to the whitelist, but without enabling users to edit their   
> whitelists. Is that
> possible?

This might work with locking the whitelist and blacklist preferences  
and using a preference hook to set them the correct values.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
--

-- 
Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: ingo-unsubscribe <at> lists.horde.org
Dale Hartung | 11 Jan 05:12 2006

Vacation and Forwards

List,

I've searched for some time now in the list and Google.  I cannot get the 
vacation and forwards enabled in Ingo.  It seems from previous post that 
there are options to disable these features.  Are these features disabled by

default or do they not work because of the backends that I have?  Whitelist 
and Blacklist seem to work fine and I can create new rules.  This seems to 
be the only stumper for me in horde.  I am running current stable version of

all horde apps.  Any assistance in this area would be appreciated

Dale 
Jan Schneider | 11 Jan 12:38 2006

Re: Vacation and Forwards

Zitat von Dale Hartung <dale@...>:

> I've searched for some time now in the list and Google.  I cannot get the
> vacation and forwards enabled in Ingo.  It seems from previous post that
> there are options to disable these features.  Are these features disabled by
>
> default or do they not work because of the backends that I have?  Whitelist
> and Blacklist seem to work fine and I can create new rules.  This seems to
> be the only stumper for me in horde.  I am running current stable version of
> all horde apps.  Any assistance in this area would be appreciated

Vacation and Forwards rules are not supported by all filter backends.

Jan.

--

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
Norbert Kottmann | 11 Jan 15:21 2006
Picon
Picon

* $^To:.* in Vacation Procmail Script

Hi

I am wondering why the procmail script of the vacation filter uses  
the rule:

* $^To:.*address@...

instead of:

* $^To: address@...

We had some problems with users which have two e-mail addresses with  
the same ending:

i.e. "firstname.lastname@..." and "lastname@..."

The users activated their vacation rule with both adresses (as it  
should be) and ingo writes two procmail rules for each e-mail address.

The result is, that e-mails to the "firstname.lastname@..."  
address are answered with two vacation messages because both rules "*  
$^To:.*lastname@..." and "*  
$^To:.*firstname.lastname@..." are matching.

This problem does no more appear if we use a modified version of the  
procmail.php, which does not write the regex:

$this->_action[] = '  * $^To: ' . $address;

Why is regular expression ".*" used? Is there a good reason for it?
(Continue reading)

Jan Schneider | 11 Jan 16:23 2006

Re: * $^To:.* in Vacation Procmail Script

Zitat von Norbert Kottmann <norbert.kottmann@...>:

> I am wondering why the procmail script of the vacation filter uses
> the rule:
>
> * $^To:.*address@...
>
> instead of:
>
> * $^To: address@...

Because this is an email header test, and the To: header will most  
likely not only contain the email address, but also the recipient's  
name.

I guess we should use the "* ^TO_" test instead?! But then again, I'm  
not a procmail expert.

Jan.

--

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
Lars Tobias Børsting | 11 Jan 17:10 2006
Picon
Picon

Regarding stability

Hi,

we are looking for a new email filtering solution at our university to
replace Procmail, like for example Sieve. We use the Courier IMAP
server, and unfortunately I havent been able to find a stand alone
Manage Sieve server, like Cyrus' timsieved.  I came across Ingo, and it
caught my interest. We are already using IMP for webmail.

I can see that Ingo is a rather new project. Would you consider Ingo
stable enough for a production system for about 50k users?

Thanks for your time!

-- 
Regards,

Lars Tobias Børsting
(sys.adm. at the Norwegian University of Science and Technology)
--

-- 
Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: ingo-unsubscribe@...

Jan Schneider | 11 Jan 17:29 2006

Re: Regarding stability

Zitat von Lars Tobias Børsting <lars.tobias.borsting <at> ntnu.no>:

> we are looking for a new email filtering solution at our university to
> replace Procmail, like for example Sieve. We use the Courier IMAP
> server, and unfortunately I havent been able to find a stand alone
> Manage Sieve server, like Cyrus' timsieved.  I came across Ingo, and it
> caught my interest. We are already using IMP for webmail.
>
> I can see that Ingo is a rather new project. Would you consider Ingo
> stable enough for a production system for about 50k users?

Where did you get that from? Ingo is already several years old and we  
currently prepare the second major version. It's definitely suitable  
for large production systems.
But it's probably not what you are looking for. It's a filter  
*frontend*, not a filter *engine*.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
--

-- 
Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: ingo-unsubscribe <at> lists.horde.org
Lars Tobias Børsting | 11 Jan 17:48 2006
Picon
Picon

Re: Regarding stability

Jan Schneider <jan@...> writes:

> Lars Tobias Børsting <lars.tobias.borsting@...> writes:
>
>> I can see that Ingo is a rather new project. Would you consider Ingo
>> stable enough for a production system for about 50k users?
>
> Where did you get that from? Ingo is already several years old and we
> currently prepare the second major version.

The oldest versions I have found of Ingo are from late 2004, so I
probably didn't look good enough.

> It's definitely suitable for large production systems.

That's good news.

> But it's probably not what you are looking for. It's a filter  
> *frontend*, not a filter *engine*.

Yes, it's what I'm looking for, a way for users who aren't procmail- or
sieve-savvy to use server-side filtering. I guess I didn't make myself
clear enough.

Thanks again!

--

-- 
Regards,

Lars Tobias Børsting
(Continue reading)


Gmane