Problem Loging into RoundCube

Discussion in 'HOWTO-Related Questions' started by botxo, Dec 20, 2016.

  1. botxo

    botxo New Member

    Hey!

    I followed this guide
    https://www.howtoforge.com/tutorial...php-pureftpd-postfix-dovecot-and-ispconfig/3/
    Awesome I have to say.

    I have finished the instalation but now I'm facing a trouble and I dont now know to solve it.

    I have created from the ISPConfig a new inbox mail o mail account "buzon de correo" a new mail account. It seems to be ok but when i try to accesss from the roundcube interface it says "the username or the pasword is incorrect".

    I have trydeleting account, creating new one, changing password...
    I took a look to the phpmyadmin and i see that in the table users from roundcube db is empty nor like mail_user table from ISPConfig db that have the information stored.

    EDIT:
    I have checked that with doveadm user * that ispconfig doesn't create users in dovecot.
    [[email protected] ~]# doveadm user *
    nfsnobody
    vmail
    getmail
    ispapps
    ispconfig


    Greetings all.
     
    Last edited: Dec 22, 2016
  2. botxo

    botxo New Member

    Problem solved!!

    I don't know if this the best solution but.. I will explain it in order to help another facing my problem.

    The roundcube was reading the users and pass from PAM but not from the bd of ISPConfig so the file dovecot-sql wan't used.

    So, you edit the file 10-auth.conf
    nano /etc/dovecot/conf.d/10-auth.conf

    and in the last lines it import the way of login


    !include auth-system.conf.ext

    #!include auth-sql.conf.ext
    #!include auth-ldap.conf.ext
    #!include auth-passwdfile.conf.ext
    #!include auth-checkpassword.conf.ext
    #!include auth-vpopmail.conf.ext
    #!include auth-static.conf.ext

    This is how I found the file, in order to maki it works you have to coment "!include auth-system.conf.ext" and uncomment "
    !include auth-sql.conf.ext"

    Finally you edit "auth-sql.conf.ext" to change the location of the dovecot-sql.conf with the configuration for ispconfig db.

    Greeting and thanks.
    SSG
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    There seems to be a general problem with your ispconfig installation then, as no files in /etc/dovecot/conf.d/ are read by dovecot on an ispconfig system. ISPConfig replaces the dovecot.conf file with it's own one and this file reads no include files at all, so your master dovecot file must be wrong if your config is read from the includes folder.

    Roundcube itself reads not from pam, it just does an imap authentication, so when imap is not working or configured incorrectly, then roundcube will not work as well. I recommend that you download ispconfig again, run the update.php script and chose to reconfigure services to let ispconfig write the correct configuration as there are probably other things that will fail as well.
     
    botxo likes this.
  4. botxo

    botxo New Member

    Hi!!

    I already update the ISPConfig but nothing happens. I suppose the same as you but for example the dovecot/dovecot-sql.conf was with the ispconfig configuration, has the pass the correct db and user so...

    There is my dovectot.conf. I don't know i it's the normal dovectot config or it's generated by ISPConfig
    Code:
    [*@vps* ~]$ cat /etc/dovecot/dovecot.conf
    ## Dovecot configuration file
    
    # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration
    
    # "doveconf -n" command gives a clean output of the changed settings. Use it
    # instead of copy&pasting files when posting to the Dovecot mailing list.
    
    # '#' character and everything after it is treated as comments. Extra spaces
    # and tabs are ignored. If you want to use either of these explicitly, put the
    # value inside quotes, eg.: key = "# char and trailing whitespace  "
    
    # Most (but not all) settings can be overridden by different protocols and/or
    # source/destination IPs by placing the settings inside sections, for example:
    # protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { }
    
    # Default values are shown for each setting, it's not required to uncomment
    # those. These are exceptions to this though: No sections (e.g. namespace {})
    # or plugin settings are added by default, they're listed only as examples.
    # Paths are also just examples with the real defaults being based on configure
    # options. The paths listed here are for configure --prefix=/usr
    # --sysconfdir=/etc --localstatedir=/var
    
    # Protocols we want to be serving.
    #protocols = imap pop3 lmtp
    
    # A comma separated list of IPs or hosts where to listen in for connections.
    # "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces.
    # If you want to specify non-default ports or anything more complex,
    # edit conf.d/master.conf.
    #listen = *, ::
    
    # Base directory where to store runtime data.
    #base_dir = /var/run/dovecot/
    
    # Name of this instance. In multi-instance setup doveadm and other commands
    # can use -i <instance_name> to select which instance is used (an alternative
    # to -c <config_path>). The instance name is also added to Dovecot processes
    # in ps output.
    #instance_name = dovecot
    
    # Greeting message for clients.
    #login_greeting = Dovecot ready.
    
    # Space separated list of trusted network ranges. Connections from these
    # IPs are allowed to override their IP addresses and ports (for logging and
    # for authentication checks). disable_plaintext_auth is also ignored for
    # these networks. Typically you'd specify your IMAP proxy servers here.
    #login_trusted_networks =
    
    # Space separated list of login access check sockets (e.g. tcpwrap)
    #login_access_sockets =
    
    # With proxy_maybe=yes if proxy destination matches any of these IPs, don't do
    # proxying. This isn't necessary normally, but may be useful if the destination
    # IP is e.g. a load balancer's IP.
    #auth_proxy_self =
    
    # Show more verbose process titles (in ps). Currently shows user name and
    # IP address. Useful for seeing who are actually using the IMAP processes
    # (eg. shared mailboxes or if same uid is used for multiple accounts).
    #verbose_proctitle = no
    
    # Should all processes be killed when Dovecot master process shuts down.
    # Setting this to "no" means that Dovecot can be upgraded without
    # forcing existing client connections to close (although that could also be
    # a problem if the upgrade is e.g. because of a security fix).
    #shutdown_clients = yes
    
    # If non-zero, run mail commands via this many connections to doveadm server,
    # instead of running them directly in the same process.
    #doveadm_worker_count = 0
    # UNIX socket or host:port used for connecting to doveadm server
    #doveadm_socket_path = doveadm-server
    
    # Space separated list of environment variables that are preserved on Dovecot
    # startup and passed down to all of its child processes. You can also give
    # key=value pairs to always set specific settings.
    #import_environment = TZ
    
    ##
    ## Dictionary server settings
    ##
    
    # Dictionary can be used to store key=value lists. This is used by several
    # plugins. The dictionary can be accessed either directly or though a
    # dictionary server. The following dict block maps dictionary names to URIs
    # when the server is used. These can then be referenced using URIs in format
    # "proxy::<name>".
    
    dict {
      #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
      #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext
    }
    
    # Most of the actual configuration gets included below. The filenames are
    # first sorted by their ASCII value and parsed in that order. The 00-prefixes
    # in filenames are intended to make it easier to understand the ordering.
    !include conf.d/*.conf
    
    # A config file can also tried to be included without giving an error if
    # it's not found:
    !include_try local.conf
    
    So... may be a permission problem?, for example with amavisd, in order to start it I had to change the permision (chown) of it config file to amavis:amavis

    It's recomendable to follow the guide using the root user or with other one? I did everithing with the root user.

    Greetings.
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    The above config file is not the one from ispconfig installer. All steps in the perfect server tutorials have to be executed as root user and there are no additional steps or changes in permissions of files required. Maybe you installed ispconfig in expert mode and chose to not configure the mail system? In this case it will be skipped on updates as well.
     
  6. botxo

    botxo New Member

    I`m sorry to say that the mode I used was standart. I followed the guide step by step and I really dont know why this has happened, also I update ispconfig instalation and reconfig dovecot with no changes on files

    regards
     

Share This Page