[...]<SNIP> >Now, from here, I can conenct to your Web home page. I can also >connect to >your SMTP server, but with a long delay: [...] >THis is a test of my ability to send a message from an >offsite >location to the test user on the mail server. Kory -- see if >it >shows up.
The message is not present in ~home/lrpqmail/Maildir/new
[...]
/var/log/qmail/qmail/current contains:
[...]
2003-12-26 09:04:08.402813500 starting delivery 40: msg 10039 to remote [EMAIL PROTECTED]
2003-12-26 09:04:08.402826500 status: local 0/10 remote 1/20
2003-12-26 09:04:08.819743500 delivery 40: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
OK. The problem here is that qmail does not know that mail to [EMAIL PROTECTED] is mail for local delivery, so it tries to relay it to I can't-guess-where (can that host resolve kroffts.com?). This is, no doubt, a side effect of moving from kroffts.com to kroffts.dmz (or whatever you changed to) on the LAN.
I don't know how to fix this in qmail. In exim (the MTA I use), there is a config file called "local-host-names" that contains all the variants of the FQN that exim should treat as for local (on-host) delivery. qmail probably has something similar; you need to add "kroffts.com" to the list.
[...]
he problem down, you need to do some more tests. > >First, can the mail server resolve various types of FQNs? Examples >would be > >its own FQN yes, but...
>a LAN client's FQN
yes, but both names are in the local /etc/hosts file so it probably is not using dns. (Qmail does not use the hosts file)
Good point. Try the "host" command. [...]
I fixed the resolv.conf. I then ran host on the dmz machine with the following results.
# host 192.168.1.1 1.1.168.192.IN-ADDR.ARPA domain name pointer coventry.kroffts.home
kroffts_web: -root- # host 192.168.1.5 Host not found.
kroffts_web: -root- # host 192.168.1.254 254.1.168.192.IN-ADDR.ARPA domain name pointer markii.kroffts.home
kroffts_web: -root- # host 192.168.10.1 Host not found, try again.
I think I asked this last time ... does the config file for tinydns have an entry for 192.168.10.1? Or for 192.168.1.5? Last time, it didn't (in what you posted):
=markii.kroffts.home:192.168.1.254
=coventry.kroffts.home:192.168.1.1From the results above, it looks like tinydns is working just fine ... it resolves what it knows about ... now it needs actual entries for the other hosts you want it to resolve.
It can resolve other machines but not itself. Should it be able to? I would think it should and that this is a big part of the problem.
Actually, resolving itself or not should not matter in the immediate context ... except insofar as it indicates other, more general DNS problems.
[remainder deleted]
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
