Dev March 2016

dev@lists.roundcube.net

10 participants
8 discussions

Enigma S/MIME support
by Kyle Francis 23 Aug '16

23 Aug '16

Alec, Thanks for helping me get up and running with the enigma plugin and for pointing me to the previously existing work on an SMIME plugin. For those of you who don't know and are interested, I'm a Master's Candidate and I'm implementing S/MIME in the enigma plugin for an independent study this semester. So far I have implemented the following features: - Import PKCS#12 certificate store (password protected) - Pub cert, priv key, any additional certs contained in the store treated as CA certs. - create a hashed directory of CA certs - Verify S/MIME signatures (pkcs7-signatures .p7s) - Decrypt S/MIME encrypted emails - Decrypt and verify signed then encrypted emails Features that are not yet complete: - Encrypt only outgoing - Add menu option to Compose Window - Sign only outgoing (clear signing) - Add menu option to Compose window - Encrypt then Sign - Sign then Encrypt - List certs/details from settings view - Verify pkcs7-mime (.p7m) signed emails - Generate CSR - Handle CRL's (.p7c) Modifications are available at github.com/guitarmanusa/roundcubemail in a branch called enigma-smime-dev. -- Kyle Francis M.S.IT Candidate Rensselaer Polytechnic Institute Email - franck6(a)rpi.edu kyle(a)linuxtoolbox.ninja

3 8

rc next: ember broccoli error
by Brendan 01 May '16

01 May '16

has anyone encountered this error before? just trying to get things set up for the first time, everything was installed from scratch and latest versions. brendan@xps:~/rcube/roundcube-shell$ export JMAP_HOST=http://127.0.0.1:8080 && STYLEGUIDE=true && ember server version: 1.13.12 BroccoliMergeTrees: Expected Broccoli node, got undefined for inputNodes[0] TypeError: BroccoliMergeTrees: Expected Broccoli node, got undefined for inputNodes[0] at BroccoliMergeTrees.Plugin (/home/brendan/rcube/roundcube-shell/node_modules/broccoli-plugin/index.js:23:13) at new BroccoliMergeTrees (/home/brendan/rcube/roundcube-shell/node_modules/broccoli-merge-trees/index.js:29:10) at BroccoliMergeTrees (/home/brendan/rcube/roundcube-shell/node_modules/broccoli-merge-trees/index.js:23:53) at Class.module.exports.treeForVendor (/home/brendan/rcube/roundcube-shell/node_modules/roundcube-mail/index.js:28:12) at Class._treeFor (/home/brendan/rcube/roundcube-shell/node_modules/ember-cli/lib/models/addon.js:319:31) at Class.treeFor (/home/brendan/rcube/roundcube-shell/node_modules/ember-cli/lib/models/addon.js:289:19) at /home/brendan/rcube/roundcube-shell/node_modules/ember-cli/lib/broccoli/ember-app.js:369:20 at Array.map (native) at EmberApp.addonTreesFor (/home/brendan/rcube/roundcube-shell/node_modules/ember-cli/lib/broccoli/ember-app.js:367:30) at EmberApp._processedVendorTree (/home/brendan/rcube/roundcube-shell/node_modules/ember-cli/lib/broccoli/ember-app.js:796:29)

2 1

Say goodbye to Trac
by Thomas Bruederli 01 Apr '16

01 Apr '16

Hello devs and list lurkers You all might have noticed the hickups we recently had with our Trac platform. Our Trac site was under heavy attack from spammers which put high load on the system and flooded the database with garbage. None of us really is a Trac expert and we failed at bringing the necessary measures in place to fight the spamming an to clean up the mess they caused. Adam, our volunteer admin who donated his private server for hosting the Trac site wants to resign from his duties which is fair and understandable. As a first action we deactivated user registration while we're looking for alternatives. That said, we're now looking at possible replacements for Trac or a successor for Adam who is willing to take the burden of hosting that crap. The most obvious - and already often requested - option is to migrate the tickets and the wiki pages into github. I already tested the import through the github API and that's a feasible option. But of course there are downsides: issue IDs cannot be kept and would be re-assigned. Also one cannot add tickets and comments with a date in the past. >From the 6.5K tickets we have in the database, there are ~ 200 open. I guess migrating these plus the resolved ones back to milestone 1.0.0 into github issues would give us a clean restart without loosing to much valuable data and - most importantly - without having to setup, host and protect our own tracker system. Anyway, please raise your voice with suggestions, concerns or offers if you have experience with such a post-Trac situation. Many thanks, Thomas

10 11

Can you please build a roundcube mail app for Android?
by Maureen Electa Monte 30 Mar '16

30 Mar '16

I had an app that wasn't by you that didn't work very well. I read that I'm supposed to use the browser and the user interface is impossible to navigate once I log in. Are there options you recommend for people like me who want to use my smart phone to access my email? Please advise, and thank you very much for your time. -- Maureen Electa Monte Success Architect | Building Winning Teams Ideation ~ Strategic ~ Learner ~ Achiever ~ Individualization ~ Maximizer c) 248.821.6821 Learn about Strengths-Based Success at www.maureenmonte.com

2 2

Trac platform migrated to Github
by Thomas Bruederli 20 Mar '16

20 Mar '16

Dear subscribers After many ups and downs with our Trac platform which hosted our wiki and the ticket system for years now, we finally migrated the data over to Github where we already host the git repositories. Therefore, on March 25th 2016 the trac.roundcube.net site will be shut down Starting today, the site is in read-only mode meaning that user logins and ticket reporting have been disabled already. This means that submitting new tickets now goes through Github and so does the roadmap planning and overview. The entry point for that is our Github project page at https://github.com/roundcube/roundcubemail Today we just migrated 4.8K tickets from the Trac database to Github issues [1], leaving the invalid and duplicate ones behind. Unfortunately the ticket numbers could not be kept and have all been re-assigned. The original trac ticket numbers are mentioned in the migrated issue body and can be used for searching. We'll also install a redirect service which will translate old Trac urls to the corresponding issue pages. The wiki will also be translated into Github markdown pages. There's some manual reviewing involved in order to update or remove outdated information during this process. Please give us some more days to complete that task. Thank you for your understanding and see you on Github Best, Thomas [1] https://github.com/roundcube/roundcubemail/issues

1 0

bug in CC-input-field 1.1.4
by Pascal Nobus 14 Mar '16

14 Mar '16

If you type this in the CC-input field: "Your Name (your(a)email.com)" <your(a)email.com> you will endup with a bounce. It seems roundcube is seeing the values between the " as an emailadress. Reprodruce this error: Typ in the CC-field: "Your Name (your(a)email1.com)" <your(a)email2.com> And you'll get an error about email1.com P.S. I tried to put this in the TRAC-system, but couldn't create a login. Best regards, Pascal Nobus -- www.webservice.be

2 1

RC 1.2 beta status
by fsantiago＠garbage-juice.com 13 Mar '16

13 Mar '16

Where do we stand with this beta?

2 1

Re: [RCD] [RCU] Error "Invalid request! No data was saved."
by Michael Heydekamp 10 Mar '16

10 Mar '16

Am 08.03.2016 15:05, schrieb Michael Heydekamp: > Am 24.09.2015 09:16, schrieb A.L.E.C: >> On 09/23/2015 10:53 PM, Michael Heydekamp wrote: >>> But I'm hoping that one of the devs will shed some light on it, as to when >>> this error will occur. I'm seeing it for a few weeks now. >> >> "Invalid request! No data was saved" indicates CSRF security token check >> fails. Something is wrong with session or something (proxy?) removes >> X-Roundcube-Request header (or less likely POST parameter). >> >> Test with disabled all plugins and use most recent stable version. > > I didn't have the time and opportunity to investigate this further, so the > problem did persist for approx. half a year now - and since a few days, all > of a sudden it is gone. > > As we didn't change anything at our end - did you do anything which could > have solved the issue...? > > I had the issue always when I logged in a second time but with a different > (sub-)domain. The first attempt of the second login failed with "Invalid > request!", the second attempt then worked. And now the problem is back again. :( What the heck can be the reason? Any hint appreciated. Now sent to the dev-list, as no response in the users-list. Cheers, -- Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Dev March 2016