Fresh Install Vesta cant connect to roundcube

[Fantom3D]

I've resolved my issue. I'm not sure why these two installs were different but there's a good chance that I used two slightly different install options. Either way, I thought I'd post what happened just in case someone else bumps up against this edge case.

The error I was getting was:

Code: Select all

Error: User initialization failed: namespace configuration error: Duplicate namespace prefix: ""

I compared my working VestaCP Ubuntu 16.04.4 install to my new (non-working dovecot) Ubuntu 16.04.4 install. The default namespace found in /etc/dovecot/dovecot.conf already included the inbox = yes option so there was no need to include this elsewhere (at least in my scenario). Also, the version of Dovecot in both installs is 2.2.22, and yes it is functional despite past comments. VestaCP is functional/compatible with Ubuntu 16.04.4.

When comparing the files in each, I noticed that the working install did not have the file:

Code: Select all

/etc/dovecot/conf.d/15-mailboxes.conf

This file looks to be declaring a new namespace "inbox". The settings appear to a re-statement of what is in the default namespace in /etc/dovecot.conf file and shouldn't be needed. I presume this is why dovecot was giving a duplicate namespace "" error. The "" being the default namespace. I removed this file (after backing it up), and restarted dovecot

Code: Select all

systemctl restart dovecot

and I was now able to log in via roundcube.

I hope this helps someone else should they bump into this edge case.

Thank you! I was looking for a solution for few hours! you are the best :)

[FrazzledPenguin]

I'm very happy the information was able to help someone. :)

[luca.dex]

To solve the problem I simply edited dovecot.conf from this:

Code: Select all

...
namespace {
    type = private
    separator = /
    prefix =
    inbox = yes

    ...
}

into:

Code: Select all

...
namespace {
    type = private
    separator = /
    prefix = mail/
    inbox = yes
    list = no
    
    ...
}

Ciao

[khel]

I've resolved my issue. I'm not sure why these two installs were different but there's a good chance that I used two slightly different install options. Either way, I thought I'd post what happened just in case someone else bumps up against this edge case.

The error I was getting was:

Code: Select all

Error: User initialization failed: namespace configuration error: Duplicate namespace prefix: ""

I compared my working VestaCP Ubuntu 16.04.4 install to my new (non-working dovecot) Ubuntu 16.04.4 install. The default namespace found in /etc/dovecot/dovecot.conf already included the inbox = yes option so there was no need to include this elsewhere (at least in my scenario). Also, the version of Dovecot in both installs is 2.2.22, and yes it is functional despite past comments. VestaCP is functional/compatible with Ubuntu 16.04.4.

When comparing the files in each, I noticed that the working install did not have the file:

Code: Select all

/etc/dovecot/conf.d/15-mailboxes.conf

This file looks to be declaring a new namespace "inbox". The settings appear to a re-statement of what is in the default namespace in /etc/dovecot.conf file and shouldn't be needed. I presume this is why dovecot was giving a duplicate namespace "" error. The "" being the default namespace. I removed this file (after backing it up), and restarted dovecot

Code: Select all

systemctl restart dovecot

and I was now able to log in via roundcube.

I hope this helps someone else should they bump into this edge case.

Thanks

[amrithaakarthi]

FrazzledPenguin thank you verymuch

it solved the problem

[cottager]

I wanted to mention I hit this on ubuntu 16.04 as it's deployed on ovh. imap wasn't connecting in an email client, and roundcube failed as well. I found this thread, removed 15-mailboxes.conf, restarted dovecot, and solved. Thanks for posting your information here.

[Aporie]

I was getting this issue : The reported error was “Failed to issue NAMESPACE: IMAP server said BYE: Internal error occurred. Refer to server log for more information.”.

Renaming 15-mailboxes.conf in 15-mailboxes.conf.bkp did the trick.

Thanks