Re: [Phpgroupware-developers] New features in Mail app

[Dan Kuykendall (Seek3r)]

I think this is probably the best plan. Allow us to do regexp against
the different mail parts and then take some action against those that
match. We will want this to be run in order of the list as well.
The mail filter settings should be stored using the preferences class.

Once you have this part working, which seems to me to be reasonably easy
enough, then we can (as Patrick said) start working on the dummy
interface. The best dummy interface is the one used by Outlook, so we
can try and model it after that. Also modeling after Outlook would help
users transition.

Anyways, first work on allowing use to store the regexp rules. That will
be soooo damn cool and worth every penny.

Seek3r

"Patrick J. Walsh" wrote:
> 
>     My feeling is that you should do this in two stages.  First create an
> advanced filtering capability similar to that done by maildrop
> (http://www.flounder.net/~mrsam/maildrop/maildropfilter.html).  This
> essentially allows the user to use any regexp expression on any of the
> headers and optionally on the content as well.  There are basic commands for
> if statements here as well.  Then there is a set of actions that allow you
> to specify where to move the message, copy the message, who to forward it
> to, etc.  Maildrop allows the use of databases to track mail, log files, and
> unlimited piping to external commands.  I don't think any of this is
> appropriate in phpgw unless the piping is to another phpgw app.
> 
>     The second step would be to create a dummy interface similar to the
> Outlook filters where natural language options would mask the creation of
> filters.  For example:
> 
> Dummy filter says:
> 
> Apply this rule _after_ the message arrives
> Where _somebody_ is in the To or Cc box
> Forward a copy to address@hidden and
> Move it to _Special Folder_
> 
> Advanced regexp says:
> 
> If (/^(To|Cc): .*somebody/)
>   {
>      cc address@hidden
>      to SpecialFolder
>   }
> 
>     You will need to write something to handle nested if/else statements,
> but otherwise it should be fairly easy.  I wouldn't write a language that
> parses statements like:
> 
> if "to" contains "somebody" then blah blah
> 
> ..Patrick (mr_e)
> 
> _______________________________________________
> Phpgroupware-developers mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/phpgroupware-developers