I have a Debian 11 web server where SquirrelMail was working perfectly, but it stopped working after I upgraded to Debian 12 Bookworm. I’ve seen tutorials on forums about installing Roundcube, but none of them have worked out. Given that SquirrelMail doesn't work on Debian 12 Bookworm, why isn't there a standard plan to replace it with Roundcube? Also, I noticed configuration files in `/usr/local/ispconfig/server/conf/nginx_apps.vhost.master`—what are they for? I also followed tutorials like https://www.howtoforge.com/perfect-server-debian-12-buster-apache-bind-dovecot-ispconfig-3-2/, but that one is for Apache; I tried adapting it for Nginx without success—I don't know where to place the Roundcube VirtualHost. I also tried the tutorial https://www.howtoforge.com/using-roundcube-webmail-with-ispconfig-3-on-debian-wheezy-nginx (Using RoundCube Webmail With ISPConfig 3 On Debian Wheezy/Nginx), which involved creating a remote user in ISPConfig, but unfortunately, I couldn't complete the process. Could you point me to a comprehensive tutorial that covers creating a remote user in ISPConfig and the subsequent steps? Thanks in advance—I've been struggling with this for days. I managed to install Roundcube using a real domain name, but I can't seem to integrate it with ISPConfig.
I do not have any other tutorials other than the ones you find here on Howtoforge. But the process of installing RoundCube has not changed; it just gets installed with apt, and you do not have to connect it to ISPConfig to use it; it will just start working as soon as you install it. Squirrelmail was also not conected with ISPConfig. RoundCube as well as Squirremial just connect to the system using SMTP and Imap like any other mail client. There is a third-party plugin for RoundCube that uses the remote API, but I've never used it on my systems and its not required to use RoundCube with ISPConfig. If you have trouble installing it, you might want to contact its author on GitHub.
Thanks, Till, for the reply; I posted this message earlier today. To keep things simple, let's say I'm going to follow this tutorial: https://www.howtoforge.com/using-roundcube-webmail-with-ispconfig-3-on-debian-wheezy-nginx So, I'm starting by creating a remote user named "myroundcube" with the corresponding password. I have enabled the associated services: Server functions Client functions Mail user functions Mail alias functions Mail spamfilter user functions Mail spamfilter policy functions Mail fetchmail functions Mail spamfilter whitelist functions Mail spamfilter blacklist functions Mail user filter functions So, what's next? It's worth noting that I have already installed Roundcube using the command: apt-get install roundcube roundcube-plugins roundcube-plugins-extra Thanks.
After creating the remote user, the instructions say this: Next go to your website in ISPConfig. On the Options tab, you will see the nginx Directives field: However, what I see doesn't match the image shown. Could you clarify this for me? Thanks
The field nginx directives still exists on the options tab of the website in ISPConfig when you run an nginx server, so nothing has been changed in this regard. The screenshot is just from an older version that uses a different theme, and a few more settings have been added over the years.
Btw. A more recent guide is this one: https://www.howtoforge.com/install-ispconfig-3-roundcube-plugins-on-debian-10/ but as it uses a different approach to install the software, better don't mix them. The guide you used is for Debian Wheezy, which is Debian 7.
So, if I understand correctly, I need to add a new site name—like `mondomaineperso5.com`—and then add the following code to the Nginx configuration? client_max_body_size 100M; location /roundcube { root /var/lib/; index index.php index.html index.htm; location ~ (.+\.php)$ { try_files $uri =404; include /etc/nginx/fastcgi_params; # To access SquirrelMail, the default user (like www-data on Debian/Ubuntu) must be used #fastcgi_pass 127.0.0.1:9000; fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; fastcgi_intercept_errors on; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_buffer_size 128k; fastcgi_buffers 256 4k; fastcgi_busy_buffers_size 256k; fastcgi_temp_file_write_size 256k; } location ~* /.svn/ { deny all; } location ~* /README|INSTALL|LICENSE|SQL|bin|CHANGELOG$ { deny all; } } location /webmail { rewrite ^ /roundcube last; } Sorry, it wasn't mentioned that a new site needed to be added for this. Thanks.
So, for every domain that needs to use Roundcube, do I just need to add this snippet of code to the Nginx configuration? Thanks.
No, this is optional. If you just want to have the same functionality as you had before with SquirrelMail, then no site is needed. Adding a site is just an additional and fully optional way to access webmail trough another domain, it is not required.
No. This is not needed to use RoundCube for an email domain. It's just an alternative way in case you want to have additional URL's to access it. This nginx snippet configures an alias URL to Roundcube. So beside using the regular access on port 8081 as you used it for squirrelmail, which is the default to access RoundCube too, you can configure an alias URL to also access RoundCube using this alias.