Posts by Nuxwin

    rr10111101


    Please edit your last answer and suround your copy-past with bbcode tags: [code] bla bla bla [/code]


    About your question: If you enable SSL for the services (which include the smtp server) through the i-MSCP installer (or while reconfiguration), you should still be able to authentication without SSL (not recommended). You need give us further details: How your client (using no ssl) are configured exactly?

    The exact error message

    I: Cleaning COW directory
    [ERROR] main: An error occurred while executing MAKE(1) target(s) for PHP 5.3.29: /usr/lib/pbuilder/pbuilder-modules: line 487: /var/cache/pbuilder/build/cow.26226/usr/sbin/policy-rc.d: No such file or directory

    If your server is a container, please run the command with the --no-chroot option. Next time please search on our forums becaus this problem and the solution has been already given.

    If the file 50_psw_dpkg_post_invoke_tasks.pl listener file is present, it could be due to a permission problem. This listener file is automatically installed by the PhpSwitcher plugin. Permissions on that file should be root:imscp 0640. You can fix the permissions by executing the following command:


    Code
    1. perl /var/www/imscp/engine/setup/set-engine-permissions.pl -dv


    This bug will be fixed in the PhpSwitcher plugin version 5.0.4. Thank you for your report.


    bug.png

    I don't agree with that. The domain owner usually doesn't know what for example abuse emails mean. In most of the cases the owner him- or herself doesn't have that tecnical knowledge but the reseller or servers administrator has. I think it would be good to make it settable.

    The bla bla on that subject is irrelevant. You have the RFC that would help to answer your question.


    To answer your question: No there is no way to override default postmaster, abuse and so on email address. However you're free to create a feature request on our bug tracker.


    See https://www.ietf.org/rfc/rfc2142.txt

    As long as you update the roundcube instance by yourself, you cannot ask us for any support. What you expect from our side exactly? We deliver roundcube as a package and we adjust i-MSCP core according the roundcube version that we deliver. If you update to a newest Roundcube version that hasn't been tested by us, you cannot complain if you get any error message.

    I updated roundcube to Version 1.3.10 and now I get this:


    Invalid request! No data was saved.

    i-mscp is the latest.

    Can someone help me, please?

    As long as you update the roundcube instance by yourself, you cannot ask us for any support. What you expect from our side exactly? We deliver roundcube as a package and we adjust i-MSCP core according the roundcube version that we deliver. If you update to a newest Roundcube version that hasn't been tested by us, you cannot complain if you get any error message.