spamdyke bekommt MySQL-Support

coda66

Blog Benutzer
spamdyke schreibt nicht in die Datenbank

Hallo Forum,

ich habe das folgende Problem (wie irgendwie schon Mehrere vor mir, aber die Lösungen helfen nicht bei mir):

Spamdyke schreibt nicht in die Datenbank, sondern immer noch in die Verzeichnisse. Ich hab alles nach Anleitung gemacht.

System:
Code:
Debian GNU/Linux 6.0
AMD 64bit
Plesk 10.4.4
Hier die Ausgabe der von ./configure:
Code:
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdint.h... (cached) yes
checking sys/inttypes.h usability... no
checking sys/inttypes.h presence... no
checking for sys/inttypes.h... no
checking for sys/types.h... (cached) yes
checking for stdint.h... (cached) yes
checking for sys/inttypes.h... (cached) no
checking whether time.h and sys/time.h may both be included... yes
checking for int16_t... yes
checking for int32_t... yes
checking for int64_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint64_t... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for struct dirent.d_type... yes
checking whether DT_WHT is declared... yes
checking whether S_IFWHT is declared... no
checking whether INADDR_LOOPBACK is declared... yes
checking whether to include debugging symbols (for gdb)... no
checking for strip... strip spamdyke
checking whether to include excessive debugging output... no
checking whether to include some debugging output... yes
checking whether to include configuration tests... yes
checking if openssl/ssl.h will include without additional include directories... yes
checking for library containing RSA_sign... -lssl
checking for library containing SSL_library_init... none required
checking for OpenSSL libraries (for TLS support)... yes
checking for MySQL (for MySQL-Logging support)... yes
checking for MySQL includes (for MySQL-Logging support)...yes 
checking for library containing inet_aton... none required
checking for library containing bind... none required
checking for library containing inet_ntoa... none required
checking for library containing getopt_long... none required
checking whether anonymous inner functions are supported by default... yes
checking whether struct option is defined in getopt.h... yes
checking whether GCC diagnostic pragma directives are supported... yes
checking whether pid_t is an unsigned int or an unsigned long... unsigned int
checking whether uid_t is an unsigned int or an unsigned long... unsigned int
checking whether gid_t is an unsigned int or an unsigned long... unsigned int
checking whether time_t is an int or a long... long
checking whether int64_ts are supported in a test program... yes
checking whether printf()/scanf() uses %ld for 64-bit integers... yes
checking whether __func__ is available... yes
checking whether socklen_t is available... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
die config.php.inc
Code:
<?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,2));

//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));

//Use whois detection for the daily reports! If false then the RDNS-detection will be used!
define("WHOIS_DETECT",false);

//Show flattr Button in Headline
define("SHOW_FLATTR",true);

//Master-Crypt-Key for Token encryption!
define("CRYPT_KEY",DB_PWD);
//
//
//
?>
und die spamdyke.conf
Code:
#für Spamdyke:
log-level=info

config-mysql-database=xxx
config-mysql-username=xxx
config-mysql-password=xxx

local-domains-file=/var/qmail/control/rcpthosts
tls-certificate-file=/var/qmail/control/servercert.pem

smtp-auth-command=/var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /bin/true
smtp-auth-level=ondemand-encrypted

idle-timeout-secs=100
connection-timeout-secs=720
graylist-level=always-create-dir
graylist-dir=/var/qmail/spamdyke/greylist
graylist-min-secs=300
graylist-max-secs=1814400

sender-blacklist-file=/var/qmail/spamdyke/blacklist_senders
header-blacklist-file=/var/qmail/spamdyke/blacklist_headers

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
recipient-whitelist-file=/var/qmail/spamdyke/whitelist_recipient
sender-whitelist-file=/var/qmail/spamdyke/whitelist_sender
ip-in-rdns-keyword-whitelist-file=/var/qmail/spamdyke/whitelist_ip-in-rdns-keyword
greeting-delay-secs=5

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
Hat jemand einen Tipp was nicht stimmen kann?

Grüße,
Coda
 

coda66

Blog Benutzer
Hallo haggybear,

ja alles stimmt. hab die datenbank noch mal gelöscht, neu aufgesetzt. der Datenbank-User hat alle Rechte.

Meinst du es bringt was, wenn ich die Spamdyke deinstalliere und neu installiere? Falls ja, wie müsste ich es machen?

Gruß
Coda66
 

lnadieba2014

New Member
Spamdyke mit libssl.so

Hallo Zusammen,

Hilfe gesucht.
Ich versuche vergeblich Spamdyke mit mysql-support zum laufen zu bringen.
Bei Eingabe folgende Kommando:

spamdyke -f /etc/spamdyke.conf --config-test /var/qmail/bin/qmail-smtpd

Kommt folgende Fehler:
spamdyke: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory

Ich benutze:
OS: CentOS 6.5 (Final)
/usr/lib64/libssl.so.1.0.1e
Spamdyke-5.0.0-mysql von haggybear. Danke ihm für die Arbeit.

Hilfe. Wie verfahre ich weiter?

Danke für Unterstützung
 

Huschi

Moderator
Staff member
Wie hast Du Deine Spamdyke-Version denn kompiliert?
Kann es sein, dass Du die von einem anderen Server rüber kopiert hast?
Denn wenn Du gar nicht die libssl.so.0.9.8 auf dem Server hast, hätte er beim Kompilieren schon Fehler melden müssen.

huschi.
 

lnadieba2014

New Member
Spamdyke mit libssl.so

huschi,

Nein. Ich habe das SPAMDYKE-MYSQL von haggybear heruntergeladen.
Bei der Installation gab erst Probleme "configure: error: unable to compile without inet_aton()"

Ich konnte aber das Problem lösen, indem ich in Configure den Pfad von libmysqlclient.a geändert.

Danke für die Hilfe
 

Huschi

Moderator
Staff member
Dann stimmt was nicht mit Deinen Paketen. Denn wenn er zur Kompilierzeit die libssl.so.0.9.8 verlinkt, obwohl nur die libssl.so.1.0.1e vorhanden ist, hast Du Versionskonflikte auf der Maschine.

huschi.
 

lnadieba2014

New Member
Spamdyke mit libssl.so

Hallo huschi,

Wie erkenne ich die Versionskonflikte auf der Maschine? bzw. wie kann ich die Versionskonflikte beheben.
Macht es Sinn die Installation erneut zu machen?

Danke für die Unterstützung?
 

Teco

New Member
Hallo huschi,
ich habe folgendes Problem mit Spamdyke 5.0, Plesk 11.0.8, Debian Wheezy und dem Spamdyke Control Panel welches ich auch nach intensivem FAQ und Doku Studium nicht in den Griff bekomme.

Spamdyke: spamdyke 5.0.0+TLS+CONFIGTEST+DEBUG+MYSQL[haggybear.com] (C)2014 Sam Clippinger, samc (at) silence (dot) org

Ich möchte die Header Blacklist nutzen.
Dazu habe ich im Format
From: *cialis* ... entsprechende Liste unter /var/qmail/spamdyke/blacklist_headers mit korrekten Rechten gepflegt.

Leider wird der Inhalt dieser Liste ständig ignoriert und die Mails kommen an (andere Whitelist Faktoren habe ich ausgeschlossen).

Dies wird auch beim Config-Test deutlich, wo das Wort header-blacklist nirgendwo auftaucht.

Code:
spamdyke -f /etc/spamdyke.conf --config-test /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true


WARNING: Running tests as superuser root(0), group root(0). These test results may not be valid if the mail server runs as another user.
SUCCESS(binary-check): File is executable: /usr/local/bin/spamdyke
SUCCESS: /var/qmail/bin/relaylock appears to offer TLS support but spamdyke will intercept and decrypt the TLS traffic so all of its filters can operate.
SUCCESS: /var/qmail/bin/relaylock appears to offer SMTP AUTH support. spamdyke will observe any authentication and trust its response. spamdyke will offer authentication if /var/qmail/bin/relaylock does not.
SUCCESS(ip-blacklist-file): Opened for reading: /var/qmail/spamdyke/blacklist_ip_xx
SUCCESS(ip-in-rdns-keyword-blacklist-file): Opened for reading: /var/qmail/spamdyke/blacklist_keywords_xx
SUCCESS(ip-whitelist-file): Opened for reading: /var/qmail/spamdyke/whitelist_ip_xx
SUCCESS(rdns-blacklist-file): Opened for reading: /var/qmail/spamdyke/blacklist_rdns_xx
SUCCESS(rdns-whitelist-file): Opened for reading: /var/qmail/spamdyke/whitelist_rdns_xx
SUCCESS(recipient-blacklist-file): Opened for reading: /var/qmail/spamdyke/blacklist_recipient_xx
SUCCESS(recipient-whitelist-file): Opened for reading: /var/qmail/spamdyke/whitelist_recipient_xx
SUCCESS(sender-blacklist-file): Opened for reading: /var/qmail/spamdyke/blacklist_senders_xx
SUCCESS(sender-whitelist-file): Opened for reading: /var/qmail/spamdyke/whitelist_senders_xx
SUCCESS(config-file): Opened for reading: /etc/spamdyke.conf
SUCCESS(dns-resolv-conf): Opened for reading: /etc/resolv.conf
SUCCESS(graylist-level): Graylist directory tests succeeded: /var/qmail/spamdyke/greylist
SUCCESS(ip-blacklist-file): Opened for reading: /var/qmail/spamdyke/blacklist_ip
SUCCESS(ip-in-rdns-keyword-blacklist-file): Opened for reading: /var/qmail/spamdyke/blacklist_keywords
SUCCESS(ip-relay-file): Opened for reading: /var/qmail/spamdyke/ip_relay_file
SUCCESS(ip-whitelist-file): Opened for reading: /var/qmail/spamdyke/whitelist_ip
SUCCESS(qmail-rcpthosts-file): Opened for reading: /var/qmail/control/rcpthosts
SUCCESS(rdns-relay-file): Opened for reading: /var/qmail/spamdyke/rnds_relay_file
SUCCESS(rdns-whitelist-file): Opened for reading: /var/qmail/spamdyke/whitelist_rdns
SUCCESS(recipient-blacklist-file): Opened for reading: /var/qmail/spamdyke/blacklist_recipients
SUCCESS(sender-blacklist-file): Opened for reading: /var/qmail/spamdyke/blacklist_senders
SUCCESS(sender-whitelist-file): Opened for reading: /var/qmail/spamdyke/whitelist_senders
SUCCESS(smtp-auth-level): File is executable: /var/qmail/bin/smtp_auth
WARNING(smtp-auth-level): Authentication command is owned by root but not setuid. Some require being setuid root to read system passwords: /var/qmail/bin/smtp_auth
SUCCESS(tls-certificate-file): Opened for reading: /var/qmail/control/servercert.pem
SUCCESS(tls-certificate-file): Certificate and key loaded; SSL/TLS library successfully initialized
SUCCESS(tls-dhparams-file): Opened for reading: /var/qmail/control/dhparam1024.pem
SUCCESS: Tests complete. No errors detected.
In der spamdyke.conf ist der Eintrag
header-blacklist-file=/var/qmail/spamdyke/blacklist_headers
aber definitiv drin!

Wie es aussieht wird die Header Backlist nicht verarbeitet - woran kann das liegen? Selbst ein direkter Parameter Aufruf mit --header-blacklist-file=xxx gelingt nicht.

Ich bitte um Hilfe, bin mit meinem Wissen leider am Ende
 

Huschi

Moderator
Staff member
Es gibt hier Support. Aber eben für die MySQL-Unterstützung von Spamdyke. Wenn eine Basis-Funktion von Spamdyke nicht geht, musst Du Dich an Sam Clippinger wenden.

huschi.
 
Top