Atomicorp

This is the initial test release for Haggybear's (www.haggybear.de) Plesk control module for Spamdyke.

I wish I could give you a feature list here, but his site is in german and kind of in disarray... much like ART! The button to access spamdyke is viewable at the client and/or domain level.

1) Add the atomic repo
wget -q -O - http://www.atomicorp.com/installers/atomic | sh

2) update the package from atomic-testing

yum install psa-spamdyke

Installed this one yesterday. Installation went fine, but it refuses to work. Upgraded to the latest version (2.1.3)
manually and now it's working. Seems like a great product! Haven't seen any reports yet, but it'll probably take a day or two to get some data... All settings seems to be manageable from within Plesk at least!

OK. Realized the config.inc.php had the wrong maillog. You have to edit this fail and point to your maillog (Plesk/Centos /usr/local/psa/var/log/maillog)

Hmmm... would be interesting to try out the Haggybear mysql edition of Spamdyke. Could give some great logging capabilities...

Hi,

I don't use this product from haggybear, but others. Because I'm German I have translated the german parts for you.

Best,
BruceLee

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

Spamdyke Control Panel

The Spamdyke Control Panel (SCP) is a GUI for the antispam implementation of spamdyke with qmail.

The native spamdyke version from spamdyke.org as well as the patched MySQL variation (from haggybear) are supported.
The MySQL variation is substantially more performant in case of high mail traffic.

By means of the SCP you can view the mail traffic graphically and retrieve various information to each mail.
IP and Mail whois are possible. Besides that you can manage White- and Blacklists.

additional functions are:

* percentage statistics of the mail traffic as well as the blocked mails.
* TOP values view. TOP hour/TOP spammed Mail/TOP spamming IP/country.
* daily report.
* extensive options of filtering the view.
* search function.
* activate/deactivate greylistings.


Additionaly SCP comes with extensive administration options for configuring spamdyke easily and effective.

* greylisting administration inclusive the integration into Plesk for a new domain creation.
* administration of DNSBL lists.
* administration of e-mail reports.
* extensive rights management for the users of SCP.

Urgent notice: right after a new installation it is necessary to administer the correct rights under the rights management immediately!!

-------

Spamdyke Control Panel - Changelog
Version 2.1.3
IP-Whois in statistics and daily report improved.

Version 2.1.2
Global White/Blacklist bug fixed. RDNS-Name country detection and IP-Whois within statistics added.

Version 2.1.1
Plesk 9 Fix for 'Level Up' and wrong view with other installed addons.

Version 2.1
New white/blacklist management. Domain specific lists are possible.

Version 2.0.3
IP search fix within detail-layer.Multi-domain-rights function added to deativate or activate all methods for one domain or all domains for one method.

Version 2.0.2
IP search fix in MySQL version. User view fixed openening settings and filterbar. Directionview in adminview corrected!

Version 2.0.1
Bugfix in TOP-Stat view in File-Version

Version 2.0.0
First public release

-------

Spamdyke Control Panel - Installation

1)
- Change into your Plesk Admin htdocs directory (e.g. /opt/psa/admin/htdocs)
- Make a directory for the Spamdyke Config Panel (e.g. "mkdir spamdyke")
- Set chown of the directory you made above to root:psaadm ("chown root:psaadm spamdyke")
- Set chmod of the directory you made above to 755 ("chmod 755 spamdyke")
- Extract all files of the ZIP into that directory
- Set chown of all files to root:psaadm ("chown -R root:psaadm *")
- Set chmod of all files to 755 ("chmod 755 -R *")
- Set the wrapper to chown root:root ("chown root:root wrapper")
- Set the wrapper to chmod 4755 ("chmod 4755 wrapper")
- Set all *.txt to chmod 777

============================================================================================================
IMPORTANT IF THE SCP DON'T WORK ON PLESK 8.x (WHITE SCREEN), SET ALL FILES TO 775
============================================================================================================

-make your settings in file config.inc.php
-only use LOG_TYPE level "mysql"if you have the pachted spamdyke version with
mysql-logging from haggybear.de installed.

Make sure the Spamdyke is installed and working, don't forget to set the correct path
to the spamdyke.conf

2)
-Login to your Plesk as admin
-Make a new Custom Button with the following settings:

Button label: Just choose a name
Location: Domain administration page
Priority: 100
Background image: choose the dslogo.gif of the ZIP
URL: your directory you made above an the index file (e.g. "/spamdyke/index.php")
Include domain id: yes
Include domain name: yes
Include FTP Login: no
Include FTP password: no
Include client id: yes
Include client's company name: no
Include client's contact name: no
Include client's e-mail: no
Context help tip contents: whatever you want
Open URL in the Control Panel: yes
Visible to all sub-logins: yes (if your clients are allowed to manager their spamdyke)

Thanks A LOT! Now that I know that I have a transalator availble I might have the courage to try the SQL-flavored Spamdyke...

(I can read some german myself, but it takes quite a while and I'm not that up to date on computer terms and expressions in german...)

Tried the Sql-version of Spamdyke from haggybear. Compiled fine, works fine, except for the sql part. As soon as I enable the sql logging the server stops receiving mail. No error message what so ever. Just starts the recieving connection, and then nothing. Really don't know where to look for errors, when there aren't any in the maillog...

Taken a look for MySQL log errors?

have you done all these steps?
-1. DATABASE and USER -2. /etc/spamdyke.conf (this is just a sample) -3. create Files -4. Deactivate Plesk-based-DNSBL
under Plesk>Server>Email>spam protection DNSBL...

-5. Check/add spamdyke to smtp connection:

Best,
BruceLee

Kalimari wrote:Taken a look for MySQL log errors?

I don't find anything interesting in /var/log/mysqld.log... Any other mysql logs to check for?

BruceLee wrote:have you done all these steps?
-1. DATABASE and USER

Code: Select all

CREATE DATABASE spamdyke;
USE spamdyke;
CREATE TABLE `spamdyke_log_table` (
	`id` bigint(7) NOT NULL auto_increment,
	`time` timestamp NOT NULL default CURRENT_TIMESTAMP,
	`reason` varchar(20) character set utf8 NOT NULL,
	`from` varchar(50) character set utf8 NOT NULL,
	`to` varchar(50) character set utf8 NOT NULL,
	`ip` varchar(15) character set utf8 NOT NULL,
	`rdns` varchar(50) character set utf8 NOT NULL,
	`auth` varchar(25) character set utf8 NOT NULL,
	PRIMARY KEY  (`id`),
	KEY `time` (`time`),
	KEY `reason` (`reason`,`from`,`to`,`ip`,`rdns`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8;

#create user under shell:
GRANT ALL ON spamdyke.* TO 'spamdyke'@'localhost' IDENTIFIED BY 'spamdyke';
FLUSH PRIVILEGES;

-2. /etc/spamdyke.conf (this is just a sample)

Code: Select all

 

#Plesk-Addon from 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/qmail/bin/true
smtp-auth-level=ondemand-encrypted

#Timeouts:
idle-timeout-secs=100
graylist-level=always-create-dir
graylist-dir=/var/qmail/spamdyke/greylist
#(300 Sec. = 5 Min.)
graylist-min-secs=300
#1814400 Sec. = 3 Weeks
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

#Blacklists de-/activate:
dns-blacklist-entry=ix.dnsbl.manitu.net
#dns-blacklist-entry=sbl.spamhaus.org
#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

-3. create Files

Code: Select all

mkdir /var/qmail/spamdyke
mkdir /var/qmail/spamdyke/greylist
touch /var/qmail/spamdyke/blacklist_ip 
touch /var/qmail/spamdyke/blacklist_recipients
touch /var/qmail/spamdyke/whitelist_ip
touch /var/qmail/spamdyke/whitelist_senders
touch /var/qmail/spamdyke/blacklist_keywords
touch /var/qmail/spamdyke/blacklist_senders
touch /var/qmail/spamdyke/whitelist_rdns
chown -R qmaild:qmail /var/qmail/spamdyke

-4. Deactivate Plesk-based-DNSBL
under Plesk>Server>Email>spam protection DNSBL...

-5. Check/add spamdyke to smtp connection:

Code: Select all

/etc/inetd.conf:

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.conf /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true

Or under /etc/xinetd.d/smtp_psa (and smtps_psa):

service smtp {
	...
	server          = /var/qmail/bin/tcp-env
	server_args     = -Rt0 /var/qmail/bin/relaylock /usr/local/bin/spamdyke -f /etc/spamdyke.conf /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}

Best,
BruceLee

Well most of it was in place. But I added the DB (checked via phpmyadmin as well), but as soon as I add the sql-commands in the spamdyke.conf it refuses to work. If I uncoment them, it works great... but without sql support of course...

Thanks for the input!

Just a guess......

If it stops working when you add the correct usernames/passwords for the sql bit in the spamdyke conf, then there's a chance that the version of spamdyke being called in smtp_psa is still the old non-sql version of spamdyke. It would also explain the lack of errors in the sql logs.

Same goes for when you add the sql logging in the conf - the normal version of spamdyke probably chokes on them.

So, how about renaming the mysql version of the binary that you compiled to something like spamdykesql just to make absolutely sure you are pointing to the right one?

Like I say -- just a guess at what might be wrong. could be something else entirely.

Faris.

Great tip! Trying right now...



"Stay tuned for the next episode in the marvelous story about a server administrators daily struggle to provide the best service to the best customers..." said in a dark, mysterious voice a la James Earl Jones...

It works!!! Faris for President!

Lots of balloons and champagne to everyone!

yay! I'm glad to be useful.

As for President....I presume you mean of the World, right?

Please note, however, that the full title would be President For Life. It would be run as a Benevolent Dictatorship.

Faris.