At 14:49 12-12-2008, Bill(_dot_)Oxley(_at_)cox(_dot_)com wrote:
One can set an -x flag to capture the original outbound border
sending IP address and that information is certainly available to
the MUA but I dont think this document is the place to discuss what
to do with that information within the MUA
Agreed.
At 14:51 12-12-2008, Douglas Otis wrote:
No, iprev would not be a good solution. The reverse IP address space
is poorly maintained which causes resource limited performance to be
reduced by an order of magnitude while waiting for the timeouts.
According to Section 6.2 of the draft, you can get the client IP
address for iprev method.
There are temporal lists that are kept current to the minute. If a
compromised system is involved, the only relevant identifier will be
its IP address.
My use of "out of date" was wrong. What I meant was that the current
information isn't always relevant as the IP address may have been
reassigned by the time the message reaches the MUA.
I'm not advocating that MUAs should use IP addresses to determine
reputation. Let's not get into a discussion about whether that
should be done or not as we already had that discussion.
Regards,
-sm
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html