Hi Javier and Chris!!<br>Javier:<br>1.- Sorry, the translator script is a shell script written in PHP (to take the db info and rest). It&#39;s easy to make a UI (frontend) for this.<br>2.- What is RPC?<br>3.- That&#39;s a good idea to make them compatible, but structured filtering is not just ordered filtering. I mean: we should work on improving the old UI to be able to create what the new one can: reply, forward, delete, 
<span style="font-weight: bold;">copy</span>  and <span style="font-weight: bold;">if/else</span>. Copy and if/else are the most complicated features to develop on the text UI, because these have 2 possibilities after them.
<br><br>Chris:<br>1.- RoundCube have to know which is the end filtering system because probably not all of them have all the features (actual and future), so you (as mail admin) will need to block some of the features. For sure this is a config issue. 
<br>¿Are we able to make an admin entrance to enable RC administration via web? It would be great!!<br><br>2.- Every mail system has it&#39;s own and very different working method. You can have, for example, a DB based users auth or just a Linux users auth, IMAP on a server and RC on another one and LDAP auth on a third one, etc You can configure each of the filtering system nearly as you want, so it&#39;s difficult for RC to do all the work. What I mean is that mail configuration is nearly chaotic to improve all the possibilities. Due to this issue, we can think on an intermediate solution, which, for example, lets the admin to create the scripts that will be executed by RC automatically to save the filters on the right way.
<br><br><div><span class="gmail_quote">2008/1/10, J. Javier Maestro &lt;<a href="mailto:roundcube-devel@nosys.es">roundcube-devel@nosys.es</a>&gt;:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Jan Thu 10 2008 18:19, emi delg wrote:<br>&gt; Hi Javier!!<br>&gt; The simpler filters UI is testable at <a href="https://mail.cio.cat">https://mail.cio.cat</a> with same user<br>&gt; and passwd.<br><br>Cool, I&#39;ll have a look at it as soon as I have some free time.
<br><br>&gt; May be we can add both UIs and let the user/admin decide whether to use one<br>&gt; or the other.<br><br>I think the best model would be something like:<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Let the basic, text-based UI form be the default
<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- This should use the usual .inc functions in program/steps, broken<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;in (duh!) simple steps such as save_filter.inc,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;translate_filter.inc, etc.<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Finally, the graphic UI should construct the same textual info from
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;the text-UI but using the graphic UI, and then pass it to the same<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;step .inc files from the textual UI.<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- The .inc in steps/ should be doing the translation in PHP... doing<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;it in a bash script is OK, but I think integrating it into PHP
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;would be better). Then, they should send this maildrop, procmail,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;whatever filter to a central server through RPC, to incorporate it<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;in the user mail-flow, etc.<br><br><br>--<br>J. Javier Maestro&nbsp;&nbsp;&lt;
<a href="mailto:jjmaestro@nosys.es">jjmaestro@nosys.es</a>&gt;<br>Socio Consultor&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;Nosys AJjV S.L.<br></blockquote></div><br>