texxasrulez/account_details

Display additional information for the current user and much more.

4.1.0 2026-04-11 21:03 UTC

Requires

• php: >=7.1.0
• roundcube/plugin-installer: >=0.1.4

GPL-3.0

• Gene Hawkins

README

Adds tab in Setting for more user info.

• Identities
• email address
• storage space quota
• Operating System
• Web Browser
• Video Resolution
• Mailbox Stats
• Server URL, port and other useful info
• CalDAV URL;s
• CardDAV URL's
• and more

You can enable/disable certain things via the config.inc.php

Installation

php composer.phar require texxasrulez/account_details

Upload contents to '/roundcube_location/plugins/account_details/'.

Enable plugin via config.inc.php with

$config['plugins'] = array('account_details');

Make an hourly cronjob with your web credentials as follows for Roundcube Version Checking:

curl -sL https://api.github.com/repos/roundcube/roundcubemail/releases/latest | jq -r ".tag_name" | sort -n | tail -1 > /path_to_roundcube/plugins/account_details/rc_latest.txt`

Enjoy!

💰 Donations 💰

If you use this plugin and would like to show your appreciation by buying me a cup of coffee, I surely would appreciate it. A regular cup of Joe is sufficient, but a Starbucks Coffee would be better ...
Zelle (Zelle is integrated within many major banks Mobile Apps by default) - Just send to texxasrulez at yahoo dot com
No Zelle in your banks mobile app, no problem, just click Paypal and I can make a Starbucks run ...

I appreciate the interest in this plugin and hope all the best ...

Screenshot

With All Details enabled

Versioning

• account_details now keeps its canonical version in account_details::PLUGIN_VERSION inside account_details.php.
• account_details::info() exposes the plugin metadata array used for self-identification.
• Development builds should use a +dev suffix such as 5.0.0+dev.
• Release builds should use a clean tagged version such as 5.0.0.

For a release bump:

1. Update account_details::PLUGIN_VERSION in account_details.php or run sh scripts/bump-version.sh 5.0.0.
2. Update CHANGELOG.md.
3. Create the matching release tag after verification.