On Tue, Sep 06, 2005 at 10:43:24AM +0200, Alex van den Bogaerdt wrote:
On Tue, Sep 06, 2005 at 02:05:22AM -0600, Commerco WebMaster wrote:
If I may interject. In your example, it seems like there are several
IP addresses tied to one system that is doing SMTP services. No problem.
Indeed.
If each interface sends a HELO with the reverse of the IP for its
interface and that is in turn checkable via a DNS lookup, I'm really
not sure what the problem would be.
The problem is that RFC2821 explicitly forbids this. The parameter
for EHLO _MUST_ be the primary name.
If this is the case, I would think that there should be no problem in
doing a HELO check. If this is not the case and all of the IPs use
the HELO jupiter.example.org, then perhaps the SPF record could be
checked to confirm the IP is valid for the variations of Jupiter (in
other words, checking for TXT records for each of the variations and
making note of the IPs that Jupiter could also be in its TXT record).
Indeed, an SPF record does help here.
don't understand.
the spf record for example.org will be in the example.org zone file.
the ptr for an ip would be under different administrative control.
if all I need is a domain to claim that I can send from an ip ???
or do I need an spf record on 1.0.0.10.in-addr.arpa (or whatever) ?
Regards,
Paddy
--
Perl 6 will give you the big knob. -- Larry Wall
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com