Re: [spamdyke-users] Receiving from other Mailservers with StartTLS on port 25 failed

2015-12-17 Thread Arne Metzger via spamdyke-users 
I am not sure if this will give us more informetion, since there are 
only relaylock entries written to maillog and no firther entries from 
spamdyke.


I activated the option and looking forward to capture one of these 
connections.


Am 17.12.2015 um 02:21 schrieb Sam Clippinger via spamdyke-users:
I don't see anything in your config file that looks like a problem. 
 Since it's working for some connections and not others, I'd guess 
it's something about those mailservers -- they're expecting some 
response (or something) that spamdyke isn't sending, so the connection 
stalls.  Can you try enabling the "full-log-option" to capture the 
data from one of these failed connections?


-- Sam Clippinger




On Dec 14, 2015, at 8:29 AM, Arne Metzger > wrote:



Hi Sam,

sorry for the delayed reply.

My config files are attached below. But i can't provide any log file 
data - the only hint i see in /var/log/maillog is an entry 
"relaylock: ..." any nothing more. Spamdyke doesn't seem to notice 
the connection.


# cat /etc/spamdyke5.conf
log-level=verbose
log-target=syslog
dns-level=normal
filter-level=normal
smtp-auth-level=ondemand-encrypted
smtp-auth-command=/var/qmail/bin/smtp_auth /var/qmail/bin/true 
/var/qmail/bin/cmd5checkpw /var/qmail/bin/true

relay-level=normal
tls-certificate-file=/var/qmail/control/servercert.pem
idle-timeout-secs=300
greeting-delay-secs=0
tls-level=smtp
max-recipients=20
policy-url=http://www.shjjv.de/home/spamfilter

reject-empty-rdns
reject-ip-in-cc-rdns
reject-unresolvable-rdns
ip-in-rdns-keyword-blacklist-file=/var/qmail/spamdyke/rdns-keyword-blacklist
ip-in-rdns-keyword-whitelist-file=/var/qmail/spamdyke/rdns-keyword-whitelist

ip-blacklist-file=/var/qmail/spamdyke/ip-blacklist
rdns-blacklist-file=/var/qmail/spamdyke/rdns-blacklist
ip-whitelist-file=/var/qmail/spamdyke/ip-whitelist
rdns-whitelist-file=/var/qmail/spamdyke/rdns-whitelist

dns-blacklist-entry=zen.spamhaus.org 
dns-blacklist-entry=dnsbl.inps.de 
dns-blacklist-entry=ix.dnsbl.manitu.net 
dns-blacklist-entry=bl.spamcannibal.org 
rhs-blacklist-entry=fresh.spameatingmonkey.com 


#dns-whitelist-entry=list.dnswl.org 

header-blacklist-file=/var/qmail/spamdyke/header-blacklist

reject-sender=no-mx
reject-recipient=same-as-sender

sender-whitelist-file=/var/qmail/spamdyke/sender-whitelist
sender-blacklist-file=/var/qmail/spamdyke/sender-blacklist

graylist-dir=/var/qmail/spamdyke/graylist
graylist-level=always-create-dir
graylist-min-secs=300
graylist-max-secs=1814400
qmail-rcpthosts-file=/var/qmail/control/rcpthosts

# cat /etc/spamdyke5_smtps.conf
log-level=verbose
log-target=syslog
dns-level=normal
filter-level=normal
smtp-auth-level=ondemand-encrypted
smtp-auth-command=/var/qmail/bin/smtp_auth /var/qmail/bin/true 
/var/qmail/bin/cmd5checkpw /var/qmail/bin/true

relay-level=normal
tls-certificate-file=/var/qmail/control/servercert.pem
idle-timeout-secs=300
greeting-delay-secs=0
#151117he
tls-level=smtps
tls-certificate-file=/var/qmail/control/servercert.pem
max-recipients=20
policy-url=http://www.shjjv.de/home/spamfilter

reject-empty-rdns
reject-ip-in-cc-rdns
reject-unresolvable-rdns
ip-in-rdns-keyword-blacklist-file=/var/qmail/spamdyke/rdns-keyword-blacklist
ip-in-rdns-keyword-whitelist-file=/var/qmail/spamdyke/rdns-keyword-whitelist

ip-blacklist-file=/var/qmail/spamdyke/ip-blacklist
rdns-blacklist-file=/var/qmail/spamdyke/rdns-blacklist
ip-whitelist-file=/var/qmail/spamdyke/ip-whitelist
rdns-whitelist-file=/var/qmail/spamdyke/rdns-whitelist

dns-blacklist-entry=zen.spamhaus.org 
dns-blacklist-entry=dnsbl.inps.de 
dns-blacklist-entry=ix.dnsbl.manitu.net 
dns-blacklist-entry=bl.spamcannibal.org 
rhs-blacklist-entry=fresh.spameatingmonkey.com 


#dns-whitelist-entry=list.dnswl.org 

header-blacklist-file=/var/qmail/spamdyke/header-blacklist

reject-sender=no-mx
reject-recipient=same-as-sender

sender-whitelist-file=/var/qmail/spamdyke/sender-whitelist
sender-blacklist-file=/var/qmail/spamdyke/sender-blacklist

graylist-dir=/var/qmail/spamdyke/graylist
graylist-level=always-create-dir
graylist-min-secs=300
graylist-max-secs=1814400
qmail-rcpthosts-file=/var/qmail/control/rcpthosts

Best regards,
Arne

Am 25.11.2015 um 02:51 schrieb Sam Clippinger via spamdyke-users:
It's hard to say what the problem might be without more information. 
 Could you post your spamdyke config file?  Also, if you use the 
full-log-dir option, spamdyke will capture everything that happens 
into a log file for each connection, which should show exactly 
what's going on.


-- Sam Clippinger




On Nov 19, 2015, at 2:41 AM, Arne Metzger via spamdyke-users

Re: [spamdyke-users] Receiving from other Mailservers with StartTLS on port 25 failed

2015-12-16 Thread Sam Clippinger via spamdyke-users 
I don't see anything in your config file that looks like a problem.  Since it's 
working for some connections and not others, I'd guess it's something about 
those mailservers -- they're expecting some response (or something) that 
spamdyke isn't sending, so the connection stalls.  Can you try enabling the 
"full-log-option" to capture the data from one of these failed connections?

-- Sam Clippinger




On Dec 14, 2015, at 8:29 AM, Arne Metzger  wrote:

> Hi Sam,
> 
> sorry for the delayed reply.
> 
> My config files are attached below. But i can't provide any log file data - 
> the only hint i see in /var/log/maillog is an entry "relaylock: ..." any 
> nothing more. Spamdyke doesn't seem to notice the connection.
> 
> # cat /etc/spamdyke5.conf
> log-level=verbose
> log-target=syslog
> dns-level=normal
> filter-level=normal
> smtp-auth-level=ondemand-encrypted
> smtp-auth-command=/var/qmail/bin/smtp_auth /var/qmail/bin/true 
> /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
> relay-level=normal
> tls-certificate-file=/var/qmail/control/servercert.pem
> idle-timeout-secs=300
> greeting-delay-secs=0
> tls-level=smtp
> max-recipients=20
> policy-url=http://www.shjjv.de/home/spamfilter
> 
> reject-empty-rdns
> reject-ip-in-cc-rdns
> reject-unresolvable-rdns
> ip-in-rdns-keyword-blacklist-file=/var/qmail/spamdyke/rdns-keyword-blacklist
> ip-in-rdns-keyword-whitelist-file=/var/qmail/spamdyke/rdns-keyword-whitelist
> 
> ip-blacklist-file=/var/qmail/spamdyke/ip-blacklist
> rdns-blacklist-file=/var/qmail/spamdyke/rdns-blacklist
> ip-whitelist-file=/var/qmail/spamdyke/ip-whitelist
> rdns-whitelist-file=/var/qmail/spamdyke/rdns-whitelist
> 
> dns-blacklist-entry=zen.spamhaus.org
> dns-blacklist-entry=dnsbl.inps.de
> dns-blacklist-entry=ix.dnsbl.manitu.net
> dns-blacklist-entry=bl.spamcannibal.org
> rhs-blacklist-entry=fresh.spameatingmonkey.com
> #dns-whitelist-entry=list.dnswl.org
> 
> header-blacklist-file=/var/qmail/spamdyke/header-blacklist
> 
> reject-sender=no-mx
> reject-recipient=same-as-sender
> 
> sender-whitelist-file=/var/qmail/spamdyke/sender-whitelist
> sender-blacklist-file=/var/qmail/spamdyke/sender-blacklist
> 
> graylist-dir=/var/qmail/spamdyke/graylist
> graylist-level=always-create-dir
> graylist-min-secs=300
> graylist-max-secs=1814400
> qmail-rcpthosts-file=/var/qmail/control/rcpthosts
> 
> # cat /etc/spamdyke5_smtps.conf
> log-level=verbose
> log-target=syslog
> dns-level=normal
> filter-level=normal
> smtp-auth-level=ondemand-encrypted
> smtp-auth-command=/var/qmail/bin/smtp_auth /var/qmail/bin/true 
> /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
> relay-level=normal
> tls-certificate-file=/var/qmail/control/servercert.pem
> idle-timeout-secs=300
> greeting-delay-secs=0
> #151117he
> tls-level=smtps
> tls-certificate-file=/var/qmail/control/servercert.pem
> max-recipients=20
> policy-url=http://www.shjjv.de/home/spamfilter
> 
> reject-empty-rdns
> reject-ip-in-cc-rdns
> reject-unresolvable-rdns
> ip-in-rdns-keyword-blacklist-file=/var/qmail/spamdyke/rdns-keyword-blacklist
> ip-in-rdns-keyword-whitelist-file=/var/qmail/spamdyke/rdns-keyword-whitelist
> 
> ip-blacklist-file=/var/qmail/spamdyke/ip-blacklist
> rdns-blacklist-file=/var/qmail/spamdyke/rdns-blacklist
> ip-whitelist-file=/var/qmail/spamdyke/ip-whitelist
> rdns-whitelist-file=/var/qmail/spamdyke/rdns-whitelist
> 
> dns-blacklist-entry=zen.spamhaus.org
> dns-blacklist-entry=dnsbl.inps.de
> dns-blacklist-entry=ix.dnsbl.manitu.net
> dns-blacklist-entry=bl.spamcannibal.org
> rhs-blacklist-entry=fresh.spameatingmonkey.com
> #dns-whitelist-entry=list.dnswl.org
> 
> header-blacklist-file=/var/qmail/spamdyke/header-blacklist
> 
> reject-sender=no-mx
> reject-recipient=same-as-sender
> 
> sender-whitelist-file=/var/qmail/spamdyke/sender-whitelist
> sender-blacklist-file=/var/qmail/spamdyke/sender-blacklist
> 
> graylist-dir=/var/qmail/spamdyke/graylist
> graylist-level=always-create-dir
> graylist-min-secs=300
> graylist-max-secs=1814400
> qmail-rcpthosts-file=/var/qmail/control/rcpthosts
> 
> Best regards,
> Arne
> 
> Am 25.11.2015 um 02:51 schrieb Sam Clippinger via spamdyke-users:
>> It's hard to say what the problem might be without more information.  Could 
>> you post your spamdyke config file?  Also, if you use the full-log-dir 
>> option, spamdyke will capture everything that happens into a log file for 
>> each connection, which should show exactly what's going on.
>> 
>> -- Sam Clippinger
>> 
>> 
>> 
>> 
>> On Nov 19, 2015, at 2:41 AM, Arne Metzger via spamdyke-users 
>>  wrote:
>> 
>>> Hi,
>>> 
>>> i am using tls-level = smtp for standard smtp connections (for smtps on 
>>> port 465 i use a seperate configugartion file with tls-level = smtps)
>>> 
>>> Some mails from specific mailservers were not handled by spamdyke, there 
>>> was just an relaylock entry in maillog, nothing more.
>>> 
>>> My hosters support staff also tried to send mail with StartTLS on port 25 
>>> and got the same

Re: [spamdyke-users] Receiving from other Mailservers with StartTLS on port 25 failed

2015-11-24 Thread Sam Clippinger via spamdyke-users 
It's hard to say what the problem might be without more information.  Could you 
post your spamdyke config file?  Also, if you use the full-log-dir option, 
spamdyke will capture everything that happens into a log file for each 
connection, which should show exactly what's going on.

-- Sam Clippinger




On Nov 19, 2015, at 2:41 AM, Arne Metzger via spamdyke-users 
 wrote:

> Hi,
> 
> i am using tls-level = smtp for standard smtp connections (for smtps on port 
> 465 i use a seperate configugartion file with tls-level = smtps)
> 
> Some mails from specific mailservers were not handled by spamdyke, there was 
> just an relaylock entry in maillog, nothing more.
> 
> My hosters support staff also tried to send mail with StartTLS on port 25 and 
> got the same result: relaylock entry and nothing more.
> 
> Spamdyke seems not to offer StartTLS on port 25, thus delivering fails and 
> the sending server does not try to deliver without encryption. So the email 
> ist not delivered at all.
> 
> Has anyone heard about that? Any hints? Or more information needed?
> Using spamdyke 5.0.1 on ubuntu 14.04
> 
> Best regards,
> Arne
> ___
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users

___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users