Date: Fri, 19 Sep 2003 03:20:22 GMT From: Mark <admin@asarian-host.net> To: "Greg 'groggy' Lehey" <grog@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: "May be forged"? Message-ID: <200309190320.H8J3KL5M031529@asarian-host.net> References: <200309190044.H8J0IU5M025025@asarian-host.net> <200309190056.H8J0U35M025526@asarian-host.net> <20030919025620.GT37023@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> ----- Original Message -----
> From: "Mark" <admin@asarian-host.net>
> To: <freebsd-questions@freebsd.org>
> Sent: Friday, September 19, 2003 2:44 AM
> Subject: "May be forged"?
>
>>> Thanks to Kris I found the new sendmail. :) But a slight anomaly occurs
>>> in> 8.12.10:
>>>
>>> AUTH=server, relay=my-xp-machine.net [192.168.1.3] (may be forged),
>>> authid=admin
>>>
>>> That is odd; why would it suddenly say "may be forged"?
>>
>> Hmm, this wouldn't, by any chance, have anything to do with Verisign's
>> latest DNS crap, would it? Kinda like a preemptive caution that a "net"
>> domain might be fake?
>
> No, this is the result of a failed reverse DNS lookup or a failed
> consistency check between forward and reverse DNS. Given that the
> address is in the non-routable RFC 1918 range, this is to be expected.
Then why does it not occur in 8.12.9? If I start my 8.12.9 sendmail, it does
NOT say "may be forged". Did something change in-between versions?
Here is why I think it seems related to Verisign somehow:
asarian-host: {root} % nslookup my-xp-machine.net
Name: my-xp-machine.net
Address: 64.94.110.11
Maybe 8.12.10 picks up on the IP-mismatch? But that still does not explain
why my 8.12.9 sendmail does not say "may be forged". And if I change
/etc/hosts to have 192.168.1.3 called "my-xp-machine.ORG", then the error
goes away, in 8.12.10 too!
- Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200309190320.H8J3KL5M031529>