--
On Sat Aug 23, 2003 at 09:26:34PM -0700, Keith Goettert wrote:
> Ok, lets ask the hard question. If you do a dig linsec.vx do you get an
> answer section? i.e. Does the domain resolve.
No. If it did, I wouldn't be worried. It resolves to all the hosts in my
internal LAN; it's use is only on my LAN and I have an internal DNS server
that handles that "domain" (better than messy /etc/hosts files or using
NIS/LDAP). It isn't a real domain by any means.
The exim server in question is on a different internet connection and has no
access to my LAN, so it can do any lookups for that "domain".
> Also, try
>
> Exim -d-all+acl+lookup+expand (I think that is it.)
>
> It is in spec.txt under -d
Hmmm... looks like it's crapping out on the dnslookup router, so maybe I can
toss something in there to allow for that domain name. It's the dnslookup
router where it's being stopped.
(And yes, you had it right).
Ok, that gives me a few more clues... =) Thanks! Will have to try
tomorrow when I can open my eyes further.
--
MandrakeSoft Security;
http://www.mandrakesecure.net/
Online Security Resource Book;
http://linsec.ca/
"lynx -source
http://linsec.ca/vdanen.asc | gpg --import"
{FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
--
[ Content of type application/pgp-signature deleted ]
--