IMAP SSL service is running but panel shows service down

  • Hi i-MSCP Team,


    by clicking through the i-MSCP panel I have noticed that (besides telnet) IMAP SSL is not running (service down). Though, I can receive mails with SSL.


    The service is running:


    Code
    1. root@menkisyscloudsrv29:/etc/courier# service courier-imap-ssl status● courier-imap-ssl.service - Courier IMAP Daemon (SSL) Loaded: loaded (/lib/systemd/system/courier-imap-ssl.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2017-07-23 01:54:51 CEST; 2min 45s ago Process: 4894 ExecStop=/usr/sbin/imapd-ssl stop (code=exited, status=0/SUCCESS) Process: 4900 ExecStart=/usr/sbin/imapd-ssl start (code=exited, status=0/SUCCESS) Main PID: 4917 (courierlogger) Tasks: 7 (limit: 4915) CGroup: /system.slice/courier-imap-ssl.service ├─4917 /usr/sbin/courierlogger -pid=/var/run/courier/imapd-ssl.pid -start -name=imapd-ssl /usr/sbin/couriertcpd -address=178.33.26. ├─4918 /usr/sbin/couriertcpd -address=178.33.26.29 -maxprocs=40 -maxperip=20 -access=.dat -nodnslookup -noidentlookup 993 /usr/bin/ ├─4946 /usr/bin/couriertls -server -tcpd /usr/lib/courier/courier/imaplogin /usr/bin/imapd Maildir ├─4947 /usr/bin/imapd ziin.de/look/ ├─4949 /usr/lib/gamin/gam_server ├─4950 /usr/bin/couriertls -server -tcpd /usr/lib/courier/courier/imaplogin /usr/bin/imapd Maildir └─4951 /usr/bin/imapd ziin.de/look/Jul 23 01:54:51 menkisyscloudsrv29 systemd[1]: Starting Courier IMAP Daemon (SSL)...Jul 23 01:54:51 menkisyscloudsrv29 imapd-ssl[4900]: Usage: /usr/bin/makedat -src=src -file=file -tmp=tmpfile -hup=hupfile [-cidr]Jul 23 01:54:51 menkisyscloudsrv29 systemd[1]: Started Courier IMAP Daemon (SSL).Jul 23 01:54:51 menkisyscloudsrv29 imapd-ssl[4917]: .dat: No such file or directoryJul 23 01:55:47 menkisyscloudsrv29 imapd-ssl[4917]: Connection, ip=[::ffff:178.203.233.225]Jul 23 01:55:47 menkisyscloudsrv29 imapd-ssl[4917]: LOGIN, [email protected], ip=[::ffff:178.203.233.225], port=[53207], protocol=IMAPJul 23 01:55:47 menkisyscloudsrv29 imapd-ssl[4917]: Connection, ip=[::ffff:178.203.233.225]Jul 23 01:55:47 menkisyscloudsrv29 imapd-ssl[4917]: LOGIN, [email protected], ip=[::ffff:178.203.233.225], port=[53025], protocol=IMAP


    This is what the log looks like from tail -f /var/log/mail.info:



    Just a few questions: what does .dat no such file or directory mean (line 26)? Also, I am getting SASL LOGIN authentication failed messages. When opening the postfix main.cf, there is a note that I must not edit that file.




    I am using Debian 9 with i-MSCP 1.4.7, MariaDB 10.2, PHP 7.1 and Apache 2.4.25.


    How do I fix that?


    Thanks,
    Sven

  • Just a few questions: what does .dat no such file or directory mean (line 26)?

    http://www.courier-mta.org/makedat.html
    I'll investigate because I never encountered such issue.


    Also, I am getting SASL LOGIN authentication failed messages.


    Result of mount command please.


    BTW: One thread = One problem. Here, you're talking about IMAP-SSL and SASL (two unrelated problems).


    When opening the postfix main.cf, there is a note that I must not edit that file.

    That is expected. Those warning are made to warn the administrator on the fact that any manual change will be lost on next i-MSCP update/reconfiguration

    I am using Debian 9 with i-MSCP 1.4.7, MariaDB 10.2, PHP 7.1 and Apache 2.4.25.


    Next time, don't forget to say us that you use Courier as IMAP/POP server.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • Hi,


    thanks for the fast reply.


    How do I get the service running in i-MSCP? on the console, it shows that it is running. Does it mean, that I cannot connect securely to my mailserver?


    Thanks!

  • @TheRiddler1982



    Your public key is installed on my server.

    Ok but.... Without your server IP address (and SSH port if not default) I can't do anything ;)

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • @TheRiddler1982


    I did checked your courier-imap installation. The problem is due to the fact that you have played too much with your installation. Indeed many parameters were changed manually. For instance, the value of the SSLADDRESS parameter from the /etc/courier/imapd-ssl configuration file is your server wan IP address while by default, the value for that parameter should be 0 (listen on all interfaces).


    i-MSCP is trying to connect to the IMAP server through localhost but your server don't listen locally as explained above:

    Code
    1. root@menkisyscloudsrv29:~# netstat -plunt |grep 993
    2. tcp 0 0 1x8.3x.2x.x9:9x3 0.0.0.0:* LISTEN 4918/couriertcpd

    You should better not to touch something that you don't understand ;) Note that I've not changed anything yet. I'm waiting for your instructions.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • Hi again,


    sorry for keeping you waiting. Again, I have changed it to 0 but now I cannot establish a login with imap on my mail clients and with the rainloop web interface. Also, the FTP service is now down, I do not understand that.


    I'd be more than happy, if you could fix that. I know that I change things I do not fully understand, that's how I learn :-). I will make a donation to thank you for that.


    Thanks a lot!



    Bye,
    Sven

  • @TheRiddler1982



    I'd be more than happy, if you could fix that.

    The following issues were addressed on your server:

    • Incompatibility issue with the MariaDB client library that is provided by the MariaDB 10.2 repository (MariaDB team): I had to force installation of the libmariadbclient18 package from the Debian repository. It seem that the libdbd-mysql-perl package is not compatible with the client library provided by MariaDB 10.2 repository (MariaDB team). I'll investigate further and a fix will be added in version 1.5.0 (official). See the /etc/apt/preferences.d/nxw_quickfix file for my temporary solution.
    • ProFTPD start failure: ProFTPD was unable to start due to a problem with the sql module. A file was missing somewhere. I had to purge ProFTPD and reinstall it.
    • IMAP server connection failures: I've processed a full reinstallation.
    • I've updated your i-MSCP installation to current 1.5.x branch. There are still some issues to fix in the frontEnd but at least, your system is working.

    Also:


    For testing purpose, I've created an administrator account (nuxwin)
    I've tested an FTP connection by creating an FTP account ([email protected])
    I've tested IMAP connection from both roundcube and rainloop. For this, I've created a normal mail account ([email protected])


    I'm now waiting for your feedback. Note that I'll update your i-MSCP installation again when i-MSCP 1.5.0 will be released.

    I will make a donation to thank you for that.

    I hope so, else, you will get an invoice :D

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206