Why isn spamdyke blocking messages from some blacklisted servers/senders/recipients?
Most likely, the problem is TLS. If the remote server is using TLS to encrypt its transmission and spamdyke doesn’t have access to the certificate (using the “tls-certificate-file” option), spamdyke can’t decrypt the traffic to monitor the entire connection. In that situation, spamdyke will not block the connection if there is any chance it could be allowed. For example, if the remote server should be blocked because its IP address is blacklisted, spamdyke normally won’t reject the connection until it has exhausted every opportuntity to be allowed. If SMTP AUTH is possible, spamdyke must wait to see if the server authenticates. If sender or recipient whitelists are in use, spamdyke must wait to see if any of those whitelists are matched. However, when TLS is in use and spamdyke can’t decrypt the traffic, the SMTP AUTH, the sender and the recipient will all be hidden. spamdyke must allow the connection to continue just in case. Most of the time, when qmail provides TLS for a connection,
Related Questions
- I enabled the IP-in-rDNS filter, so why isn spamdyke blocking connections from servers with rDNS names that contain IP addresses?
- If spamdyke checks IP blacklists before it checks sender whitelists, will whitelisted senders from blacklisted IPs be blocked?
- Is it ok for me to send spam (ie, to send unsolicited messages to large numbers of recipients)?
