Posts by fulltilt

    thanks Nuxwin,
    there is second conf for postfix:

    Code
    1. warning: /var/spool/postfix/etc/resolv.conf and /etc/resolv.conf differ


    can this be ignored or shoud this also contain the external NS?
    or is it better to add all entrys into:
    /lib/init/rw/resolvconf and link to /etc/reslov.conf

    until v 1.1.1 I always entered my 3 external nameserver into resolv.conf

    Code
    1. nameserver 127.0.0.1
    2. nameserver 00.00.000.010
    3. nameserver 00.00.000.002
    4. nameserver 00.00.000.003


    after upgrading v1.0 to 1.1.2 relsov.conf contains only 1 entry:
    nameserver 127.0.0.1


    so I renamed the resolv.conf symlink to resolv.conf.bak and copied my original resolf.conf back to /etc/reslov.conf
    now I'm not sure if I did everything right, so I would like to ask how to use external nameserver with imscp

    funktioniert bestens, klasse Plugin !
    wenn ich jetzt eine White / Blacklist einbinden möchte, kann bzw. sollte dies auch über die Plugin Config geschehen oder über:
    /etc/spamassassin/local.cf


    ### edit ###


    funktioniert ;-)
    ich verwende reject in der config mit SpamScore=7

    in der stable gibt es ja momentan diesen Bug bei der Plugin Verwaltung:

    Code
    1. Fixed: Use of undefined constant SORT_NATURAL


    kann man so trotzdem Plugins installieren oder sollte man besser das Update abwarten?
    würde gerne das SpamAssassin Plugin installieren und bin mir jetzt nicht sicher ob nachher alles funktioniert

    because of many customers complain the mail quota ;(
    many user have 50-100 mail accounts and they do not want constantly adjust the qouta of all their mail accounts, I decided to set all accounts to unlimited.


    ### edit ###
    I guess this should work:

    SQL
    1. UPDATE mail_users SET quota = "0";
    2. UPDATE domain SET mail_quota = "0";

    Hello Nuxwin,
    the modification will generate a new (personal) cookie if the location is /admin or /client:

    Code
    1. Header set Set-Cookie: "YourCookieName=YourSecret123456; path=/;"


    if you try to call /pma or /tools/pma you will be redirected to the ControlPanel

    Code
    1. <Location /tools/pma> RewriteEngine On RewriteCond %{HTTP_COOKIE} !YourCookieName=YourSecret123456 [NC] RewriteRule .* https://admin.YourPanelURL.tld [L] </Location>


    I know this is a simple cookie protection only but it will be more comfortable for the User as htaccess password Protection ... and if a User gives a htaccess password to others everyone can access htaccess protected areas ...


    It would be better to use a random value for the cookie but this can be done only in the PHP sources (I dont want to touch or change it) ...


    the auto PMA login from sql_manage.tpl will not work because of the header location from pma_auth.php ... and so I changed the PMA URLs to:

    Code
    1. nano /var/www/imscp/gui/themes/default/client/sql_manage.tpl
    2. change:
    3. pma_auth.php?id={USER_ID}
    4. to:
    5. {PMA_PATH}

    For all those who are just as paranoid as I am ;-)


    This modification prevents direct access to PMA and Filemanager, you have to login into the control panel first.


    IMPORTANT: this is working only with version starting @ Latest Stable-Release: 1.1.2
    because of different V-Host entrys in earlier version


    replace with your details:
    - YourSecret123456
    - YourCookieName
    - https://admin.YourPanelURL.tld



    Code
    1. a2enmod headersservice apache2 restart



    Code
    1. nano /etc/apache2/sites-available/00_master.confbelow: <LocationMatch ^/.*/themes/.*/assets/.*$> Allow from all </LocationMatch>add: <LocationMatch /client> Header set Set-Cookie: "YourCookieName=YourSecret123456; path=/;" </LocationMatch> <LocationMatch /admin> Header set Set-Cookie: "YourCookieName=YourSecret123456; path=/;" </LocationMatch> <Location /pma> RewriteEngine On RewriteCond %{HTTP_COOKIE} !YourCookieName=YourSecret123456 [NC] RewriteRule .* https://admin.YourPanelURL.tld [L] </Location> <Location /filemanager> RewriteEngine On RewriteCond %{HTTP_COOKIE} !YourCookieName=YourSecret123456 [NC] RewriteRule .* https://admin.YourPanelURL.tld [L] </Location> <Location /tools/pma> RewriteEngine On RewriteCond %{HTTP_COOKIE} !YourCookieName=YourSecret123456 [NC] RewriteRule .* https://admin.YourPanelURL.tld [L] </Location> <Location /tools/filemanager> RewriteEngine On RewriteCond %{HTTP_COOKIE} !YourCookieName=YourSecret123456 [NC] RewriteRule .* https://admin.YourPanelURL.tld [L] </Location>


    Code
    1. nano /etc/apache2/sites-available/00_master_ssl.confbelow <LocationMatch ^/.*/themes/.*/assets/.*$> Allow from all </LocationMatch>add: <LocationMatch /client> Header set Set-Cookie: "YourCookieName=YourSecret123456; path=/;" </LocationMatch> <LocationMatch /admin> Header set Set-Cookie: "YourCookieName=YourSecret123456; path=/;" </LocationMatch> <Location /pma> RewriteEngine On RewriteCond %{HTTP_COOKIE} !YourCookieName=YourSecret123456 [NC] RewriteRule .* https://admin.YourPanelURL.tld [L] </Location> <Location /filemanager> RewriteEngine On RewriteCond %{HTTP_COOKIE} !YourCookieName=YourSecret123456 [NC] RewriteRule .* https://admin.YourPanelURL.tld [L] </Location> <Location /tools/pma> RewriteEngine On RewriteCond %{HTTP_COOKIE} !YourCookieName=YourSecret123456 [NC] RewriteRule .* https://admin.YourPanelURL.tld [L] </Location> <Location /tools/filemanager> RewriteEngine On RewriteCond %{HTTP_COOKIE} !YourCookieName=YourSecret123456 [NC] RewriteRule .* https://admin.YourPanelURL.tld [L] </Location>


    service apache2 restart


    Code
    1. nano /var/www/imscp/gui/themes/default/client/sql_manage.tplchange:pma_auth.php?id={USER_ID}to:{PMA_PATH}


    also as administrator you have to log into the panel before you can use PMA, therefore we will create a custom menu entry in the Admin Panel:

    Code
    1. Login your ControlPanel as Administrator
    2. create a custom menu for PMA
    3. https://admin.YourPanelURL.tld/pma