ALERT: dopey home user sorry to be a nuisance Is current Debian buster, dovecot, roundcube with enigma and managesieve plugins. Everything was working nicely 1.3.8 and then something went wrong. Since installed 1.4-beta. I was a bit confused because I read it that the "updateto" would update the downloaded 1.4-beta to the configuration from the previous install but updates instead the previous install.
Anyway it is working now and installation page has the green ticks except I just get the unhappy document face in the right hand window in the "settings" tab. In the "settings/folders" tab all the folders are there but I get the unhappy document picture if I try to make a new folder. I can move emails about between folders in "mail". Likewise the "PGP keys"tab shows the keys I copied there by hand but there is no information in the right hand window. There is the text "rapunzel.home refused to connect". ufw is turned off.
Is this likely an issue with Dovecot or something daft I haven't done in roundcube configuration ?
Can't see anything in any of the logs I've looked at except enigma log says:
[11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: USING GPG 2.2.12 with PHP 7.3.0-2 [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: OPENING GPG SUBPROCESS WITH THE FOLLOWING COMMAND: [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: /usr/bin/gpg --status-fd '3' --command-fd '4' --no-secmem-warning --no-tty --no-default-keyring --no-options --no-permission-warning --exit-on-status-write-error --trust-model always --pinentry-mode loopback --ignore-time-conflict --ignore-valid-from --with-colons --with-fingerprint --with-fingerprint --fixed-list-mode --homedir '/usr/share/roundcubemail/plugins/enigma/home/mick' --list-secret-keys [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: BEGIN PROCESSING [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: selecting streams [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: => got 1 [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: GPG output stream ready for reading [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: => about to read 65536 bytes from GPG output [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: => read 470 bytes [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: selecting streams [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: => got 1 [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: GPG output stream ready for reading [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: => about to read 65536 bytes from GPG output [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: => read 474 bytes [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: selecting streams [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: => got 3 [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: GPG output stream ready for reading [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: => about to read 65536 bytes from GPG output [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: => read 0 bytes [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: GPG error stream ready for reading [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: => about to read 65536 bytes from GPG error [11-Jan-2019 10:34:04 +0000]: <h5bcdh7c> GPG: => read 0 bytes
mick