> I know this is a month and a half from the original post, and probably the
> original poster has long forgotten it, but have you tried it with 1000
> characters?
>

If I remember correctly, I ran into trouble with
the (common) SPF checkers. It's usually more
about complexity than actual length (again IIRC)
though.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

"Ace Fekay [MVP]" <PleaseAskMe@SomeDomain.com> wrote in message
news:uV4rBFkZGHA.4424@TK2MSFTNGP05.phx.gbl...
> In news:OnRS6cVZGHA.4248@TK2MSFTNGP05.phx.gbl,
> Herb Martin <news@LearnQuick.com> stated, which I commented on below:
>
>> Maybe I can .
>>
>> If you write a TXT record (for SPF etc) that is too long
>> (and I forget the actual limit but generally make it fit
>> in the dialog width and you are ok) then you WILL get
>> truncated behavior -- if not in the console itself, in the
>> return value to client requests.
>>
>> IF HOWEVER you (artificially) use your own line
>> breaks it seems to work for most all purposes.
>>
>> There are also absolute limits beyond which at least
>> some clients and SPF processing software (that is
>> common) will blow up on your records.
>>
>> The following (rather long) record works -- it is
>> LITERALLY 5 lines as shown:
>>
>> v=spf1 ip4:64.202.167.0/24 ip4:64.202.189.0/24
>> ip4:64.202.166.0/24 ip4:64.202.165.0/24 ip4:64.202.163.0/24
>> ip4:68.178.144.60/31 include:in.spf.secureserver.net
>> include:spf.learnquick.com include:deleted.com
>> include:ak.learnquick.com ip4:68.178.144.167 -all
>
> I checked your txt record. But didn't count the characters. Was that more
> than 512 bytes?
>
> I know this is a month and a half from the original post, and probably the
> original poster has long forgotten it, but have you tried it with 1000
> characters?
>
> Ace
>