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-user
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 enab
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
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 Clippin
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
