Posts by robbo007

  • Error with CERT

    That did it. Looks like the problem was with the file permissions.
    Great thanks Flames!!
    I re-ran the ssl install and all working. :)


    I still get this error in my /var/log/mail.log I'll investigate...


    Feb 3 23:51:57 sosaria imapd-ssl: couriertls: /etc/ssl/certs/930ac5d2.0: No such file or directory
    Feb 3 23:51:57 sosaria imapd-ssl: couriertls: /etc/ssl/certs/930ac5d2.0: No such file or directory
    Feb 3 23:51:57 sosaria imapd-ssl: couriertls: /etc/ssl/certs/930ac5d2.0: No such file or directory
    Feb 3 23:51:57 sosaria imapd-ssl: couriertls: /etc/ssl/certs/930ac5d2.0: No such file or directory

  • Error with CERT

    Its a purchased cert from RapidSSL.


    I run: perl /var/www/imscp/engine/setup/imscp-setup -dr ssl
    use my key file when specified
    then my intermediate cert
    then my cert


    It then start to update my client files. Gets to here then freezes.


    │ Performing step 19 from total of 22 │ │ │ │ Rebuilding customers files │ │ │ │ Performing step 18 from total of 28 │ │ │ │ Processing Htgroup (tochange) tasks: statistics:3 (ID 3)


    I control-C the setup. Now my control panel shows this when I navigate to it.


    Warning: The Exception Writer `iMSCP_Exception_Writer_Browser` was unable to write the following message: `The GUI `gui/data/sessions` directory must be writable. - at line: 274 in file: /var/www/imscp/gui/library/iMSCP/Initializer.php` Reason: Unable to find the box.tpl template file - at line: 533 in file: /var/www/imscp/gui/library/iMSCP/pTemplate.php in /var/www/imscp/gui/library/iMSCP/Exception/Handler.php on line 319


    I also see this in my /var/log/mail.log:


    Feb 3 23:34:10 sosaria imapd-ssl: couriertls: /etc/ssl/certs/930ac5d2.0: No such file or directory

  • Error with CERT

    I've just tried again with perl /var/www/imscp/engine/setup/imscp-setup -dr ssl and enter in teh right cert details and it gets stuck here. Does not advance. Any ideas?


    │ Performing step 19 from total of 22 │


    │ │


    │ Rebuilding customers files │


    │ │


    │ Performing step 18 from total of 28 │


    │ │


    │ Processing Htgroup (tochange) tasks: statistics:3 (ID 3)

  • Upgrade to 1.1.0 stable

    Just wondering whats the best approach to upgrade from my version? I'm on Debian Squeeze and I see in my Control Panel. Not sure what Release this is. RC?


    I-MSCP:
    GiT Master: Build 201307223
    Codename Eagle



    Download 1.1.0 Release
    #cd /usr/local/src
    # tar xjvf imscp-1.1.0-rc4.7.tar.bz2
    cd ./imscp
    perl imscp-autoinstall


    Is that the best way?

  • Error with CERT

    I've just launched perl /usr/local/src/imscp/imscp-autoinstall -dsr mailfilters to change some setting and the first screen said my cert was corrupt. I re added the correct private key, intermediate cert and my cert and I get the following at the end of the install???



    │ Modules::openssl::ssl_check_cert: SSL certificate │


    │ /etc/imscp/sosaria.secnet.es.pem is not valid. │


    │ Please, post on http://i-mscp.net/forum to get any help


    Any ideas? No matter which variable I use on the auto-install it seems to complain about the cert. My cert seems to be all on when I logon to the control panel..STrange???

  • CL_IP_NE_HELO=1.5 RESOLVED_IP_IS_NOT_HELO Postfix config

    Quote from flames


    judging on the previous questions, i guess robbo007 won't be able to setup a good working antispam setup and will rely on the default settings. anyway:
    blacklist check is enabled by i-mscp with policyweightd, you can still optimize it.
    for spamassassin and antivirus there are plugins from TheCry and mrpink


    I think the main problems here are: helo/hostname mismatch); Hows can I open my server up a little more. I think I prefer to have spam and all mail arriving no delays or blocked because of bad HELO configs on remote server.


    Could you point me to the right files to edit for the bad HELO and deactivate the greylisting?


    Example of bad helo as well.


    <helo=ayptorw3s042.azulejos.local> <[email protected]> <[email protected]>; delay: 6s
    Jan 21 22:45:31 sosaria postfix/smtpd[2972]: NOQUEUE: reject: RCPT from 177.Red-79-148-117.staticIP.rima-tde.net[79.148.117.177]: 550 5.7.1 <[email protected]>: Recipient address rejected: Mail appeared to be SPAM or forged. Ask your Mail/DNS-Administrator to correct HELO and DNS MX settings or to get removed from DNSBLs; MTA helo: ayptorw3s042.azulejos.local, MTA hostname: 177.red-79-148-117.staticip.rima-tde.net[79.148.117.177] (helo/hostname mismatch); from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<ayptorw3s042.AZULEJOS.LOCAL>


    Thanks,
    Rob