Better to ask for help / assistance instead of damaging something.
Posts by DrCarsonBeckett
-
-
Das stimmt schon, aber die besagt Blacklist ist eh nicht in der default config dabei.
-
Postscreen macht das "selbe".
Wenn du mal in die Postscreenconfig rein guckst:Siehst du das wie bei polycid-weight ebenfalls die Blacklists abgefragt werden.
Postscreen alleine sollte schon 90% des Spams filtern, was mal ne ordentliche Leistung ist.Whitelisten ist ebenfalls möglich.
-
Sollte mit iptables gehen, dass ist ja soweit dabei (bin ich zu mindestens der Meinung). Google gibt dies zu mindestens bei dem Thema raus.
iptables -A INPUT -p tcp -s Quell-IP-hier --dport 25 -j LOG --log-uid --log-level debugEdit: Gerade gemerkt das es nur die Pakete loggen sollte. Sorry. Wobei ja die user ID gelockt wird, sollte daher vielleicht doch dann klappen.
-
Its like in the link.
Heres a quick overview (step by step)Follow the guy step by step.
PS.: If you like you can remove older i-mscp zips (archives in general) and folders, but thats not really needed.
-
Works like a charm, thank you very much.
-
The thing is I never installed that plugin. Checked but I (obviously in that case) found nothing from that plugin.
-
Hi all,
I got a problem with the latest Monitorix plugin. I tried to install the version 1.1.1.
I installed every lib which is needed, restarted the monitorix service and installed the plugin after that.
The installation works and the activation too but when I try to access the Monitorix page I get this error:
At the same time I get this mail:CodeTo be sure, I removed monitorix completly [apt-get purge monitorix] (removed the /etc/monitorix folder too) and retried it. Same thing.
I took a look at the readme file and at the monitorix page:
http://www.monitorix.org/doc-debian.htmlOf course I checked the wiki page too:
http://wiki.i-mscp.net/doku.php?id=plugins:monitorixSomeone got an idea how to solve it?
I am not sure if I forgot something but atm I dont see the reason for that error.
Edit: I read in another topic that I don't need the CronJob plugin, so I didn't installed that one. Might that be the problem? -
Why don't you simply upload a .htaccess file to the domain? That takes a few seconds and is an easy way to do it.
The mentioned (in your post) method should work too.I saw your .htaccess and it can't work like this if I am correct.
Better is:
-
Freut mich das es geklappt hat. Hatte selbst mal das Problem wie du, deswegen viel mir das wieder ein.