-----Original Message-----
From: Rob MacGregor [mailto:rob.macgregor@gmail.com]
Sent: Tuesday, February 09, 2010 2:22 PM
To: spf-help@v2.listbox.com
Subject: ***SPAM*** Re: [spf-help] Over 255 character SPF record with
TinyDNS/djbdns
Importance: Low
On Tue, Feb 9, 2010 at 18:52, <CSingh@lightspeedresearch.com> wrote:
>> I am looking for help with the correct syntax for specifying a longer
>> than 255 characters SPF record in TinyDNS. Here is what I have right
now
>> but it splits the result of the lookup after 127 characters:
> The correct approach is to use the include: tag, as specified in
> http://www.openspf.org/SPF_Record_Syntax. Just ensure you watch the
> number of DNS lookups - there's a limit of 10 and each include will
> use one, A will use 2 and MX will use at least 3.
>
> You should also list the IP addresses first and where possible break
> the A and MX records down - since your current MX and A records are
> covered by the IP ranges listed you can simply remove them.
Thanks for your response but I am not sure if I understood correctly. I
used SPF setup wizard at this location to set it up:
http://old.openspf.org/wizard.html?mydomain=lightspeedaheadnewsletter.co
m
the include: tag syntax appears to be true for BIND but it looks like it
has to be ip4\072IPAddress for TinyDNS.
Splitting the lookup output for records over 127 characters is a tinyDNS
known issue, also referred to here:
http://www.anders.com/projects/sysadmin/djbdnsRecordBuilder/#SPF
SPF employs text records and tinydns silently splits text records larger
than 127 characters leaving the reconstruction to the client DNS
software. Usually this isn't a problem, but if your records are longer
than 127 characters and you don't want to trust arbitrary client DNS
implementations to reconstruct your SPF records, a generic record can be
used instead. Generic records support a maximum of 255 characters so if
your record is longer than that, you should look at TXT records instead
I am still searching for the correct syntax but unsuccessful so far.
Charan
This email is intended only for the named person or entity to which it is addressed and contains valuable business information that is proprietary, privileged, confidential and/or otherwise protected from disclosure. Dissemination, distribution or copying of this email or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this email by mistake, please delete it from your system immediately and notify the sender. Email transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission.
-------------------------------------------
Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
Archives: https://www.listbox.com/member/archive/1020/=now
RSS Feed: https://www.listbox.com/member/archive/rss/1020/
Powered by Listbox: http://www.listbox.com
From: Rob MacGregor [mailto:rob.macgregor@gmail.com]
Sent: Tuesday, February 09, 2010 2:22 PM
To: spf-help@v2.listbox.com
Subject: ***SPAM*** Re: [spf-help] Over 255 character SPF record with
TinyDNS/djbdns
Importance: Low
On Tue, Feb 9, 2010 at 18:52, <CSingh@lightspeedresearch.com> wrote:
>> I am looking for help with the correct syntax for specifying a longer
>> than 255 characters SPF record in TinyDNS. Here is what I have right
now
>> but it splits the result of the lookup after 127 characters:
> The correct approach is to use the include: tag, as specified in
> http://www.openspf.org/SPF_Record_Syntax. Just ensure you watch the
> number of DNS lookups - there's a limit of 10 and each include will
> use one, A will use 2 and MX will use at least 3.
>
> You should also list the IP addresses first and where possible break
> the A and MX records down - since your current MX and A records are
> covered by the IP ranges listed you can simply remove them.
Thanks for your response but I am not sure if I understood correctly. I
used SPF setup wizard at this location to set it up:
http://old.openspf.org/wizard.html?mydomain=lightspeedaheadnewsletter.co
m
the include: tag syntax appears to be true for BIND but it looks like it
has to be ip4\072IPAddress for TinyDNS.
Splitting the lookup output for records over 127 characters is a tinyDNS
known issue, also referred to here:
http://www.anders.com/projects/sysadmin/djbdnsRecordBuilder/#SPF
SPF employs text records and tinydns silently splits text records larger
than 127 characters leaving the reconstruction to the client DNS
software. Usually this isn't a problem, but if your records are longer
than 127 characters and you don't want to trust arbitrary client DNS
implementations to reconstruct your SPF records, a generic record can be
used instead. Generic records support a maximum of 255 characters so if
your record is longer than that, you should look at TXT records instead
I am still searching for the correct syntax but unsuccessful so far.
Charan
This email is intended only for the named person or entity to which it is addressed and contains valuable business information that is proprietary, privileged, confidential and/or otherwise protected from disclosure. Dissemination, distribution or copying of this email or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this email by mistake, please delete it from your system immediately and notify the sender. Email transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission.
-------------------------------------------
Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
Archives: https://www.listbox.com/member/archive/1020/=now
RSS Feed: https://www.listbox.com/member/archive/rss/1020/
Powered by Listbox: http://www.listbox.com