- Dev - Roundcube mailing lists

Update 1.4.2 released
by Thomas Bruederli 01 Jan '20

01 Jan '20

Dear subscribers We start the year 2020 with the second service release to update the brand new Roundcube Webmail version 1.4. It contains fixes and improvements reported since the release of version 1.4.0. See the full changelog in the release notes on the Github download page [1]. This release is considered stable and we recommend to update all productive installations of Roundcube with this version. Download it from https://roundcube.net/download. Please do backup your data before updating. Happy New Year everybody! Alec & Thomas [1] https://github.com/roundcube/roundcubemail/releases/tag/1.4.2

1 0

Update 1.4.1 released
by Thomas Bruederli 22 Nov '19

22 Nov '19

Dear subscribers Short time after the release of the stable version 1.4.0 of Roundcube Webmail we already publish the first service release. With the recent release we missed to mention a few breaking changes since the last stable version 1.3. We apologize for this and are now clarifying and correcting these: Breaking changes ---------------- (since 1.3.x) * new defaults for smtp_* config options: Upon many requests and in order to get closer to the default setup of most SMTP servers, we changed the defaults as follows: // SMTP port (default is 587) $config[‘smtp_port’] = 587; // SMTP username (if required). %u will use the current username for login $config[‘smtp_user’] = ‘%u’; // SMTP password (if required). %p will use the current user’s password for login $config[‘smtp_pass’] = ‘%p’; * changed default password_charset to UTF-8: Because of many complaints, we decided to choose a more sane default that covers most setups and configurations. * login page returning 401 Unauthorized status: The new behavior that Roundcube 1.4 returns a 401 status code if the client is not authenticated apparently was very unexpected and lead to monitoring problems. Despite not having mentioned that change in the release notes, we now partly reverted it so that 401 is only returned on login failures but not on the first request to Roundcube which by definition is unauthorized. Besides these three major concerns we heard from your much appreciated feedback, we fixed a number of nasty bugs that sneaked into the 1.4.0 release. See the full changelog in the release notes on the Github download page [1]. This release is considered stable and we recommend to update all productive installations of Roundcube with this version. Download it from roundcube.net [2]. Please do backup your data before updating. We'd also like to thank Phil for his steady efforts to keep our website up-to-date. Your work is much appreciated! Best, Thomas & Alec [1] https://github.com/roundcube/roundcubemail/releases/tag/1.4.1 [2] https://roundcube.net/download

1 0

Roundcube Webmail 1.4.0 - Elastic released
by Thomas Bruederli 09 Nov '19

09 Nov '19

Dear subscribers It's a big honor for me to announce the final release of the long awaited major version 1.4 of Roundcube webmail. After more than two years of hard work by Alec and other volunteer contributors, Roundcube finally gets the responsive skin with full mobile device support - the Elastic. In addition to the new UI we introduce these new features: * Email Resent (Bounce) feature * Improved [Mailvelope](https://www.mailvelope.com) integration * Support for Redis and Memcached cache * Support for SMTPUTF8 and GSSAPI Plus numerous improvements and bug fixes collected from your precious feedback as well as updates to recent versions of 3rd party libraries like jQuery and TinyMCE. See the full changelog in the release notes on the Github download page [1]. The new Elastic theme, which is the new default skin, is built with LESS and of course the sources are included. They allow a certain degree of customization by adjusting some colors and variables using the `_styles.less` and `_variables.less` files. Please consider customizing your Roundcube installation in order to make phishing [2] harder. You'll find guidance in the README.md file inside the skin folder. This release is considered stable and we encourage you to update your productive installations after carefully testing the upgrade scenario and preparing your users to the significant changes in their webmail UI. Download it from https://roundcube.net/download. With the release of Roundcube 1.4.0, the previous stable release branches 1.3.x and 1.2.x will change into LTS low maintenance mode which means they will only receive important security updates but no longer any regular improvement updates. The 1.1.x series is no longer supported and maintained. Kind regards, Thomas [1] https://github.com/roundcube/roundcubemail/releases/tag/1.4.0 [2] https://roundcube.net/news/2019/10/28/phishing-alert

1 0

Schema change practices in roundcube
by Atalay Karatay 20 Oct '19

20 Oct '19

Dear developers from roundcube, I'm a student at the University of Applied Sciences in Regensburg (Germany). Currently I'm working on my master's thesis, contributing to a research project in the field quantitative software engineering. By mining the software histories of popular open source projects, we want to get insight about current development practices and challenges. Our main focus here is to understand the co-evolution/change-coupling of software artifacts, especially in the case of database-related changes. Since there are hardly works or established tools considering the co-evolution of schema and the code accessing it, we are investigating this topic. As roundcube is one major project in the open-source-community and is also supporting several databases, I have some questions: We found out that schema related changes were often committed together - across all databases . So in your case, some schema-changes were done for mssql, mysql, oracle, postgres and sqlite simultaneously. 1) Could you describe the common process of introducing these schema changes or do you have a manual for that? 2) Is there any tool in use, which supports this process automatically or is it done manually? 3) How much time is consumed when introducing schema changes in your project? 4) Which problems occur when changing the schema? Hopefully you can spend some time to answer these questions, I would be very grateful. Best regards Atalay Karatay

1 0

preferences in users table
by soumitri＠iitk.ac.in 19 Sep '19

19 Sep '19

Hello All, Can some one give me some light on the preferences column and if i want to modify how should i do it. I tried following command, but failed(no error, but no result too). # ./moduserprefs.sh --user='xyz' plugin.hotkeys.mapping_list --delete --type=string # ./moduserprefs.sh --user='xyz' plugin.hotkeys.mapping_list --delete Although i guess a brief structure from the below layout from preference column, but not in exact. Any reference document for this. Thanks for this nice OSS and any help. ============================ preferences: a:18: {s:27:"plugin.hotkeys.mapping_list";a:92: {i:0;a:7: {s:7:"profile";s:10:"cor.bosman";s:7:"command";s:23:"plugin.hotkeys.activate";s:7:"context";s:3:"any";s:7:"comment";s:30:"activate hotkeys plugin dialog";s:6:"script";s:0:"";s:3:"key";s:7:"shift+/";s:6:"source";s:8:"external";} i:91;a:7: {s:7:"profile";s:16:"andrei.pozolotin";s:7:"command";s:16:"#compose-subject";s:7:"context";s:9:"mail_edit";s:7:"comment";s:23:"focus: select 'subject'";s:6:"script";s:23:"top.$(command).focus();";s:3:"key";s:5:"alt+3";s:6:"source";s:6:"custom";} } s:16:"message_sort_col"; s:4:"date"; s:18:"message_sort_order"; s:4:"DESC"; s:9:"lastlogin"; a:4:{s:4:"from";s:12:"172.27.17.45";s:4:"date";s:10:"1567942038";s:3:"geo";s:12:"IITK network";s:7:"timeout";i:10;} s:44:"plugin.contextmenu_folder.collect_predefined"; a:2:{s:10:"INBOX/Sort"; a:3:{s:4:"mbox";s:10:"INBOX/Sort";s:6:"action";s:7:"default";s:12:"created_msec";i:0;} s:9:"Sent/Sort";a:3:{s:4:"mbox";s:9:"Sent/Sort";s:6:"action";s:7:"default";s:12:"created_msec";i:0;}} s:41:"plugin.contextmenu_folder.collect_special"; a:5:{s:5:"INBOX";a:3:{s:4:"mbox";s:5:"INBOX";s:6:"action";s:7:"default";s:12:"created_msec";i:0;}s:12:"INBOX.Drafts";a:3:{s:4:"mbox";s:12:"INBOX.Drafts";s:6:"action";s:7:"default";s:12:"created_msec";i:0;}s:10:"INBOX.Sent";a:3:{s:4:"mbox";s:10:"INBOX.Sent";s:6:"action";s:7:"default";s:12:"created_msec";i:0;}s:10:"INBOX.Junk";a:3:{s:4:"mbox";s:10:"INBOX.Junk";s:6:"action";s:7:"default";s:12:"created_msec";i:0;}s:11:"INBOX.Trash";a:3:{s:4:"mbox";s:11:"INBOX.Trash";s:6:"action";s:7:"default";s:12:"created_msec";i:0;}} s:22:"plugin.hotkeys.profile";s:5:"linux"; s:15:"per_folder_sort";a:2:{s:5:"INBOX";s:9:"date_DESC";s:12:"INBOX.Drafts";s:9:"date_DESC";} s:11:"search_mods";a:4:{s:1:"*";a:2:{s:7:"subject";i:1;s:4:"from";i:1;}s:10:"INBOX.Sent";a:2:{s:7:"subject";i:1;s:2:"to";i:1;}s:12:"INBOX.Drafts";a:2:{s:7:"subject";i:1;s:2:"to";i:1;}s:5:"INBOX";a:2:{s:7:"subject";i:1;s:4:"from";i:1;}} s:9:"list_cols";a:10:{i:0;s:7:"threads";i:1; s:5:"chbox";i:2; s:7:"subject";i:3; s:4:"date";i:4; s:4:"size";i:5; s:6:"status";i:6; s:4:"flag";i:7; s:10:"attachment";i:8; s:4:"from";i:9;s:2:"to";} s:31:"plugin.hotkeys.reset_to_default";b:0; s:11:"client_hash"; s:32:"badfa0036e5cdedeffa0aa2b0f341011"; s:11:"drafts_mbox"; s:12:"INBOX.Drafts"; s:9:"junk_mbox"; s:10:"INBOX.Junk"; s:9:"sent_mbox"; s:10:"INBOX.Sent"; s:10:"trash_mbox"; s:11:"INBOX.Trash"; s:15:"namespace_fixed";b:1; s:7:"filters"; a:1: {i:0;a:4: {s:10:"whatfilter";s:7:"subject";s:12:"searchstring";s:6:"[SPAM]";s:10:"destfolder";s:10:"INBOX.Junk";s:8:"messages";s:3:"all";} } ===================== -- Sincerely, Soumitri Mishra

2 2

Error When trying to update from the last git to version 1.4 rc2
by Fabián Burbano Gutiérrez 18 Sep '19

18 Sep '19

Dear: When trying to update from the last git to version 1.4 rc2, I get this message: ERROR: Target installation already in version 1.4-git. I don't know if it's the expected behavior and an update is impossible in that scenario. Maybe I should install from scratch? Or maybe I should report an incident? Thank you -- Fabián Burbano Gutiérrez

2 2

Roundcube Webmail 1.4 Release Candidate 2
by Thomas Bruederli 16 Sep '19

16 Sep '19

Dear subscribers We just published the long awaited second release candidate for the next major version 1.4 of Roundcube webmail. Many fixes, improvements and final touches have gone into this since the first release candidate was published. Check the Changelog [1] for a complete list of changes. We waited for some promised contributions which unfortunately never arrived but we now feel confident to call the new Elastic skin complete and ready to be officially released. As we’re moving towards the final release, we strongly encourage everybody to customize the Elastic skin using the _styles.less and _variables.less files to blend into your corporate design. You’ll find guidance for customization in the README.md file inside the skin folder. Rolling out a new and significantly different user interface should be carefully planned and we recommend to prepare your users for the change. Therefore the Elastic theme is not set to be the default theme. Adjust your config in order to enable it by default or let your users switch themselves in the user settings. Please note that the Classic skin will no longer be maintained and completely removed in future releases. Within the 1.4 release series, the Classic skin remains part of the package but it will not receive new features that were added to the Larry or Elastic themes. This is still a preview release and we recommend to test it on a separate environment. And don’t forget to backup your data before installing it. Download it from https://roundcube.net/download and keep on submitting bugs and send us your feedback. Best, Alec & Thomas [1] https://github.com/roundcube/roundcubemail/releases/tag/1.4-rc2

1 0

Roundcube Webmail 1.3.10 released
by Thomas Bruederli 29 Aug '19

29 Aug '19

Dear subscribers We proudly announce the next service release to update the stable version 1.3. It contains fixes to several bugs backported from the master branch including minor security fixes around CSS and HTML cleanup. See the full changelog in the release notes on the Github download page [1]. This release is considered stable and we recommend to update all productive installations of Roundcube with this version. Download it from https://roundcube.net/download. Best, Alec & Thomas [1] https://github.com/roundcube/roundcubemail/releases/tag/1.3.10

1 0

plugins calendar
by Rudisbel Tomlinson 24 Jul '19

24 Jul '19

I need to run the calendar plugin. How can I do?

1 0

Configure Enigma plugin with ie11 shows no output in window
by David Mehler 21 Jul '19

21 Jul '19

Hello, I got enigma plugin going. I atempted via ie11 on win10 x64 to configure the enigma plugin. I went to settings, > preferences, > and atempted to access encryption. It showed a blank output window. I went in to chrome latest I believe did the same thing and got options I could configure. Is there a roundcube/ie11 issue with content display? A side note on chrome after setting the encryption and identity options I was able to generate and associate a gpg key with my account. Any info on the ie11 issue appreciated. Thanks. Dave.

1 0

How to create a new letter by url?
by Vladimir Gorpenko 18 Jul '19

18 Jul '19

Hi! I would like to be able to immediately enter the RoundCube in the mode of creating a new letter by url from another application. Some fields, such as "from", "to" and "body" of the created letter must be initially filled with the data transmitted in the request. Since the volume of this data can be significant, it is advisable to use the POST method. However, if only the GET method is available, I will find another way to pass the information. In other words, I want to be able to create a link such as https://rcmail.a.b/newletter?from=a@b.c&to=d@e.f&body=Hello! in another application; when clicking on it, the user would open a window for creating a new letter in RC with partially filled content. For this illustration, I use a more visual GET method, but of course POST is desirable. Is it possible to do this in principle without reworking the RC thorough and what means are there for it? I apologize for my English, I use Google translator. -- Best regards, Vladimir Gorpenko

2 8

Collected recipients and senders
by A.L.E.C 04 Jun '19

04 Jun '19

In Roundcube we automatically collect email addresses. Some plugins exist that do this. I think it would be good to finally move the functionality into core and fix some related issues. As collecting senders and recipients is related let's consider this together. 1. Collected recipients. Recipient email addresses (and names) collected (automatically) when sending an email. We'll make it optional, i.e. when disabled we'll not collect addresses nor display the addressbook. I guess we'll have to have an option to use existing addressbook instead of the special one. So, it would be a single option: "Automatically add outgoing email addresses to": none/collected recipients/list of writable addressbooks for selection. I'm not sure we should consider checking an address existence in all writable or all other addressbooks, but I would like to not add an option for this. Let's check only the above configured addressbook + all writable addressbooks. Maybe provide a plugin api hook to modify the list (e.g. Kolab may choose to check all user personal addressbooks). 2. Collected senders. Email addresses of senders collected when using "Always allow from..." link/button. This addressbook will be displayed/used only when "Allow remote resources from known senders" is set. I guess we'll have to have an option to use existing addressbook instead of the special one. So, it would be a single option: "Store safe senders in": collected senders/list of writable addressbooks for selection. So, when we check if the html message is safe we look for an address in the configured addressbook. I'm not sure we should consider only the special addressbook, all writable addressbooks or all existing, but I would like to not add an option for this. Let's check the configuread addressbook + all writable addressbooks. And provide a plugin api hook to modify the list. I'm not sure about the name, maybe it should be "Safe senders"? I'm also not sure about the wording for these new options above. 3. "My contacts". We have an option "On request for return receipt send receipt to my contacts...". I think both above addressbooks should be considered as "my contacts" in this context. I don't like to add another option. The list could be modified by a plugin if needed. 4. Autocompletion. I think both above addressbooks should be used for autocompletion. I'm not sure it have to be configurable via 'autocomplete_addressbooks' option. Of course, these entries should have lower prio than entries from other addressbooks. ---------------- Both these addressbooks will use the same new database table. The table will contain columns: id, user_id, source_id, email, name. I think we should allow only a single email address per record. For both sources we'll allow only entries deletion. No editing. No groups. References: https://github.com/roundcube/roundcubemail/issues/5124 https://github.com/roundcube/roundcubemail/issues/5046 https://github.com/roundcube/roundcubemail/issues/4971 -- Aleksander 'A.L.E.C' Machniak Kolab Groupware Developer [http://kolab.org] Roundcube Webmail Developer [http://roundcube.net] ---------------------------------------------------- PGP: 19359DC1 # Blog: https://kolabian.wordpress.com

1 0

elastic bug on flagging
by Brendan 01 May '19

01 May '19

is there any preferred procedure for submitting bugs for elastic? do they just get submitted to the github issues section, or is a different process desired? we've found a minor bug in elastic (unsure if it also happens in larry); when a message is being displayed in env.contentframe, flagging a different message causes the message being displayed to show the flagged icon. it should only change change the flag in env.contentframe if the message being flagged/unflagged matches it. the problem seems to like in program/js/app.js; this.toggle_flagged_status() doesn't consider if the currently displayed uid is included in the list of uids it is changing - it just does it no matter what. a fix, though perhaps not the best way to do it (perhaps the parent window should remember which uid it's opened so it doesn't need to read it from the child iFrame?): --- src/1.4.1.rc1/program/js/app.js 2019-04-29 18:55:49.000000000 +0000 +++ deltas/1.4.1.rc1/program/js/app.js 2019-04-29 19:55:34.000000000 +0000 @@ -3402,7 +3402,10 @@ for (i=0; i<len; i++) this.set_message(a_uids[i], 'flagged', (flag == 'flagged' ? true : false)); - $(win.document.body)[flag == 'flagged' ? 'addClass' : 'removeClass']('status-flagged'); + if (a_uids.includes(win.frameElement.contentWindow.rcmail.env.uid * 1)) { + // only update flag on currently displayed message if it's part of the uidlist being updated + $(win.document.body)[flag == 'flagged' ? 'addClass' : 'removeClass']('status-flagged'); + } this.http_post('mark', post_data, lock); }; (also, this fix is untested against larry and classic) sorry for html email, didn't like the line wrapping a plain text email was causing on the diff.

2 1

Re: [RCD] dev Digest, Vol 136, Issue 3
by Rudisbel Tomlinson 18 Apr '19

18 Apr '19

Greetings colleagues, the reason why I write is that I have installed iredmail in a container of proxmox with debian 9 and since a few days I do not leave the mails or locals among users, check the log and tell me something that the amavis is having problems, which is why he rejects the request of the users. This happens to me when the electricity goes out suddenly. What can this be? Thank you. 2019-04-18 5:00 GMT-05:00, dev-request(a)lists.roundcube.net <dev-request(a)lists.roundcube.net>: > Send dev mailing list submissions to > dev(a)lists.roundcube.net > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.roundcube.net/mailman/listinfo/dev > or, via email, send a message with subject or body 'help' to > dev-request(a)lists.roundcube.net > > You can reach the person managing the list at > dev-owner(a)lists.roundcube.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of dev digest..." > > > Today's Topics: > > 1. (sin asunto) (Rudisbel Tomlinson) > 2. Re: (sin asunto) (A.L.E.C) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 17 Apr 2019 17:19:57 -0500 > From: Rudisbel Tomlinson <rudisbeltomlinson(a)gmail.com> > To: dev(a)lists.roundcube.net > Subject: [RCD] (sin asunto) > Message-ID: > <CACbQb-N3NLeObcOYX7Jxyc1+to06OqzP0Gq=pBNV9r26EY964A(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Saludos a los colegas, tengo un problema con el roundcube que he > instalado hace un tiempo, pues resulta que no envia los correos > internos, me fijo en los repositorios de los logos y me dice que > amavis esta teniendo problemas con el postfix. ?C?mo puedo solucionar > esto? , me ha sucedido en varias ocaciones Esto es un ejemplo: > > root@domain > > 4E5B7418ED 574 Tue Apr 16 11:55:44 postmaster@domain > (connect to 127.0.0.1[127.0.0.1]:10026: Connection > refused) > > > Gracias. > > > ------------------------------ > > Message: 2 > Date: Thu, 18 Apr 2019 08:22:36 +0200 > From: "A.L.E.C" <alec(a)alec.pl> > To: dev(a)lists.roundcube.net > Subject: Re: [RCD] (sin asunto) > Message-ID: <5e99bb1b-bb3b-d258-47ca-de065b62ecde(a)alec.pl> > Content-Type: text/plain; charset=utf-8 > > On 4/18/19 12:19 AM, Rudisbel Tomlinson wrote: >> Saludos a los colegas, tengo un problema con el roundcube que he >> instalado hace un tiempo, pues resulta que no envia los correos >> internos, me fijo en los repositorios de los logos y me dice que >> amavis esta teniendo problemas con el postfix. ?C?mo puedo solucionar >> esto? , me ha sucedido en varias ocaciones Esto es un ejemplo: >> >> root@domain >> >> 4E5B7418ED 574 Tue Apr 16 11:55:44 postmaster@domain >> (connect to 127.0.0.1[127.0.0.1]:10026: Connection >> refused) > > Please, don't spam the list. This is English speaking list. You have problem > with postfix > not Roundcube, find a better place for this matter. This has nothing to do > with Roundcube > development. > > -- > Aleksander 'A.L.E.C' Machniak > Kolab Groupware Developer [http://kolab.org] > Roundcube Webmail Developer [http://roundcube.net] > ---------------------------------------------------- > PGP: 19359DC1 # Blog: https://kolabian.wordpress.com > > > ------------------------------ > > _______________________________________________ > List info: http://lists.roundcube.net/dev/ > > > End of dev Digest, Vol 136, Issue 3 > *********************************** >

2 1

(sin asunto)
by Rudisbel Tomlinson 18 Apr '19

18 Apr '19

Saludos a los colegas, tengo un problema con el roundcube que he instalado hace un tiempo, pues resulta que no envia los correos internos, me fijo en los repositorios de los logos y me dice que amavis esta teniendo problemas con el postfix. ?C?mo puedo solucionar esto? , me ha sucedido en varias ocaciones Esto es un ejemplo: root@domain 4E5B7418ED 574 Tue Apr 16 11:55:44 postmaster@domain (connect to 127.0.0.1[127.0.0.1]:10026: Connection refused) Gracias.

2 1

Roundcube
by Rudisbel Tomlinson 16 Apr '19

16 Apr '19

Saludos a los colegas, tengo un problema con el roundcube que he instalado hace un tiempo, pues resulta que no envia los correos internos, me fijo en los repositorios de los logos y me dice que amavis esta teniendo problemas con el postfix. ¿Cómo puedo solucionar esto? , me ha sucedido en varias ocaciones Esto es un ejemplo: root@domain 4E5B7418ED 574 Tue Apr 16 11:55:44 postmaster@domain (connect to 127.0.0.1[127.0.0.1]:10026: Connection refused) Gracias.

1 0

Roundcube Webmail 1.3.9 released
by A.L.E.C 31 Mar '19

31 Mar '19

Dear subscribers We proudly announce the next service release to update the stable version 1.3. It contains fixes to several bugs backported from the master branch. See the full changelog in the release notes on the Github download page [1]. This release is considered stable and we recommend to update all productive installations of Roundcube with this version. Best, Alec & Thomas [1] https://github.com/roundcube/roundcubemail/releases/tag/1.3.9

1 0

Roundcube Webmail 1.4 RC1 released
by Thomas Bruederli 28 Feb '19

28 Feb '19

Dear subscribers We just published a first release candidate for the next major version 1.4 which has now been in development for quite a while. Although the new responsive Elastic skin is now functional and feature complete, it still lacks the final brush-up to make it shine. We have now finally found a volunteer to work on this and once completed, a second release candidate will follow. For now you’re all invited to give the new 1.4 version another test run. Besides the responsive theme it comes with lots of new features and improvements since the beta release. Check the Changelog [1] for a complete list of changes. Please also try customizing the Elastic skin using the _styles.less and _variables.less files and let us know what’s missing. You’ll find guidance in the README.md file inside the skin folder. Because we don’t yet consider the Elastic theme fully complete, it’s not set to be the default theme. Adjust your config in order to enable it with $config['skin'] = 'elastic'; This is a beta release and we recommend to test it on a separate environment. And don’t forget to backup your data before installing it. Download it from https://roundcube.net. Cheers, Thomas & Alec [1] https://github.com/roundcube/roundcubemail/releases/tag/1.4-rc1

1 0

Contribution to Roundcube
by egoitz＠sarenet.es 19 Feb '19

19 Feb '19

Good afternoon, We have adapted and make some modifications to Kolab calendar's plugin, in order to work with recent versions of Roundcube (1.3.X). Our plugin too, supports scheduling properly as we adapted that code from Kolab's plugin. Would you be interested in it?. At my company Sarenet, have given me permission for donating it to Roundcube. Would you like to have it?. Where could I send?. Cheers!

2 1

Roundcube Webmail 1.3.8 released
by Thomas Bruederli 26 Oct '18

26 Oct '18

Dear subscribers We proudly announce the next service release to update the stable version 1.3. It contains fixes to several bugs backported from the master branch including a security fix for a reported XSS vulnerability plus updates to ensure compatibility with PHP 7.3 and recent versions of Courier-IMAP, Dovecot and MySQL 8. See the full changelog in the release notes on the Github download page [1]. This release is considered stable and we recommend to update all productive installations of Roundcube with this version. Download it from https://roundcube.net. Best, Alec & Thomas [1] https://github.com/roundcube/roundcubemail/releases/tag/1.3.8

1 0

Roundcube should include CalDAV / CardDav client in its core functionality
by André Rodier 10 Oct '18

10 Oct '18

Hello all, I know there are many calendar and contact plugins for Roundcube, some of them offering CalDAV and CardDAV client or server functionalities. However, they not stable, not integrate well with mail functionalities or with the interface. Lets say presenting options to accept or refuse an invitation sent by email. I don't even mention support for the advanced features that some CalDAV and CardDAV servers are providing, for instance the excellent Davical. Moreover, some of them are coming with their own CalDAV or CardDav server, which I think is non-sense. Roundcube is a webmail client. It does do only one thing, but does it well. It does not come with a mail server feature... Is there any planning to add a nice and well integrated calendar feature on Roundcube? What about adding a CardDAV client for the address book as well. Using the LDAP address book in Roundcube is already great, it would be nice to have CardDAV integrated as well. Thanks to consider this! I have plenty of users who are concerned with Google Mail lack of privacy, and don't even like its web interface. Kind regards, André -- https://github.com/progmaticltd/homebox

3 5

plugin development for elastic
by cor＠xs4all.nl 15 Sep '18

15 Sep '18

Hi, i maintain some public plugins and have a question about elastic skin. One of my plugins has a custom preferences page and it looks like I have to use different markup for elastic vs larry/classic. What is the recommended way to handle different markup based on the skin when using the plugin preferences hooks? Cor

1 1

Folder List Refresh
by Tim Evers 10 Sep '18

10 Sep '18

Hi List, I recently came across an issue with the way RC handles the folder (mailbox) list. It only draws it when the page itself is loaded. And while the list gets updated for changed number of unread mails / trash stuff, it never gets reloaded as a whole inbetween. I would consider this an issue in case two clients (even two RCs) operate on the same mailbox, which is quite common for our users. In this case new folders created in another client do not show up in RC until the whole page is reloaded by selecting a task that reloads the UI. Right now it's even necessary to invalidate the cache if active. (But that should be an easy fix.) I would like to see the folder list being refreshed whenever the list of mails itself is refreshed. Since getting the folder list from the server is not expensive and as far as I could see trivially patched into the refresh handling in RC, it comes down to changing the mailbox list display from HTML fragment to JSON/Javascript command. As far as I saw nobody is or was working on this, so I would like to do it myself. But bevor I start working on it I would appreciate any input on this idea. Thanks Tim

1 0

managesieve and 'editheader' extension
by Michael Heydekamp 31 Aug '18

31 Aug '18

Hi, I did ask that in the RCU list already, but as there was no response, I try it here again: We just moved all domains and mail accounts to another hoster, and I managed to convince the new hoster to install the 'editheader' sieve extension (RFC 5293), as we definitely need it. It's not a problem to amend the 'addheader' commands manually to the filter set (as the managesieve plugin for RC doesn't offer any options for it yet). But it is a sort of problem that all 'addheader' commands are being removed if any rule is changed and saved through the frontend of the plugin (except if editing the filter set manually, of course). Is there any way to avoid this...? And/or are there any plans to implement the commands of the 'editheader' extension? I did have a look into the code already, but I have no real clue of PHP. Would it be sufficient to just amend 'addheader' to this array in rcube_sieve_script.php (just to avoid that it is being removed upon saving a rule through the frontend, not to really support it in the UI): > private $supported = array( // supported Sieve extensions: > 'body', // RFC5173 > 'copy', // RFC3894 > [... etc. ...] Furthermore, we'd like to use 'address :is' and 'address :matches' with non-standard headers such as "X-Envelope-To" and "X-Sieve-Redirected-From". Currently this doesn't work because the filter set can't even be saved (it throws an error). Is this a server-side limitation or a limitation of the plugin? If the latter, would it help to add those headers to this array in rcube_sieve_engine.php: > protected $addr_headers = array( > // Required > "from", "to", "cc", "bcc", "sender", "resent-from", "resent-to", > // Additional (RFC 822 / RFC 2822) > "reply-to", "resent-reply-to", "resent-sender", "resent-cc", "resent-bcc", > // Non-standard (RFC 2076, draft-palme-mailext-headers-08.txt) > "for-approval", "for-handling", "for-comment", "apparently-to", "errors-to", > "delivered-to", "return-receipt-to", "x-admin", "read-receipt-to", > [...] We can of course just give it a try, but I thought it would make sense to ask before we might be following a completely wrong path. Any helpful response will be appreciated. Cheers, -- Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany

2 1

Roundcube Webmail 1.4 beta released
by Thomas Bruederli 28 Aug '18

28 Aug '18

Dear subscribers We proudly announce the beta release of the next major version 1.4 of Roundcube webmail. With this milestone we introduce some new features: * New responsive skin with mobile support * Email Resent (Bounce) feature * Improved Mailvelope integration * Support for Redis cache * Support for SMTPUTF8 See the full changelog in the release notes on the Github download page [1]. Thanks to the tremendous effort Alec has put into the new skin, we finally managed solve the most urgent issue and make Roundcube accessible to the growing number of mobile and tablet devices. We'd also like to thank Kolab Systems for sponsoring some of Alec's working hours to the project. Because the new responsive skin is not yet fully completed, it’s not enabled by default. In order to make it the default for your users, change your config.inc.php accordingly: $config['skin'] = 'elastic'; As an alternative, the plugin elastic4mobile [2] makes it the default for mobile devices while keeping the configured default for desktop browsers. The Elastic skin is built with LESS and of course the sources are included. They allow a certain degree of customization by adjusting some color variables [3]. All you need is to compile your very own customized skin with lessc. This is a beta release and we recommend to test it on a separate environment. And don’t forget to backup your data before installing it. Download it from https://roundcube.net/download/#beta Please report bugs to our Github issue tracker [4] and check for duplicates before hitting the submit button. == New Logo and Website Design == As you may have noticed, the appearance of the Roundcube website has changed a while ago and it's also responsive now ;-) Many thanks to Phil Weir for re-coding the entire website and submitting a proper pull request! The new Elastic skin also brings a reshaped logo which has now been added to our website. The new logo was kindly designed and contributed by DRU Design [5]. Kudos! Kind regards, Thomas [1] https://github.com/roundcube/roundcubemail/releases/tag/1.4-beta [2] https://plugins.roundcube.net/packages/roundcube/elastic4mobile [3] https://github.com/roundcube/roundcubemail/blob/master/skins/elastic/styles… [4] https://github.com/roundcube/roundcubemail/issues [5] https://github.com/drudesign

7 8

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Dev