Dev August 2006

dev@lists.roundcube.net

59 participants
66 discussions

Re: Filtering spam with SpamAssassin header
by Michel Moreira 17 Aug '06

17 Aug '06

Try allowing the roundcube users to set their spam level and actions, and roundcube 'll manage the messages through those rules, no admin panel access 'll be needed.. ;) 2006/8/16, Nipun Jain <jain.nipun(a)gmail.com>: > Well, what I am talking about is that I have set my install in such a way > that if the user receives any email marked as spam by spamassasin, then it > automatically goes into the spam folder and I have roundcube automatically > subscribe to this folder when a new user is created. As for users marking a > mail as spam, thats not possible as to configure spamassasin, you need to re > write subjects which can only be done through the admin panel. > > > On 8/17/06, Michel Moreira <drungrin(a)gmail.com> wrote: > > You, the admin, setup it... and the other users? how about them having > > an friendly interface for setting it that isnt dependant of the server > > software? > > > > 2006/8/16, Nipun Jain < jain.nipun(a)gmail.com>: > > > Well, not exactly. If you got some kinda control panel with your shared > > > hosting, I am pretty sure that you can set spam mail to show up in a > spam > > > folder. If you are using a cPanel based hosting, let me know, I ll > provide > > > you guidance to set it up the way you want. > > > > > > Regards, > > > Nipun Jain. > > > > > > > > > On 8/17/06, Michel Moreira <drungrin(a)gmail.com> wrote: > > > > I dont think that we can rely on the server side software, cause of > > > > shared hostings, dont having access to this stuff and a lot of hosting > > > > issues. > > > > > > > > 2006/8/16, Brennan Stehling < brennan(a)offwhite.net>: > > > > > Yes, it would be great to get the webmail client set up so that it > can > > > actually control the procmail and mailfilter behavior somehow. I > suppose > > > you would need some server-side software to handle that interaction. > > > > > > > > > > Are there any projects which do this? > > > > > > > > > > Brennan > > > > > > > > > > On Wed, 16 Aug 2006 15:07:07 -0400, Mehmet Tolga Avcioglu > > > <mehmet(a)activecom.net> wrote: > > > > > > > > > > > > In my opinion something like this should be setup in the delivery > > > agent > > > > > > (procmail, maildrop). This behavior should be consistent between > > > > > > clients. For example we have a web based configuration tool for > these > > > > > > types of settings which creates the appropriate .mailfilter files > and > > > > > > the MDA does the rest. The behavior is same even is the users logs > in > > > > > > through web client or thunderbird, etc. > > > > > > > > > > > > I would actually like to see the Settings section extended so > these > > > > > > types of server side configurations could be implemented (spam > rules, > > > > > > blacklist, whitelist, vacation, etc.) as additional > > > extensions/modules.?? > > > > > > > > > > > > -- > > > > > > Mehmet Tolga Avcioglu > > > > > > > > > > > > Brennan Stehling wrote: > > > > > >> I would like to adjust RoundCube to automatically place new mail > into > > > > > > the Junk folder if it has a spam ranking from SpamAssassin. > > > > > >> > > > > > >> On my server... > > > > > >> > > > > > >> http://pronto.offwhite.net/antispam.html > > > > > >> > > > > > >> ..I have SpamAssassin set up and it will place the X-Spam-Level > > > header > > > > > > with a set of stars indicating the spam level. I think RoundCube > > > could > > > > > > check the SpamLevel and provide a personal setting to allow the > user > > > to > > > > > > automatically drop spam into the Junk folder. > > > > > >> > > > > > >> Thoughts? > > > > > >> > > > > > >> -- > > > > > >> Brennan Stehling > > > > > >> Offwhite.net LLC > > > > > >> brennan(a)offwhite.net > > > > > >> > > > > > >> > > > > > >> > > > > > -- > > > > > Brennan Stehling > > > > > Offwhite.net LLC > > > > > brennan(a)offwhite.net > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >

1 0

Re: Filtering spam with SpamAssassin header
by Brennan Stehling 17 Aug '06

17 Aug '06

Can I even configure procmail to move potential spam into my IMAP Junk folder? I have not seen how that can be done. Brennan On Wed, 16 Aug 2006 21:03:50 +0200, Michael Bueker <m.bueker(a)berlin.de> wrote: > Brennan Stehling wrote: >> I would like to adjust RoundCube to automatically place new mail into > the Junk folder if it has a spam ranking from SpamAssassin. >> [...] >> Thoughts? > > IMHO, this is not Roundcube's task, but that of your MDA (procmail, > maildrop, whichever). > > ~Mik > > -- > A: Why don't they just launch an arial attack? > B: An _arial_ attack! For a moment I was worried it might be a > Times New Roman one! > C: As long as they don't fight a war on two fonts... > - seen on /. -- Brennan Stehling Offwhite.net LLC brennan(a)offwhite.net

3 3

Fix for Bug #1483930
by Michael Bueker 15 Aug '06

15 Aug '06

Hi, I've worked on Bug #1483930 and resolved it thus: There are now two additional labels named "previousmessage" and "nextmessage", which are used in message.html, as opposed to "previousmessages" and "nextmessages" in mail.html. I've included the label entries for en_GB, en_US, de_DE, de_CH and es in the patch. If that's an okay course of action for you, please commit the patch and close the ticket :) Cheers, mtu -- What seems to be the Officer, problem? - From South Park, "Bloody Mary" diff -uNr rc-294/program/localization/de_CH/labels.inc rc-294fix/program/localization/de_CH/labels.inc --- rc-294/program/localization/de_CH/labels.inc 2006-08-06 15:51:22.000000000 +0200 +++ rc-294fix/program/localization/de_CH/labels.inc 2006-08-06 17:15:07.000000000 +0200 @@ -99,7 +99,9 @@ $labels['deletemessage'] = 'In den Papierkorb verschieben'; $labels['printmessage'] = 'Diese Nachricht drucken'; $labels['previousmessages'] = 'Vorherige Nachrichten anzeigen'; -$labels['nextmessages'] = 'Weitere Nachrichten anzeigen'; +$labels['previousmessage'] = 'Vorherige Nachricht anzeigen'; +$labels['nextmessages'] = 'Folgende Nachrichten anzeigen'; +$labels['nextmessage'] = 'Folgende Nachricht anzeigen'; $labels['backtolist'] = 'Zurück zur Liste'; $labels['select'] = 'Auswählen'; diff -uNr rc-294/program/localization/de_DE/labels.inc rc-294fix/program/localization/de_DE/labels.inc --- rc-294/program/localization/de_DE/labels.inc 2006-08-06 15:51:20.000000000 +0200 +++ rc-294fix/program/localization/de_DE/labels.inc 2006-08-06 17:03:49.000000000 +0200 @@ -100,7 +100,9 @@ $labels['deletemessage'] = 'In den Papierkorb verschieben'; $labels['printmessage'] = 'Diese Nachricht drucken'; $labels['previousmessages'] = 'Vorherige Nachrichten anzeigen'; -$labels['nextmessages'] = 'Weitere Nachrichten anzeigen'; +$labels['previousmessage'] = 'Vorherige Nachricht anzeigen'; +$labels['nextmessages'] = 'Folgende Nachrichten anzeigen'; +$labels['nextmessage'] = 'Folgende Nachricht anzeigen'; $labels['backtolist'] = 'Zurück zur Liste'; $labels['select'] = 'Auswählen'; diff -uNr rc-294/program/localization/en_GB/labels.inc rc-294fix/program/localization/en_GB/labels.inc --- rc-294/program/localization/en_GB/labels.inc 2006-08-06 15:51:20.000000000 +0200 +++ rc-294fix/program/localization/en_GB/labels.inc 2006-08-06 16:56:16.000000000 +0200 @@ -99,7 +99,9 @@ $labels['deletemessage'] = 'Move message to trash'; $labels['printmessage'] = 'Print this message'; $labels['previousmessages'] = 'Show previous set of messages'; +$labels['previousmessage'] = 'Show previous message'; $labels['nextmessages'] = 'Show next set of messages'; +$labels['nextmessage'] = 'Show next message'; $labels['backtolist'] = 'Back to message list'; $labels['viewsource'] = 'Show source'; diff -uNr rc-294/program/localization/en_US/labels.inc rc-294fix/program/localization/en_US/labels.inc --- rc-294/program/localization/en_US/labels.inc 2006-08-06 17:09:45.000000000 +0200 +++ rc-294fix/program/localization/en_US/labels.inc 2006-08-06 16:58:43.000000000 +0200 @@ -98,7 +98,9 @@ $labels['deletemessage'] = 'Move message to trash'; $labels['printmessage'] = 'Print this message'; $labels['previousmessages'] = 'Show previous set of messages'; +$labels['previousmessage'] = 'Show previous message'; $labels['nextmessages'] = 'Show next set of messages'; +$labels['nextmessage'] = 'Show next message'; $labels['backtolist'] = 'Back to message list'; $labels['viewsource'] = 'Show source'; diff -uNr rc-294/program/localization/es/labels.inc rc-294fix/program/localization/es/labels.inc --- rc-294/program/localization/es/labels.inc 2006-08-06 15:51:22.000000000 +0200 +++ rc-294fix/program/localization/es/labels.inc 2006-08-06 17:05:28.000000000 +0200 @@ -103,7 +103,9 @@ $labels['deletemessage'] = 'Mover mensaje a la papelera'; $labels['printmessage'] = 'Imprimir este mensaje'; $labels['previousmessages'] = 'Mostrar mensajes anteriores'; +$labels['previousmessage'] = 'Mostrar mensaje anterior'; $labels['nextmessages'] = 'Mostrar mensajes siguientes'; +$labels['nextmessage'] = 'Mostrar mensaje siguiente'; $labels['backtolist'] = 'Volver a la lista de mensajes'; $labels['viewsource'] = 'Mostrar código'; diff -uNr rc-294/skins/default/templates/message.html rc-294fix/skins/default/templates/message.html --- rc-294/skins/default/templates/message.html 2006-08-06 15:51:29.000000000 +0200 +++ rc-294fix/skins/default/templates/message.html 2006-08-06 17:26:15.000000000 +0200 @@ -11,9 +11,9 @@ <roundcube:include file="/includes/header.html" /> <div id="messagecountbar"> -<roundcube:button command="previousmessage" imageSel="/images/buttons/previous_sel.png" imageAct="/images/buttons/previous_act.png" imagePas="/images/buttons/previous_pas.png" width="11" height="11" title="previousmessages" /> +<roundcube:button command="previousmessage" imageSel="/images/buttons/previous_sel.png" imageAct="/images/buttons/previous_act.png" imagePas="/images/buttons/previous_pas.png" width="11" height="11" title="previousmessage" />  <roundcube:object name="messageCountDisplay" />  -<roundcube:button command="nextmessage" imageSel="/images/buttons/next_sel.png" imageAct="/images/buttons/next_act.png" imagePas="/images/buttons/next_pas.png" width="11" height="11" title="nextmessages" /> +<roundcube:button command="nextmessage" imageSel="/images/buttons/next_sel.png" imageAct="/images/buttons/next_act.png" imagePas="/images/buttons/next_pas.png" width="11" height="11" title="nextmessage" /> </div> <div id="messagetoolbar">

1 1

Re: Sorting Support in IMAP
by Eric Stadtherr 15 Aug '06

15 Aug '06

2 2

Sorting Support in IMAP
by Kevin Landers 15 Aug '06

15 Aug '06

I am wondering what kind of look up or test RoundCube does in order to decide whether or not it will allow the user to use the sorting function at the top of the columns in your mail folders. I have had the problem with quotas in the past, where RoundCube's initial look for Quota support in IMAP failed, even though Quota support does exist. So I had to comment out the checks for the Quota support in order to force RC to just go ahead and use the Quota functions. I am wondering if RC is doing a similar lookup in reference to sorting. I have logged in using Brett's RC 0.1 Beta 2 demo install. I logged into a demo account provided by "SKaero" on the RC forums. When I use his demo email account, the sorting features are present in each column. However, I then logged out and logged back in using my own account on my own server and I do not receive any sorting options. Where should I look to resolve this issue? Anyone have any insights? Thanks in advance, Kevin L.

2 3

New Template Command
by Brett Patterson 14 Aug '06

14 Aug '06

Hi all. After a user on the forum (Flash) tried to easily add a variable into a template. He tried many things, and I devised a nice template way of doing it. You can see the steps to do so here: http://roundcubeforum.net/forum/index.php?topic=342.msg1887#msg1887 It works as expected in the following manner: <roundcube:variable name="variableName" /> As with PHP, variableName != VariableName != VARIABLENAME != vArIaBlEnAmE != . . . so the name is case sensitive. This allows users to add variables they want in to their skin easily. Not sure if you want to add this or not, but I thought I'd put it on the table as an option for the beta3 or rc1 release (whichever naming convention you want to go with). ~Brett

1 0

attachment problem
by George Wu 12 Aug '06

12 Aug '06

There is a bug with roundcube where attachments don't get correctly displayed. This happens when a user sends email with an attachment via Apple Mail client to a user using roundcube. Although the email is viewable there is no attachment. Forwarding and saving to drafts correctly displays an attachment as well as forwarding to anyone else. diff -uNr rev304/roundcubemail/program/steps/mail/func.inc rev304-fixed/program/steps/mail/func.inc --- rev304/roundcubemail/program/steps/mail/func.inc 2006-08-08 16:27:06.000000000 -0700 +++ /var/www/lolamail/program/steps/mail/func.inc 2006-08-09 10:53:10.000000000 -0700 @@ -426,7 +426,8 @@ $message_icon = $attrib['messageicon']; // set attachment icon - if ($attrib['attachmenticon'] && preg_match("/multipart\/m/i", $header->ctype)) +// if ($attrib['attachmenticon'] && preg_match("/multipart\/m/i", $header->ctype)) + if ($attrib['attachmenticon'] && preg_match("/multipart\//i", $header->ctype)) $attach_icon = $attrib['attachmenticon']; $out .= sprintf('<tr id="rcmrow%d" class="message%s%s %s">'."\n", @@ -875,7 +876,8 @@ } // message contains multiple parts - else if ($message_ctype_primary=='multipart' && is_array($structure->parts)) + // else if ($message_ctype_primary=='multipart' && is_array($structure->parts)) + if ($message_ctype_primary=='multipart' && is_array($structure->parts)) { foreach ($structure->parts as $mail_part) { I've commented out the lines in question that cause this bug and replaced them with lines that do show the attachment. Is there a reason why lines 813 and down aren't under line 878 (i.e. nested if)? Also I can send out an email via Apple Mail if anyone is interested. Basically Apple Mail uses multipart/alternative as default and an attachment is contained after it. - George

1 1

Encoding problem
by Jan Mikus 11 Aug '06

11 Aug '06

There is encoding problem in headers with central european characters. Recipient address "Jan Mikuš <mikus(a)itcomputers.cz>" after encoding return "=?UTF-8?Q?Jan=20Miku=C5=A1=20<mikus(a)itcomputers.cz>?=" (right is "=?UTF-8?Q?Jan=20Miku=C5=A1?= <mikus(a)itcomputers.cz>") and Postfix this header encode to "=?UTF-8?Q?Jan=20Miku=C5=A1=20 <mikus(a)itcomputers.cz>,\n ?=(a)arachne.itcomputers.cz".

3 2

Alert message when attaching a file to a mail
by Ian 11 Aug '06

11 Aug '06

Hello, Since I updated Roundcube with the second beta, a JS alert() with some obscure HTML code is shown every time I upload an attachment. The file is uploaded correctly, I think this message was just used for debugging purpose. It can be removed by removing the line 2189 of the file "program/js/app.js". (the one with "alert(content)") Ian

2 1

Re: Addressbook database (was Re: Ticket #1332930 (Feature Requests))
by Eric Stadtherr 11 Aug '06

11 Aug '06

Brett, I have to disagree - XML is not meant for persistent storage of application data. You sacrifice referential integrity and efficient query capability if you just store everything as long text documents. Sure, the code to parse and transform it is easy, but the runtime cost of parsing through a complicated XML document for a single value in a single context is significant. Picture the popup address completion list taking 3-5 seconds to fill itself out when you start typing a name into the "Recipient" field... As an aside, if we do ever end up wanting to represent contact information in XML, there's a schema out there already for it: http://www.jabber.org/jeps/jep-0054.html -Eric > Eric Stadtherr wrote: >> >> I would suggest a database schema such as the following (let me know >> if my HTML table doesn't come across correctly): >> >> <snip> >> >> This would make it easily mappable to vCard contents without being too >> locked into vCard specifics. The "Field" column keeps you from having >> "n" columns for "n" bits of information (and saves space if only a >> subset of the fields are provided for a contact). The labels would map >> reasonably well to vCard parameters, while maintaining semantic >> consistency with tools like Apple's Address Book. Primary Key could be >> a simple surrogate key assigned to each row, or a compound key >> consisting of (Contact ID, Field, Label). The compound key would be >> more intuitive, but may cause implementation problems if the database >> provider doesn't like NULL values in the PK. Indexes could be built on >> any combination of columns to optimize searching. >> >> What do you think? >> >> -Eric >> >> >> >> On Thu, 10 Aug 2006 20:07:52 +0200, Thomas Bruederli wrote: >> >> Eric Stadtherr wrote: >> > Should rev306 be backed out then? It goes against this concept. >> > >> Well, my explanations haven't been clear enough when I talked to >> Tobias... I'll take care of that, but it definitely goes against my > ideas. >> >> I don't see any reason to have lots of fields in the database if we >> choose a format that can be parsed fast and allows us interchange > the >> data with other formats for import/export/sync. If searching the >> contacts gets a problem I suggest to create a fulltext index with > all >> field values required for search. >> >> Please don't hesitate to post your opinions to the > addressbook/database >> design. >> >> Regards, >> Thomas >> > Upon that note, why not use XML... it's what it's meant for. Instead of > another table to hold contacts, or multiple rows per contact, just store > XML data in one field. Then you can have X number of attributes of any > vCard or whatever format. It's easily parsable in PHP and can be > exported in a number for formats. It may even be quicker ;) > > <?xml version="1.0" encoding="ISO-8859-1"?> > <contacts> > <contact> > <fullname>FN</fullname> > <email type="home">fname(a)site.domain</email> > <email type="work">full.name(a)company.com</email> > <tele type="fax">+1 011-555-1234</tele> > </contact> > <contact> > <fullname>FN2</fullname> > <email type="home">someone(a)somewhere.de</email> > <tele type="work">+1 234-555-6666</tele> > </contact> > </contacts> > > Something like that would work wouldn't it? Obviously all the values > would be wrapped inside of <![CDATA[ ]]> tags... > > ~Brett

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Dev August 2006