@loudlemur Here are some of the possible trouble indicators in the logs (I have obfusticated the domain names/email addresses)
One clue might be that though I am actually able to send mail, none of it appears in the "Sent" folder.
Also, if I go into "Manage folders", i can't create a folder or even click on those toggle buttons on the "inbox" for example. They don't respond.
Dec 17 17:09:50 (node:90) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
Dec 17 17:09:50 (Use `node --trace-deprecation ...` to show where the warning was created)
Dec 17 17:09:50 [INFO] [outbound] secured verified=false cipher=TLS_AES_256_GCM_SHA384 version=TLSv1.3 error=ERR_TLS_CERT_ALTNAME_INVALID cn=*.mydomain.com organization=""
[core] hook=connect plugin=dnsbl function=connect_multi params="" retval=DENY msg="host [123.456.789.012] is blacklisted by zen.spamhaus.org"
I just tried installing the carddav plugin (I think perhaps that should actually come pre-packaged in the app), but so far I can't get it to work.
Does the Roundcube app need to be restarted or anything? (not that that has helped me, just be good to know).
I note that the docs say:
Add the plugin to $config['plugins'] in /app/data/customconfig.php. The name below must match the name of the directory in the first step.
But in the actual customconfig.php file in the app it doesn't have $config it has $rcmail_config - so either the file in the app or the docs need updating to reflect whichever is actually correct.
Also, I think I'm correct in saying that you don't need to add another array_push... line, just to add 'myplugin' to the existing array, right?
So perhaps the docs should say:
Add the plugin to $rcmail_config['plugins'] in /app/data/customconfig.php. The name below must match the name of the directory in the first step.
To make that clearer?
Also, just so I know, does whitespace/ spaces make any difference in this file?
Some part of this like rate limits and notifications of hitting rate limits (for API, LDAP etc) are part of our focus in 6.3. We want to review all our current security settings before going multi-host.
I know I'm going to need this when it's time to update the plugin. Make sure to remove the -master from the folder name so it's just "twofactor_gauthenticator" and use the code mentioned in the Cloudron doc page, and not the one on the plugin's github page.
Thanks for notifying! We use an app called release bell to get notifications and it has bug for some repos like roundcube where we don't get notification. Generally, I check on these apps monthly manually. For the moment, if I missed it, just open a forum post here and I can push out an update.
We are fixing release bell in the mean time to support gitlab/gogs/gitea as well.
I found the github email notifications very reliable when setting "Watch -> Releases only".
Changed 🙂 As it is the default configuration for Roundcube it is working like intended and we could leave it like this? I don't think its a rare use case but maybe it could be added to the documentation (which I always found very helpful).