Posts by DeltaLima

  • Please help - update i-MSCP to run on new system

    One thing I havent tested before but I notice now: My dovecot login fails now with the error


    Code
    1. dovecot: imap-login: Error: Failed to initialize SSL server context: Can't load DH parameters (ssl_dh setting): error:1408518A:SSL routines:ssl3_ctx_ctrl:dh key too small: user│...

    But it seems that can be easely fixed:

    https://www.mediamill.de/blog/…server-context-cant-load/


    Update 1:

    And there seems to be some options get depricated soon

    Code
    1. dovecot: config: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf │
    2. dovecot: config: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:175: ssl_protocols has been replaced by ssl_min_protocol

    This could also be fixed easy (https://unix.stackexchange.com…laced-by-ssl-min-protocol), just delete the line with ssl_protocols in /etc/dovecot/dovecot.conf and add the line

    ssl_min_protocol = TLSv1.2



    Update 2:


    SpamAssassin Plugin misses a column

    Code
    1. spamd[1457]: auto-whitelist: sql-based get_addr_entry [email protected]|none: SQL error: Unknown column 'msgcount' in 'field list' │
    2. spamd[1457]: auto-whitelist: sql-based add_score/update 1|-1|[email protected]|[email protected]|none: SQL error: Unknown column 'msgcount' in 'field list'[

    seems to be this bug: https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7663

    Can be solved with adding the column as mentioned

    Code
    1. $ mysql imscp_spamassassin -e "alter table awl add msgcount int(11);"


    Update 3:


    When receiving a mail, i get a permission denied error from dovecot

    Code
    1. postfix/pipe[8047]: 18CF4C0DA1: to=<[email protected]>, relay=dovecot, delay=0.39, delays=0.27/0/0/0.11, dsn=2.0.0, status=sent (delivered via dovecot service (lda([email protected]): Error: net_connect_unix(/run/dovecot/stats-writer) failed: Permission den))

    I have tried to delete it, that havent worked. Also giving the user dovecot the ownership of this file didnt worked either.

    Putting an additional service definition into dovecot.conf and specifying the permissions did the trick (https://dovecot.org/list/dovecot/2022-January/123745.html)


    Code
    1. service stats {
    2. unix_listener stats-writer {
    3. mode = 0666
    4. }
    5. }


    Update 4:


    Also when receiving a mail, I get errors from dovecat that a sieve folder cannot be found


    Code
    1. dovecot: imap([email protected])<169859><Funnyrandomstring>: Error: stat(/var/mail/virtual/domain.org/mail//.dovecot.sieve/tmp) failed: Not a directory

    I found this maillisting entry https://dovecot.org/pipermail/dovecot/2020-March/118475.html

    but for now I havent dove deeper into it :)

  • Please help - update i-MSCP to run on new system

    Thanks @joximu and all others that have worked on to get i-mscp maintenance branch working on debian 10/11.


    Today I upgraded my i-mscp 1.5.3 debian 9 installation (i know, quite late) and after a bit fiddeling around i came out with following steps for a smooth upgrade:


    0. Make a backup of your host!

    1. git clone joxis branch https://github.com/joximu/imscp/tree/1.5.3-maintenance-joxi and to commented

    2. (optional if you DONT use letsencrypt) edit OpenSSL.pm https://git.la10cy.net/DeltaLi…0e66d66ffccb7bdb622405969 (Background LetsEncrypt - SSL certificate is not valid )

    3. Remove your SSL certificate youve entered with the panel for your aliasses and (sub)domains.

    In my case i used letsencrypt - but without the plugin. that caused me into some issues, so i had to disable all ssl certificates in the panel to get a working upgrade

    4. disable all plugins you have active.

    same as for the ssl certificates. after the upgrade, the plugins (clamav, spamassassin, opendkim, mailgraph, PolicydSPF, ServerDefaultPage) worked all fine again and the dkim keys didnt changed :)

    5. dist-upgrade your machine to buster

    6. dist-upgrade after you rebooted the machine to bullseye

    7. now run the installer script:

    Code
    1. perl imscp-autoinstall -d -r

    just go through the installer, change the PHP version to a more recent one, and dont get confused when the installer wants to create a new admin account, just let it creating it.

    8. installer should be ran through without errors.

    9. reboot

    10. enable ssl certificates for your domains and aliasses

    11. enable your plugins

    after the upgrade spamassassin plugin was crying that "WEBMAIL_PACKAGES" was not found in /etc/imscp/imscp.conf

    depending which webmailer you choose, enter it. for my installation i had to add following line before activating it

    Code
    1. WEBMAIL_PACKAGES = Rainloop

    12. Youre done! 🥳



    Maybe this will help somebody. Everyone who reads this and still runs a debian 9 installation, Please upgrade now! Debian 9 is EOL since 06/2022

  • debian 9 install error

    thanks a million , exactly what i was looking for! actually im upgrading my installation from debian 9 (bit too late, i know ^^) to 10 and hopefully to 11 :) Will also try getting your fork working on my setup :)

  • i-MSCP next release 2022

    I'm also hopefully waiting for an update but for now i have the feeling I have to hack around myself to get the latest i-mscp running on debian 11.

    If I'm doing so, I will let you know here and share the results

  • New RoundCube version

    Maybe this link will help you AlexSwamp


    https://www.roundcubeforum.net/index.php?topic=24503.0



    it would be interesting whats in your error log file.


    another often failure point are file permissions - have you checked them for roundcube?


    this tip will not help you with roundcube but may give you a working webmailer. Switch to rainloop mail - I did it because it's for me the better choice and updating the version which came with imscp is pretty easy and straight forward to the rainloop documentation.

  • Reinstalling i-MSCP, from official release (1.5.3-2018120800) or Github?

    Glad you opened this thread with that question - i also was wondering which to use - the "latest" stable release or the imscp-maintenance branch from github.


    I tried an upgrade from 1.5.3 to maintenance branch on a test system which failed greatly.. only way to get back to a working system was apply the latest database backup and run the 1.5.3 autoinstaller. (btw props fpr the autoinstaller - it self healed everything after this f*up)

    I ended up with backporting some of the stuff from the maintenance branch to 1.5.3 for my environment as i needed some newer php and some of the TLS fixes.


    And good news that Nuxwin wrote few weeks ago that a new release is in the pipeline! If you are looking for a tester, i'm willed to be one as my imscp "production" instance is just for me, friends and family :)