I did not suggest using an optimizer for two reasons:
1. The optimizer I'm working on (included in libspf2-1.0.6) is not ready
for release yet, and I did not know of another.
2. Todd mentioned that the RoadRunner DNS administration is
decentralized, so there may be race conditions (between the optimizer
refresh and the DNS TTL of the subdomains). The RoadRunner network
engineer could design some script to refresh the SPF record without
having any race conditions.
Do you know of other available optimizers ?
Thanks,
Radu.
Stuart D. Gathman wrote:
On Wed, 16 Mar 2005, Radu Hociung wrote:
If you need to publish the full list of mail sources, I would not do it
as an SPF-resolvable record, but some other way. Perhaps provide a exp=
(explanation message) that points to your own why.html web-page, and put
the list of IPs there.
Why not use an SPF optimizer to convert the high level rr.com record
to a list of raw IPs, and publish that? It could be refreshed daily.
An optimizer will follow includes and evaluate all mechanisms to
form a list of lower level mechanisms (usually ip4).
As mentioned before, another efficient way to list individual ips is with
a host name with multiple a records:
mailsource IN A 1.2.3.4
mailsource IN A 2.3.4.5
mailsource IN A 3.4.5.6
mailsource IN A 4.5.6.7
mailsource IN A 5.6.7.8
But ip4 works better for subnets.