Posts by sanitariu


    I am using the latest official stable panel:

    i-MSCP 1.5.3

    Build: 2018120800

    Codename: Ennio Morricone

    There is no newer than this.

    And do not install maintenance release from github except if you want to break your installation.....

    If you point me to a link for newer i-mscp panel i will get it.

    Bug tracker does not work again !

    The problem is if you use opendkim with external mail server and if the external mail server does not sign the letters.

    DNS dkim option is discardable. This means .... my dns has the key and all mail server should sign it if they did not

    just drop the letter.

    This is a problem specially if you can not disable opendkim keys for specific domain.

    The easiest solution is to add option as it was on older panels to skip specific domain from opendkim key generation.

    We have the following solutions for that problem:

    1. Remove opendkim and do not use it if you have a client with external mail server.

    2. Use opendkim with external mail server but setup the keys at server side to sign.

    3. Fix i-mscp to add option for skip specific domain.

    I would pick option 3 for sure. This was the old behaviour and i do not know why you changed it ?!

    Let allow domain owner to choose if he wants dkim or not !

    I-mscp 1.5.3 - Build: 2018051

    OpenDkim: 2.0.0

    Debian 9

    I have reported that bug already but it says too old ... create new thread.

    Thanks for the support. I patched manually webmail and some other stuff so i hope it works now by magic.

    I will wait and update next version when it goes out.

    Yes i have backups but that release touched a lot of stuff so i think it will be dangerous to try the backups.

    I still do not know if phpswitcher is working and some other plugins....

    I will wait and even pay for newer as far as i can update my current maintenance stuck now.

    As i said downgrading and upgrading is impossible now. And reinstalling is not an option for me.

    Please change maintenance to development or something like that so no other people get confused.


    By accident i upgraded my 1.5.3 installation to imscp-1.5.3-maintenance. This led to some huge problems. One is that i can not downgrade and the other

    is that i have problems with plugins even paid ones. I saw too late that we should not use imscp-1.5.3-maintenance but then why it is allowed to be downloaded ?

    You are unable to test it in real situation. Also the name maintenance is misleading. For me it means that this revision has just some small

    fixes over 1.5.3 and you should use it. If it is something else not for mass usage just name it development. Now i am stuck to nowhere.

    Can not downgrade and can not upgrade because as far as i know there is no newer version after 1.5.3 ?

    The error i have is: "Couldn't synchronize plugin data: Invalid plugin archive: The 'name' plugin info field is missing."

    Do you have any solution for me ?



    I am using latest stable i-mscp 1.5.3 installed on debian 8 system.

    I have opendkim installed.

    I have the following scenario:

    2 domains and in one client account.

    One of the domains have external mail server (

    Opendkim is enabled.

    When we try sending mail from that external server ( to email address from the

    other domain ( we always fail with the following reason:

    "5.7.1 rejected due to DKIM ADSP evaluation;"

    The problem is that "dkim=discardable" and we can not easy change that.

    Also we can not disable opendkim for a particular domain as it was before some releases.

    Any idea how can send email to without disabling opendkim globally ?

    i-MSCP 1.5.3

    Build: 20180516

    Codename: Ennio Morricone

    php -v

    PHP 5.6.36-1+0~20180505045733.13+jessie~1.gbp9b5cab (cli)

    Copyright (c) 1997-2016 The PHP Group

    Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies

    with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies


    I put image here:

    I can confirm that SSL is working normal !

    It just does not have dates and i am afraid not to stop ?

    Maybe i should try to reinstall the module ?

    Looking at /var/log/letsencrypt/letsencrypt.log

    I see:


    Your key file has been saved at:


    Your cert will expire on 2018-09-06. To obtain a........


    Seems like cache or something similar ?


    I am using Letrencrypt 3.4.2.

    I activated everything is working from ssl point of view.

    But clicking on letsencrypt for the domain i see N/A on Expiry date and N/A on Next renewal date.

    The same is on any domain i activate here. SSL working but no dates.

    Will the be a problem after 1 month ?