Posts by TheCry

TheCry · Jul 10th 2019

You problem is the source.list

In your list you will find this

Code

deb http://deb.debian.org/debian/ stable main contrib non-free
deb-src http://deb.debian.org/debian/ stable main contrib non-free

Now "Debian 10" is stable and your "Debian 9" got the packages to upgrade.

If you don't want to upgrade change the lines

Code

deb http://deb.debian.org/debian/ oldstable main contrib non-free
deb-src http://deb.debian.org/debian/ oldstable main contrib non-free

The same problem is under Debian 8

Code

deb http://deb.debian.org/debian/ oldoldstable main contrib non-free
deb-src http://deb.debian.org/debian/ oldoldstable main contrib non-free

The word "oldstable" is now "oldoldstable"

TheCry · Jun 25th 2019

Sorry for the late answer.. I will check it on my server and give a feedback

TheCry · May 22nd 2019

Quote from Nuxwin

I don't really understand why it would be so tedious to make use of a listener in that specific case. The i-MSCP Postfix server implementation provide a routine that make edition of the main.cf file very easy. As a sysadmin, editing a single file to remove or adding RBL servers is not so hard, isn't it?

It isn't hard.

I understand now why it is not so easy to implement. So i will do it with a listener

TheCry · May 21st 2019

Thanks Laurent.

I think the the SpamAssassin Feature should be implemented in the next SpamAssassin version (Dropping the Spam).

Adding RBL with the gui is better than to use a listerner..

Just my 2 cent

TheCry · May 21st 2019

Hi Laurent,

it will be a nice feature if you implement in the admin level a section to add, activate, deactivate differnt RBL servers.

At the moment the spam are horrible and if the customers add some forwarder to GMX, Hotmail, Web.de a.s.o. your server wil be added to the blacklist.

I did add the RBL servers manually to the main.cf (smtpd_recipient_restrictions)

Code

reject_rbl_client zen.spamhaus.org,
reject_rbl_client bl.spamcop.net,
reject_rbl_client dnsbl.sorbs.net,
reject_rbl_client cbl.abuseat.org,
reject_rbl_client b.barracudacentral.org,
reject_rbl_client dnsbl-1.uceprotect.net,

This helped me a lot.

Yes i know i can use a listener, but i think this is a nice feature for the panel.

Regards

Sascha

TheCry · May 20th 2019

Ja 2FA ist eine gute Sache, aber man kann es mit der Sicherheit auch übertreiben.

Man sollte immer abschätzen was für Kunden auf dem System betrieben wedren. Davon macht man es abhängig ob so etwas überhaupt benötigt wird.

Wenn Du auf Deinem System nur simple Webkunden hast ist 2FA mit Kanonen auf Spatzen geschossen.

Ändere das SSH Port, Richte Fail2Ban ordentlich ein und schon ist Dein Server auch sicher.

Just my 2 Cent

TheCry · May 20th 2019

Normaly it is not needed to it freshclam while installation of the plugin. So - From my site you can remove this in the next version

TheCry · May 4th 2019

Ein Dist-Upgrade ein ein OS Upgrade! Debiab 8 auf Debian 9 zum Beispiel.

Bei der neuen Version kannst Du dann die Standard PHP Version ohne Probleme wechseln. Ja.

TheCry · May 1st 2019

Very strange Laurent.

I did give you the version from the panel in the plugin section. There was the vesrion 3.5.0

Now i'd uploaded the plugin again and the error does'nt appear anymore

Thank you

TheCry · May 1st 2019

Hi Laurent,

here is the content of the script

Perl

#!/usr/bin/perl
# i-MSCP LetsEncrypt plugin
#
# @author Laurent Deckercq <l.declercq@nuxwin.com>
# @license i-MSCP License <http://www.i-mscp.net/license-agreement.html>
use strict;
use warnings;
use FindBin;
use lib "$FindBin::Bin/../../../../engine/PerlLib", "$FindBin::Bin/../../../../engine/PerlVendor";
use Class::Autouse qw/ :nostat iMSCP::Database iMSCP::DbTasksProcessor iMSCP::Service /;
use File::Basename;
use iMSCP::Bootstrapper;
use iMSCP::Debug;
use iMSCP::Getopt;
use JSON;
sub getConfig
{
my $db = shift;
my $dbi = $db->getRawDb( );
my $config = $dbi->selectrow_hashref( "SELECT plugin_config FROM plugin WHERE plugin_name = 'LetsEncrypt'" );
!$dbi->errstr or die( $dbi->errstr );
$config or die( "Couldn't find LetsEncrypt plugin configuration in database" );
JSON->new( )->decode( $config->{'plugin_config'} );
}
my $bootstrapper = iMSCP::Bootstrapper->getInstance( );
exit unless $bootstrapper->lock( '/var/lock/imscp-letsencrypt-renew.lock', 'nowait' );
eval {
newDebug( 'letsencrypt-plugin-renew.pl.log' );
iMSCP::Getopt->parseNoDefault( sprintf( 'Usage: perl %s [OPTION]...', basename( $0 ) ).qq {
Process renewal tasks.
OPTIONS:
-d, --debug Enable debug mode.
-v, --verbose Enable verbose mode.},
'debug|d' => \&iMSCP::Getopt::debug,
'verbose|v' => \&iMSCP::Getopt::verbose
);
setVerbose( iMSCP::Getopt->verbose );
iMSCP::Bootstrapper->getInstance( )->boot(
{
config_readonly => 'yes',
norequirements => 'yes'
}
);
iMSCP::Service->getInstance( )->isRunning( 'mysql' ) or exit;
my $db = iMSCP::Database->factory( );
my $qrs = $db->doQuery(
'u', "UPDATE letsencrypt SET letsencrypt_status = ? WHERE letsencrypt_status = ? AND letsencrypt_expires <= ?",
'torenew',
'ok',
( time( )+getConfig($db)->{'renew_before_expiry'} )
);
ref $qrs eq 'HASH' or die( $qrs );
iMSCP::DbTasksProcessor->getInstance( mode => 'backend' )->process( );
};
if ($@) {
error("Couldn't process Let's Encrypt renewal tasks: %s", $@);
exit 1;
}
END { $bootstrapper->unlock( '/var/lock/imscp-letsencrypt-renew.lock' ); }
1;
__END__;

Display More

THe version ist 3.5.0

Posts by TheCry

Auto Upgrade i-MSCP 1.5.3 to Debian 10 Buster

InstanSSH - Jail with PhpSwitcher

Adding new feature to add, deactivate, remove RBL Server List in Admin Level

Adding new feature to add, deactivate, remove RBL Server List in Admin Level

Adding new feature to add, deactivate, remove RBL Server List in Admin Level

SSH mit 2FA (OTP)

ClamAV plugin instalation failure

Nur zur Sicherheit ( Dist upgrade / PHP wechsel )

Let's Encrypt Renew wont work anymore

Let's Encrypt Renew wont work anymore