Posts by BudSpencer

  • update to imscp 1.4.7 /error > SASL DIGEST-MD5 authentication failed

    After Update from 1.2.7 to 1.4.7 i got a lot error with mails.


    Client: Outlook 2010 and Outlook 2016


    Log: Aug 23 09:04:49 server3 dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=80.22.2*.*, lip=136.243.*.*, session=<lhPpU2ZX+QBQhIRj>


    after adding to auth_mechanisms = plain login
    digest-md5 CRAM-MD5


    Log: Aug 23 10:19:48 server3 dovecot: imap-login: Disconnected (auth failed, 3 attempts in 27 secs): user=<[email protected]>, method=DIGEST-MD5, rip=80.22.2*.**, lip=136.243.*.*, session=<zgIy4mlXVQBQhIRj>
    after remove (Require logon using Secure Password Authentication (SPA)


    Client can Login but!!
    Now i cant Login (EM Client) and Roundcube.


    Log: Aug 23 20:48:12 server3 postfix/smtpd[3111]: warning: ip-178-******.unitymediagroup.de[178.202.*.*]: SASL DIGEST-MD5 authentication failed: PDIwOTkxNzgwNDA0Mjc1NDguMTUwMzUxNDA5MEBzZXJ2ZXIzPg==


    Server Debian Jessie 8.9
    imscp 1.4.7



    Saslfinger -s

  • Joomla 3.6.4 open_basedir restriction

    All Sites working again:


    Solution:
    Joomla 3.6.3 and higher has changend the Composer Components.
    You can update to 3.6.4 just restore one Old File from Joomla 3.6.2 "autoload_real.php" in /libary/vendor/composer
    The 3.6.2 autoload_real.php file has no Security issues.

  • Joomla 3.6.4 open_basedir restriction

    After i update to Joomla 3.6.4 (High Risk Security), all 5 updates websites dosent work.


    Sites on Joomla 3.6.3 , Wordpress, and all other php sites works fine.


    If i restart the php process, and open a Joomla 3.6.4 site, the first opened site is shown, the other 4 not.
    This works with all site, the first loaded Joomla is showen, the other 4 not.


    php error show this:


    Code
    1. Warning: require(): open_basedir restriction in effect. File(/var/www/virtual/DOMAIN1/htdocs/libraries/vendor/composer/../joomla/string/src/phputf8/utf8.php) is not within the allowed path(s): (/var/www/virtual/DOMAIN2/:/usr/share/php/:/dev/random:/dev/urandom) in /var/www/virtual/DOMAIN2/htdocs/libraries/vendor/composer/autoload_real.php on line 66 Warning: require(/var/www/virtual/DOMAIN1/htdocs/libraries/vendor/composer/../joomla/string/src/phputf8/utf8.php): failed to open stream: Operation not permitted in /var/www/virtual/DOMAIN2/htdocs/libraries/vendor/composer/autoload_real.php on line 66 Fatal error: require(): Failed opening required '/var/www/virtual/DOMAIN1/htdocs/libraries/vendor/composer/../joomla/string/src/phputf8/utf8.php' (include_path='.:/usr/share/php') in /var/www/virtual/DOMAIN2/htdocs/libraries/vendor/composer/autoload_real.php on line 66


    Data:
    Debian 8.5
    PHP 5.6.27-0+deb8u1
    Server version: Apache/2.4.10 (Debian)
    PHP Limit 256M

  • (SOLVED) Cant Update -- Unknown column 'domain_dns_status' in 'where clause'

    Old Server 1.2.2 to New Server 1.2.9.
    I follow the execlent Migration Guide on GitHub (b13n1u/1109474), everything went fine until

    Code
    1. perl /var/www/imscp/engine/setup/imscp-setup -d

    It exiting with Error:

    Code
    1. "[ERROR] main::setupRebuildCustomerFiles:
    2. Error while rebuilding customers files: [ERROR] main::_process: Error while processing 1, xxxxxxx.de, tochange.
    3. main::_process: See /var/log/imscp/Domain_module_xxxxxx.de.log for more details.
    4. Modules::Domain::add: Error while executing statement: Unknown column 'domain_dns_status' in 'where clause'


    The domain has nothing special, just 2 Wordpress.


    • SERVER DETAILS
    • Server-Version: 10.0.22-MariaDB-0+deb8u1 - (Debian)
    • Datenbank-Client Version: libmysql - mysqlnd 5.0.11-dev - 20120503 - $Id: 3c688b6bbc30d36af3ac34fdd4b7b5b787fe5555 $
    • PHP-Erweiterung: mysqli
    • PHP-Version: 5.6.14-0+deb8u1

  • policyd-weight: Email DNS blacklist AHBL was shut down - Probably no email delivery

    Quote from Nuxwin

    Hello ;


    I'll remove policyd-weight in next release ( also postgrey ). Too many users complaining about those tools. If an admin want them, he will have to install them itself


    I think, removing policyd-weight isssent a good idea. It would be better to make optional, like Dovecote and Courier etc.
    A blank MailServer without spam (policyd-weight, postscreen etc.) protection is Crazy.