Please, always have a backup of your original spamdyke.conf file if
you've made special changes to it!!!!
On 3/6/2016 10:18 PM, Eric wrote:
Helmut,
I'm not sure what's in your current spamdyke.conf file, but there are
three different ways to proceed.
1) Remove and reinstall spamdyke.
I'm not sure, but your original spamdyke.conf may be lost when
you remove spamdyke. So, if there's anything special in the conf file
I'd opt for 2). On reinstall the qmail standard conf file
with necessary 5.0.1 updates (below, *b) is installed.
2) Upgrade and run my script (*a).
Please make sure that spamdyke is running correctly and that you
are able to send and receive email.
3) Upgrade and manually change spamdyke.conf (with configuration from
my previous post to the list), or paste the updated spamdyke.conf(*b)
provided in this email.
The conf file below is simply the original qmail version with the
necessary 5.0.1 updates.
(*a)
<fixsd.sh>
#!/bin/sh
sed -i \
-e 's/reject-missing-sender-mx/reject-sender=no-mx/g' \
-e 's/rejection-text-missing-sender-mx/rejection-text-sender-no-mx/g' \
-e
's/reject-identical-sender-recipient/reject-recipient=same-as-sender/g' \
-e
's/rejection-text-identical-sender-recipient/rejection-text-recipient-same-as-sender/g'
\
-e 's/local-domains-file/qmail-rcpthosts-file/g' \
-e 's/local-domains-entry=/#local-domains-entry=(Add these entries to
qmail-rcpthosts-file)/g' \
-e 's/morercpthosts/qmail-morercpthosts-cdb/'g spamdyke.conf
</fixsd.sh>
(*b)
<spamdyke.conf>
#dns-blacklist-entry=zombie.dnsbl.sorbs.net
#dns-blacklist-entry=dul.dnsbl.sorbs.net
#dns-blacklist-entry=bogons.cymru.com
dns-blacklist-entry=zen.spamhaus.org
dns-blacklist-entry=bl.spamcop.net
graylist-dir=/var/spamdyke/graylist
graylist-level=none
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=6
header-blacklist-entry=From:*>,*<*
idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
qmail-rcpthosts-file=/var/qmail/control/rcpthosts
#qmail-rcpthosts-file=/var/qmail/control/qmail-morercpthosts-cdb
log-level=info
max-recipients=50
#policy-url=http://my.policy.explanation.url/
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
reject-empty-rdns
#reject-ip-in-cc-rdns
reject-sender=no-mx
reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem
tls-level=smtp
</spamdyke.conf>
As always, if you run into issues PLEASE let me know.
EricB.
On 3/6/2016 9:39 PM, Helmut Fritz wrote:
Thx Eric. The below helps a lot. Is there a recommended method?
Remove and install anew or upgrade?
-----Original Message-----
From: Eric [mailto:[email protected]]
Sent: Sunday, March 06, 2016 2:49 PM
To: [email protected]
Subject: Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64
Helmut,
Eventually it will be in general release unless you want it there
sooner, it is in the testing tree presently (per previous posts),
though; and I've already implemented 5.0.1-0 on my business
production server. Be mindful that if you're upgrading (NOT A FRESH
INSTALL) spamdyke from the testing tree you'll have to address the
below 7 options in your server's spamdyke.conf file as an upgrade
does not overwrite existing conf file. Without the adjustments below
mail will not be delivered.
1) If the "reject-missing-sender-mx" option is given, it should
be changed to
"reject-sender" with a value of "no-mx".
2) If the "rejection-text-missing-sender-mx" option is given, it
should be
renamed to "rejection-text-sender-no-mx".
3) If the "reject-identical-sender-recipient" option is given, it
should be
changed to "reject-recipient" with a value of "same-as-sender".
4) If the "rejection-text-identical-sender-recipient" option is
given, it should
be renamed to "rejection-text-recipient-same-as-sender".
5) If the option "local-domains-file" is given, it should be
renamed to
"qmail-rcpthosts-file".
6) If the option "local-domains-entry" is given, it should be
removed. Any
domains given with this option should be added to the file given
with
"qmail-rcpthosts-file".
7) If qmail's "morercpthosts" file is provided to spamdyke with the
"qmail-rcpthosts-file" option (formerly "lcoal-domains-file"),
the CDB file
should be provided instead with the "qmail-morercpthosts-cdb"
option.
EricB
On 3/6/2016 2:00 PM, Helmut Fritz wrote:
Will this get rolled into the general rpms/release?
-----Original Message-----
From: Eric [mailto:[email protected]]
Sent: Sunday, March 06, 2016 11:10 AM
To: [email protected]
Subject: Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64
I was a bit hasty in my creation of the rpm's as the old
spamdyke.conf file should be replaced. I'll get on that and have the
rpms up by end of day.
On 3/6/2016 9:55 AM, Eric wrote:
Be mindful that some of the setting in the old spamdyke.conf will mess
with mail delivery.
I had to comment out 2 lines
#local-domains-file=/var/qmail/control/rcpthosts
#reject-missing-sender-mx
Eric
On 3/6/2016 9:32 AM, Eric wrote:
CentOS 6:
rpm -Uvh
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/testing/x86_64/spamd
yke-5.0.1-0.qt.el6.x86_64.rpm
or
# yum --enablerepo=whtc-qmt-testing update If you have White Horse
repos in your yum configuration.
CentOS7:
rpm -Uvh
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/testing/x86_64/spamd
yke-5.0.1-0.qt.el7.x86_64.rpm
or
# yum --enablerepo=whtc-qmt-testing update If you have White Horse
repos in your yum configuration.
---------------------------------------------------------------------
To unsubscribe, e-mail:
[email protected]
For additional commands, e-mail:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
