12.05 update causing exim syntax errors

This forum is only for reproducible bugs with csf and lfd (i.e. not iptables problems, lack of understanding how to use a feature, etc). Posts must be accompanied with full technical details of the problem and how it can be recreated. Any posts not adhering to this, or not considered bugs, will be moved to the General Discussion (csf) forum.
4 posts Page 1 of 1
cloudseeder
Junior Member
Posts: 10
Joined: 04 Feb 2014, 01:17


After the 12.05 update my lfd log is full of exim syntax errors:

Aug 10 08:17:20 vpc5 lfd[2111376]: Exim syntax errors from

resulting in my ingress mail servers to be blocked.

I see this in the changelog:

Added new regex for LF_EXIMSYNTAX


I whitelisted my ingress servers to get mail flowing again but any help to fix the issue would be appreciated.
ForumAdmin
Moderator
Posts: 1387
Joined: 01 Oct 2008, 09:24


Upgrade to 12.06. We reverted the change due to the chance of false-positives for mail servers without correct DNS lookups.
cloudseeder
Junior Member
Posts: 10
Joined: 04 Feb 2014, 01:17


Found it. This must be a new rule:

if (($config{LF_EXIMSYNTAX}) and ($globlogs{SMTPAUTH_LOG}{$lgfile}) and ($line =~ /^\S+\s+\S+\s+(\[\d+\] )?no host name found for IP address (\S+)/)) {

My ingress mail servers are running on AWS and connect to the servers running CSF/LFD using private IP addresses without in-addr (intentional) mapping.

What should we do to correctly fix this issue?
Sarah
Moderator
Posts: 793
Joined: 09 Dec 2006, 22:49


As you've already been told, this issue was fixed in the latest version, so you should upgrade.
4 posts Page 1 of 1