Van wrote:
> This is a problem here as well -- my users are from 3 sets of
> public IP addresses
Point 1: SME server isn't designed for clients sending from public IP addresses - usually clients are on a local network with private IP addresses.
Point 2: If there are delays, it's likely because reverse DNS isn't set up correctly for the sending IP addresses. Reverse DNS for those addresses is not under the control of the SME server.
Charlie
Hi Charlie and Co.
Interestingly, I too seem to be having this problem, ever since putting in 6.0. I'm no bunny when it comes to mail systems, but this one is starting to annoy me, hence I'm likely to start missing obvious solutions...
My SME 6.0 is on a DMZ (192.168.3.0/24), and it's authorive dns for the networks that my LAN PC's are on (192.168.2.0/24). This is of course a different network than the local eth0 interface on SME.
The LAN network is listed in SME as being a local network, an I've configured hosts for my internal PC's.
For some reason, SME just won't do a successful reverse lookup, even though it should be authoritive. dig -x 192.168.2.129 fails, although dig -x 192.168.3.1 succeeds.
My LAN PC's are on 192.168.2.0/24, and because SME can't reverse resolve these, it takes time.
I'm not familiar with the tinydns/dnscache software, so haven't made much progress yet.
The same configuration worked fine with SME 5.6 (which was based on bind.)
Anyone have any suggestions?