spamdyke localhost datenbankspezifisch ALL PRIVILEGES Ja
mysql -uspamdyke -pspamdyke spamdyke
smtp stream tcp nowait.1000 root /var/qmail/bin/tcp-env tcp-env /usr/bin/env SMTPAUTH=1 SHORTNAMES=1 END=1 /var/qmail/bin/relaylock /usr/local/bin/spamdyke -f /etc/spamdyke/spamdyke.conf /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
Wo steht das? (Fakten Fakten Fakten!)obwohl cron.daily um 0.55 Uhr ausgeführt wird.
Verschiebe es nach /usr/local/bin und rufe es über die crontab auf.Wo kann ich die Zeit festlegen, zu der das Script ausgeführt wird?
Dein Server hat zuletzt irgendwann um 12:30 gebootet, oder?Die Zeit scheint identisch mit den täglichen Status-Mails, die kommen genau um 12.30 Uhr.
make install
cp spamdyke /usr/local/bin/spamdyke-4.0.10
cp: cannot create regular file `/usr/local/bin/spamdyke-4.0.10': Text file busy
#für das Plesk-Addon von Haggybear:
log-level=info
local-domains-file=/var/qmail/control/rcpthosts
tls-certificate-file=/var/qmail/control/servercert.pem
#Copy&Paste from xinetd-conf
smtp-auth-command=/var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /bin/true
smtp-auth-level=ondemand-encrypted
#wichtiger Timeout:
idle-timeout-secs=300
graylist-level=always-create-dir
graylist-dir=/var/qmail/spamdyke/greylist
#300 Sek. = 5 Min.
graylist-min-secs=120
#1814400 Sek. = 3 Wochen
graylist-max-secs=1814400
sender-blacklist-file=/var/qmail/spamdyke/blacklist_senders
recipient-blacklist-file=/var/qmail/spamdyke/blacklist_recipients
ip-in-rdns-keyword-blacklist-file=/var/qmail/spamdyke/blacklist_keywords
ip-blacklist-file=/var/qmail/spamdyke/blacklist_ip
rdns-whitelist-file=/var/qmail/spamdyke/whitelist_rdns
ip-whitelist-file=/var/qmail/spamdyke/whitelist_ip
sender-whitelist-file=/var/qmail/spamdyke/whitelist_senders
greeting-delay-secs=5
#ggf. auskommentieren:
config-dir=/var/qmail/spamdyke/conf.d
config-dir=/var/qmail/spamdyke/conf.s
connection-timeout-secs=720
dns-blacklist-entry=ix.dnsbl.manitu.net
dns-blacklist-entry=zen.spamhaus.org
dns-blacklist-entry=list.dsbl.org
dns-blacklist-entry=zombie.dnsbl.sorbs.net
dns-blacklist-entry=dul.dnsbl.sorbs.net
dns-blacklist-entry=bogons.cymru.com
reject-missing-sender-mx
reject-empty-rdns
reject-unresolvable-rdns
reject-ip-in-cc-rdns
#MySQL-Logging:
config-mysql-database=spamdyke
config-mysql-username=spamdyke
config-mysql-password=spamdyke
<?php
/*
Plesk Spamdyke Control Panel (Version see version.php) - GUI for Plesk spamdyke implementation
Copyright (C) [2008] [Matthias Hackbarth / www.haggybear.de]
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty
of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, see <http://www.gnu.org/licenses/>.
*/
error_reporting(1);
define("DB_USR", "admin");
define("DB_PWD", trim(exec ("cat /etc/psa/.psa.shadow")));
define("DB_NAME", "psa");
define("DB_HOST", "localhost");
define("QMAIL_PATH", "/var/qmail/");
define("LOG_FILE","/var/log/mail.info");
define("SPAMDYKE_CONFIG","/etc/spamdyke.conf");
//Only if you want to use the autoupdate function
define("AUTOUPDATE",true);
// define your language file, ex: en; ro; de;
define("LANG", "de");
define("PSA_PATH",trim(exec ("grep PRODUCT_ROOT_D /etc/psa/psa.conf | sed s/^[t]*[A-Z_]*[t]*//"))."/");
define("PSA_VERSION",substr(trim(exec ("cat ".PSA_PATH."version")),0,1));
//Default view - entries per page [25,50,100,200]
define("DEFAULT_PERPAGE",100);
//Logtype file/mysql (mysql only for the patched spamdyke-version from haggybear.de)
define("LOG_TYPE","mysql");
define("PSA_PATH",trim(exec ("grep PRODUCT_ROOT_D /etc/psa/psa.conf | sed s/^[t]*[A-Z_]*[t]*//"))."/");
define("PSA_VERSION",substr(trim(exec ("cat ".PSA_PATH."version")),0,1));
define("PSA_PATH",trim(exec ("grep PRODUCT_ROOT_D /etc/psa/psa.conf | sed s/^[t]*[A-Z_]*[t]*//"))."/");
define("PSA_VERSION",substr(trim(exec ("cat ".PSA_PATH."version")),0,1));
define("PSA_PATH",trim(exec ("grep PRODUCT_ROOT_D /etc/psa/psa.conf | sed s/^[t]*[A-Z_]*[t]*//"))."/");
define("PSA_VERSION",substr(trim(exec ("cat ".PSA_PATH."version")),0,1));
?>
Ok, und hier die korrekte Auflösung:Ok, das Problem hab ich gelöst. EInfach qmail stop... und dann Prozesse gelöscht.
config-mysql-database=spamdyke
Einmal heißt die Datenbank "spamdyke", das andere mal "psa".define("DB_NAME", "psa");
Nee Huschi, das ist schon richtig so. psa ist das DB von Plesk, die das SCP braucht um die Plesk Properties zu lesen!Einmal heißt die Datenbank "spamdyke", das andere mal "psa".
Was davon richtig ist, musst Du entscheiden.
checking for MySQL (for MySQL-Logging support)... yes
checking for MySQL includes (for MySQL-Logging support)...yes
[root@ras-2 ~]# mysql_config --libs
-rdynamic -L/usr/lib/mysql -lmysqlclient -lz -lcrypt -lnsl -lm -lssl -lcrypto
[root@ras-2 src]# cd spamdyke-4.1.0-mysql/
[root@ras-2 spamdyke-4.1.0-mysql]# cd spamdyke/
[root@ras-2 spamdyke]# ./configure
[root@ras-2 spamdyke]# make
gcc -Wall -O2 -funsigned-char -c spamdyke.c
gcc -E -Wall -O2 -funsigned-char configuration.c | gcc -Wall -O2 -funsigned-char -x c -c -o configuration.o -
gcc -Wall -O2 -funsigned-char -c dns.c
gcc -Wall -O2 -funsigned-char -c environment.c
gcc -Wall -O2 -funsigned-char -c usage.c
gcc -Wall -O2 -funsigned-char -c search_fs.c
gcc -Wall -O2 -funsigned-char -c exec.c
gcc -Wall -O2 -funsigned-char -c base64.c
gcc -Wall -O2 -funsigned-char -c tls.c
gcc -Wall -O2 -funsigned-char -c log.c
gcc -Wall -O2 -funsigned-char -c config_test.c
gcc -Wall -O2 -funsigned-char -c md5.c
gcc -Wall -O2 -funsigned-char -c filter.c
gcc -Wall -O2 -funsigned-char -o spamdyke spamdyke.o configuration.o dns.o environment.o usage.o search_fs.o exec.o base64.o tls.o log.o config_test.o md5.o filter.o -lssl -lssl -lmysqlclient
log.o: In function `log_to_mysql':
log.c:(.text+0x29): undefined reference to `mysql_init'
log.c:(.text+0x66): undefined reference to `mysql_real_connect'
log.c:(.text+0x79): undefined reference to `mysql_query'
log.c:(.text+0x8d): undefined reference to `mysql_close'
collect2: ld gab 1 als Ende-Status zurück
make: *** [spamdyke] Fehler 1
Welches OS? Suse??Ohne MySQL funktioniert der Spamdyke inkl. Control-Panel ohne Probleme. Hat es etwas mit der lmysqlclient zu tun?
Welches OS? Suse??
We use cookies and similar technologies to provide the best experience on our website. You can choose which purposes you consent to. Your choice applies across websites using the same consent framework.
Below you can select which purposes you consent to. Purpose 1 is required for basic website functionality.
Cookies, device or similar online identifiers together with other information can be stored or read on your device for the purposes presented to you.
Ads can be shown to you based on the content you are viewing, the app you are using, your approximate location, or your device type.
A profile can be built about you and your interests to show you personalised ads that are relevant to you.
Personalised ads can be shown to you based on a profile about you.
A profile can be built about you and your interests to show you personalised content that is relevant to you.
Personalised content can be shown to you based on a profile about you.
The performance and effectiveness of ads that you see or interact with can be measured.
The performance and effectiveness of content that you see or interact with can be measured.
Market research can be used to learn more about the audiences who visit sites/apps and view ads.
Your data can be used to improve existing systems and software, and to develop new products.
Content can be selected based on limited data, such as the content you are viewing or the device you are using.
Below is a list of all technology vendors that may process your data. You can enable or disable each vendor individually.