I know that there was a thread started here about message filtering: http://lists.roundcube.net/mail-archive/roundcube.dev/2005/10/376/
Anyone know the status on this?
I'm liking RoundCube a lot! And if I decide to adopt it, I would want to forward all of my email addresses over to it, but I would want incoming emails to automatically go into certain folders, depending on the To Address, so that I don't have to go move each individual email into their folders.
Do we just need to wait for this feature? Any ideas on a time frame?
Keep up the good work. This is very nice!
I think Roundcube still has a way to go in some other more common areas of webmail functionality before anyone tackles filtering in a big way. But I would also question whether a webmail system is the right spot for mail filtering. This really should be done at the mail server level. That way the filtering occurs regardless of how you view your mail (eg. some days you might access it through Thunderbird, other days through Roundcube - you don't want to have to maintain two different sets of filters).
What is appropriate for a webmail client however is some sort of hook into that backend filtering system so that you have a nice way of configuring it within the webmail. An example that comes to mind is there is a plugin for squirrelmail that lets you manipulate sieve scripts on a cyrus backend. I am almost certain there would be a similar procmail one if you looked around.
So the best way would be to write the filtering interface as generically as possible, then write seperate backends for the various filtering systems around (procmail, sieve, etc).
But my main point is, in the meantime there is nothing stopping you from having filtering with your roundcube - it all depends on what mail system you use in the backend. You just have to configure it in there instead of having the convenience of doing it through roundcube.
Cheers Derek
On 4/6/06, anthony@rexburg.com anthony@rexburg.com wrote:
I know that there was a thread started here about message filtering: http://lists.roundcube.net/mail-archive/roundcube.dev/2005/10/376/
Anyone know the status on this?
I'm liking RoundCube a lot! And if I decide to adopt it, I would want to forward all of my email addresses over to it, but I would want incoming emails to automatically go into certain folders, depending on the To Address, so that I don't have to go move each individual email into their folders.
Do we just need to wait for this feature? Any ideas on a time frame?
Keep up the good work. This is very nice!
On Fri, 7 Apr 2006 08:35:06 +0800, "Derek Hinchliffe" iamplebian@gmail.com wrote:
I think Roundcube still has a way to go in some other more common areas of webmail functionality before anyone tackles filtering in a big way. But I would also question whether a webmail system is the right spot for mail filtering. This really should be done at the mail server level. That way the filtering occurs regardless of how you view your mail (eg. some days you might access it through Thunderbird, other days through Roundcube - you don't want to have to maintain two different sets of filters).
What is appropriate for a webmail client however is some sort of hook into that backend filtering system so that you have a nice way of configuring it within the webmail. An example that comes to mind is there is a plugin for squirrelmail that lets you manipulate sieve scripts on a cyrus backend. I am almost certain there would be a similar procmail one if you looked around.
So the best way would be to write the filtering interface as generically as possible, then write seperate backends for the various filtering systems around (procmail, sieve, etc).
But my main point is, in the meantime there is nothing stopping you from having filtering with your roundcube - it all depends on what mail system you use in the backend. You just have to configure it in there instead of having the convenience of doing it through roundcube.
Cheers Derek
Just my $0.02, but I would have to agree with Derek here. Adding filtering would, IMO, take RC from being a client to an LDA (local delivery agent) and could cause issues for those who already have this functionality handeled within procmail, etc. .
Focusing on being the most able webmail client and having some ability for plugins to be added to have this functionality would be much more preferable.
Server side filtering is not available to many, and most desktop clients have the capability. Should it be a focus in RoundCube's development at the moment? Probably not - but long term I think client side filtering is a logical feature for RoundCube.
-Trae Dorn
Josh King wrote:
On Fri, 7 Apr 2006 08:35:06 +0800, "Derek Hinchliffe" iamplebian@gmail.com wrote:
I think Roundcube still has a way to go in some other more common areas of webmail functionality before anyone tackles filtering in a big way. But I would also question whether a webmail system is the right spot for mail filtering. This really should be done at the mail server level. That way the filtering occurs regardless of how you view your mail (eg. some days you might access it through Thunderbird, other days through Roundcube - you don't want to have to maintain two different sets of filters).
What is appropriate for a webmail client however is some sort of hook into that backend filtering system so that you have a nice way of configuring it within the webmail. An example that comes to mind is there is a plugin for squirrelmail that lets you manipulate sieve scripts on a cyrus backend. I am almost certain there would be a similar procmail one if you looked around.
So the best way would be to write the filtering interface as generically as possible, then write seperate backends for the various filtering systems around (procmail, sieve, etc).
But my main point is, in the meantime there is nothing stopping you from having filtering with your roundcube - it all depends on what mail system you use in the backend. You just have to configure it in there instead of having the convenience of doing it through roundcube.
Cheers Derek
Just my $0.02, but I would have to agree with Derek here. Adding filtering would, IMO, take RC from being a client to an LDA (local delivery agent) and could cause issues for those who already have this functionality handeled within procmail, etc. .
Focusing on being the most able webmail client and having some ability for plugins to be added to have this functionality would be much more preferable.
On Fri, Apr 07, 2006 at 10:27:16AM -0500, Trae Dorn wrote:
Server side filtering is not available to many, and most desktop clients have the capability. Should it be a focus in RoundCube's development at the moment? Probably not - but long term I think client side filtering is a logical feature for RoundCube.
-Trae Dorn
Josh King wrote:
On Fri, 7 Apr 2006 08:35:06 +0800, "Derek Hinchliffe" iamplebian@gmail.com wrote:
I think Roundcube still has a way to go in some other more common areas of webmail functionality before anyone tackles filtering in a big way. But I would also question whether a webmail system is the right spot for mail filtering. This really should be done at the mail server level. That way the filtering occurs regardless of how you view your mail (eg. some days you might access it through Thunderbird, other days through Roundcube - you don't want to have to maintain two different sets of filters).
What is appropriate for a webmail client however is some sort of hook into that backend filtering system so that you have a nice way of configuring it within the webmail. An example that comes to mind is there is a plugin for squirrelmail that lets you manipulate sieve scripts on a cyrus backend. I am almost certain there would be a similar procmail one if you looked around.
So the best way would be to write the filtering interface as generically as possible, then write seperate backends for the various filtering systems around (procmail, sieve, etc).
But my main point is, in the meantime there is nothing stopping you from having filtering with your roundcube - it all depends on what mail system you use in the backend. You just have to configure it in there instead of having the convenience of doing it through roundcube.
Cheers Derek
Just my $0.02, but I would have to agree with Derek here. Adding filtering would, IMO, take RC from being a client to an LDA (local delivery agent) and could cause issues for those who already have this functionality handeled within procmail, etc. .
Focusing on being the most able webmail client and having some ability for plugins to be added to have this functionality would be much more preferable.
Looking this thread over, it seems that it may be best to do something along these lines:
Option 1: Build a plugin architecture Build a filtering interface on top of that Have different backend drivers for that filtering interface. Candidates would include procmail, sieve, maildrop, and roundcube-based filtering. The last would perhaps run when the user logs in or checks for new mail.
This is similar to how Horde handles filtering. A semi-separate application (ingo) handles filtering with a standard interface, and there are various backend drivers to choose from including filtering at by the webmail program itself.
Option 2: Build a plugin architecture Let people build filtering plugins for it.
This option is more like squirrelmail's handling. The avelsieve plugin driver I use with SM looks and feels much different than the procmail driver that is available. I think this option is simpler and probably more lightweight, but it is also less consistent.
Either option could allow one to write a filtering that is actually handled within RC, but could alternatively use whatever server-side filtering system is available to the user.
On Wednesday 05 April 2006 19:13, anthony@rexburg.com wrote:
I know that there was a thread started here about message filtering: http://lists.roundcube.net/mail-archive/roundcube.dev/2005/10/376/
Anyone know the status on this?
I'm liking RoundCube a lot! And if I decide to adopt it, I would want to forward all of my email addresses over to it, but I would want incoming emails to automatically go into certain folders, depending on the To Address, so that I don't have to go move each individual email into their folders.
Do we just need to wait for this feature? Any ideas on a time frame?
I've got this item on my To-Do list. As others have said the correct place to add filtering is server-side via. Sieve. That is what I'm planning on doing; Sieve and only Sieve. Right now it is just a To-Do item and no code has been written. Hopefully I'll have time sometime this summer to work on it. I'm working on getting the relevent pear packages up to snuff right now.
On Fri, Apr 07, 2006 at 04:34:49PM -0400, Anish Mistry wrote:
On Wednesday 05 April 2006 19:13, anthony@rexburg.com wrote:
I know that there was a thread started here about message filtering: http://lists.roundcube.net/mail-archive/roundcube.dev/2005/10/376/
Anyone know the status on this?
I'm liking RoundCube a lot! And if I decide to adopt it, I would want to forward all of my email addresses over to it, but I would want incoming emails to automatically go into certain folders, depending on the To Address, so that I don't have to go move each individual email into their folders.
Do we just need to wait for this feature? Any ideas on a time frame?
I've got this item on my To-Do list. As others have said the correct place to add filtering is server-side via. Sieve. That is what I'm planning on doing; Sieve and only Sieve. Right now it is just a To-Do item and no code has been written. Hopefully I'll have time sometime this summer to work on it. I'm working on getting the relevent pear packages up to snuff right now.
Hopefully the work you do on sieve (which I will be very, very grateful for) would be able to be fit into whatever plugin architecture that RC gets. Plugins are on the road map for roundcube, right?
I'm excited to see where things are heading.
Anish Mistry wrote:
On Wednesday 05 April 2006 19:13, anthony@rexburg.com wrote:
I know that there was a thread started here about message filtering: http://lists.roundcube.net/mail-archive/roundcube.dev/2005/10/376/
Anyone know the status on this?
I'm liking RoundCube a lot! And if I decide to adopt it, I would want to forward all of my email addresses over to it, but I would want incoming emails to automatically go into certain folders, depending on the To Address, so that I don't have to go move each individual email into their folders.
Do we just need to wait for this feature? Any ideas on a time frame?
I've got this item on my To-Do list. As others have said the correct place to add filtering is server-side via. Sieve. That is what I'm planning on doing; Sieve and only Sieve. Right now it is just a To-Do item and no code has been written. Hopefully I'll have time sometime this summer to work on it. I'm working on getting the relevent pear packages up to snuff right now.
How many imap servers support sieve? Making it sieve specific seems like a bad idea.
--Brian Jackson
On Sun, 23 Apr 2006 10:31:41 -0500, Brian Jackson iggy@theiggy.com wrote:
Anish Mistry wrote:
On Wednesday 05 April 2006 19:13, anthony@rexburg.com wrote:
I know that there was a thread started here about message filtering: http://lists.roundcube.net/mail-archive/roundcube.dev/2005/10/376/
Anyone know the status on this?
I'm liking RoundCube a lot! And if I decide to adopt it, I would want to forward all of my email addresses over to it, but I would want incoming emails to automatically go into certain folders, depending on the To Address, so that I don't have to go move each individual email into their folders.
Do we just need to wait for this feature? Any ideas on a time frame?
I've got this item on my To-Do list. As others have said the correct place to add filtering is server-side via. Sieve. That is what I'm planning on doing; Sieve and only Sieve. Right now it is just a To-Do item and no code has been written. Hopefully I'll have time sometime this summer to work on it. I'm working on getting the relevent pear packages up to snuff right now.
How many imap servers support sieve? Making it sieve specific seems like a bad idea.
Agreed, and again, don't take all Summer to reinvent the wheel when this has already been done before. Check out http://email.uoa.gr/projects/squirrelmail/avelsieve.php -- it's a SM plugin, with a web UI front end, take a look at the screenshots. So all the work is basically already done, you just have to 1) integrate it into RC 2) redo the layout/style 3) ??? 4) profit!
P
http://fak3r.com - you dont have to kick it
phil wrote:
On Sun, 23 Apr 2006 10:31:41 -0500, Brian Jackson iggy@theiggy.com wrote:
Anish Mistry wrote:
On Wednesday 05 April 2006 19:13, anthony@rexburg.com wrote:
I know that there was a thread started here about message filtering: http://lists.roundcube.net/mail-archive/roundcube.dev/2005/10/376/
Anyone know the status on this?
I'm liking RoundCube a lot! And if I decide to adopt it, I would want to forward all of my email addresses over to it, but I would want incoming emails to automatically go into certain folders, depending on the To Address, so that I don't have to go move each individual email into their folders.
Do we just need to wait for this feature? Any ideas on a time frame?
I've got this item on my To-Do list. As others have said the correct place to add filtering is server-side via. Sieve. That is what I'm planning on doing; Sieve and only Sieve. Right now it is just a To-Do item and no code has been written. Hopefully I'll have time sometime this summer to work on it. I'm working on getting the relevent pear packages up to snuff right now.
How many imap servers support sieve? Making it sieve specific seems like a bad idea.
By that logic, I could say: How many imap servers support procmail? Making it procmail specific seems like a bad idea.
We use Sun Java System Messaging Server, which uses sieve for mail filters. Sun's sieve GUI interface is lacking for our needs, so I wrote one. It would be nice if there was a more advanced interface that we could use.
IMO, sieve is the best option for server side filtering. From http://web.archive.org/web/20041126062029/http://www.cyrusoft.com/sieve/
"Sieve is a language that can be used to create filters for electronic mail. It is not tied to any particular operating system or mail architecture."
"The language is powerful enough to be useful, but limited in power in order to allow for a safe server-side filtering system. The intention is to make it impossible for users to do anything more complex (and dangerous) than write simple mail filters..."
"Because of the expectation that users will make use of filtering if it is offered and easy to use, this language has been made simple enough to allow many users to make use of it, but rich enough that it can be used productively. However, it is expected that GUI-based editors will be the preferred way of editing filters for most users."
"There are many filtering schemes in place at present, using widely variant underlying syntaxes and representing different levels of sophistication, functionality, and detail. Virtually no two different filtering schemes interoperate with one another, forcing users and system administrators alike to re-create filters for each individual piece of software."
Agreed, and again, don't take all Summer to reinvent the wheel when this has already been done before. Check out http://email.uoa.gr/projects/squirrelmail/avelsieve.php -- it's a SM plugin, with a web UI front end, take a look at the screenshots. So all the work is basically already done, you just have to 1) integrate it into RC 2) redo the layout/style 3) ??? 4) profit!
Avelsieve only works with Cyrus. Maybe steal avelsieve's editing interface and then modularize the way it stores the filters to allow for compatibility with other IMAP servers.
-
Anish Mistry -
anthony＠rexburg.com -
Brian Jackson -
Derek Hinchliffe -
Jesse Thompson -
Josh King -
phil -
Steve Block -
Trae Dorn