Re: Slate.com and SPF/DKIM to your root domain

[Frank Barton <bartonf () HUSSON EDU>]

We just set up slate with Technolutions, and created a new subdomain
specifically for that purpose.

I know this link has been shared here before, but I would suggest reading
it... https://blogs.msdn.microsoft.com/tzink/2015/03/13/how-to-align-with-
spf
-and-dmarc-for-your-domain-if-you-use-a-lot-of-3rd-parties-to-send-email-as-you/
<https://www.google.com/url?q=https://blogs.msdn.microsoft.com/tzink/2015/03/13/how-to-align-with-spf-and-dmarc-for-your-domain-if-you-use-a-lot-of-3rd-parties-to-send-email-as-you/&sa=D&source=hangouts&ust=1532609872443000&usg=AFQjCNFi4IqSFJCHCisFb9XvoeizAxZr1g>

Frank

On Thu, Aug 30, 2018 at 3:27 PM Graves, Rich <rxgraves () iu edu> wrote:

> I presume you mean http://technolutions.com/ Slate?
>
> Wherever possible, I'd prefer a subdomain like admissions.example.edu or
> marketing.example.edu. This is easier to manage, avoids
> cross-contamination
> of any abuse issues, and delays running into a hard technical limit:
>
> SPF implementations MUST limit the number of mechanisms and modifiers that
> do DNS lookups to at most 10 per SPF check, including any lookups caused by
> the use of the “include” mechanism or the “redirect” modifier. If this
> number is exceeded during a check, a PermError MUST be returned. The
> “include”, “a”, “mx”, “ptr”, and “exists” mechanisms as well as the
> “redirect” modifier do count against this limit. The “all”, “ip4”, and
> “ip6”
> mechanisms do not require DNS lookups and therefore do not count against
> this limit.
>
> Rich Graves <rxgraves () iu edu>
> Principal Security Engineer
> https://OmniSOC.iu.edu/

-- 
Frank Barton, MBA
Security+, ACMT, MCP
IT Systems Administrator
Husson University