I did a PR on github, for those who want to test I pushed a rpm on my server http://mirror.de-labrusse.fr/NethDev/rainloop/
yum install http://mirror.de-labrusse.fr/NethDev/rainloop/rainloop-1.12.0-1.ns7.noarch.rpm
the user interface is at https:///yourIP_or_Domain/rainloop
the admin interface is at https://yourIP_or_Domain/rainloop?admin
what differences from your work
- apache settings are done by the spec file (rainloop.conf created)
- php post_max_size & upload_max_filesize are set to 25MB
- no actions to set the apache permissions (data folder is owned by apache)
- data folder is denied to all (accordingly the documentation)
- httpd is restarted on installation/uninstallation
- php-pdo installed by dependency (needed if contacts are stored in mysql)
- https is forced
- upgrade to 1.12.0
Really it is just one shot…much should be done but rainloop is not so easy to customize like we use to do, why ?
Because the admin interface applies immediately the changes you do to
/usr/share/rainloop/data/_data_/_default_/configs/application.ini and this file doesn’t exist before you use the admin interface.
This could complicate our template system, I have had the same issue with BackupPC and I needed to use sed to rewrite the configuration file.
I renamed this rpm to rainloop firstly because I want to separate the configuration for nethserver, from the binary that even you could use on a bare centos.
This webmail is fun, you can use it to replace the gmail webmail, or in the admin interface declare several domains that your users might use. Therefore you even do not need to install a full mail server.
At the first prompt, you must declare your mail server on the localhost or remote server, if you do not do this, only gmail authentication is allowed (use your gmail account)