Posts by TheRiddler1982

    Hi all,

    I had to move my VPS and did a clean install of I-MSCP two months ago. I installed all the plugins I had on my old server. No modifications have been done to the config files outsite I-MSCP I am aware of. Everything works like it should :-). However, spam mails are not automatically deleted. Instead, SpamAssassin just flags it as spam like the example at the end of the post. I did not get any mails on my old setup.

    Could you help me how to configure I-MSCP to automatically delete/reject those messages? I know the risks :-). Believe me, every spam message is indeed spam.




    thanks for the quick fix. I mad a donation, it should have arrived 1h ago :-). I hope that the amount is fine. Currently, you have the best view on my server, so no more feedback from my side, as long as you have seen other things that crash oder are not set properly. What's the release date for the 1.5.x branch?

    Another thing: do you reasons for very slow Wordpress backend performances? Frontend ist nice, but the backend from clicking from one menu point to another takes decades. OPCACHE is active, PHP 7.1 is used instead of 5.6, I have a own VPS with SSD. I have no idea. MariaDB is 300MByte in size. Honestly, I do not why it's so big, but it's on SSD.


    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!


    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:

    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/ -start -name=imapd-ssl /usr/sbin/couriertcpd -address=178.33.26. ├─4918 /usr/sbin/couriertcpd -address= -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 ├─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 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:]Jul 23 01:55:47 menkisyscloudsrv29 imapd-ssl[4917]: LOGIN,, ip=[::ffff:], port=[53207], protocol=IMAPJul 23 01:55:47 menkisyscloudsrv29 imapd-ssl[4917]: Connection, ip=[::ffff:]Jul 23 01:55:47 menkisyscloudsrv29 imapd-ssl[4917]: LOGIN,, ip=[::ffff:], port=[53025], protocol=IMAP

    This is what the log looks like from tail -f /var/log/

    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, 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?