Hi, Hector,
> For the umpteenth time, not everyone need 4000 domains. Most of the
> domains that will or may utilize it, simply don't need this scale.
I'm not sure you get the point that the others are trying to make. While this
*may* scale for small domains (a big maybe), it won't scale for la
On 4/15/2015 6:11 PM, Murray S. Kucherawy wrote:
Also, if one were to interpret the Pareto Principle correctly, it actually
favors the idea that the only things we should consider are the ones the
large operators are willing to adopt, which means it's abundantly clear
that registration protocols
On 4/15/2015 4:39 PM, Scott Kitterman wrote:
For the umpteenth time, the issue isn't managing a DNS zone. That's the easy
part. The hard part is knowing what to put in it.
Right. I never said it was hard problem. This didn't stop the large
domain with SPF in adding INCLUDE and still have a
On Apr 15, 2015, at 3:11 PM, Murray S. Kucherawy wrote:
> On Wed, Apr 15, 2015 at 1:39 PM, Scott Kitterman wrote:
>> For the umpteenth time, the issue isn't managing a DNS zone. That's the easy
>> part. The hard part is knowing what to put in it. Many companies, not even
>> the really big on
On Wed, Apr 15, 2015 at 1:39 PM, Scott Kitterman
wrote:
> For the umpteenth time, the issue isn't managing a DNS zone. That's the
> easy
> part. The hard part is knowing what to put in it. Many companies, not
> even
> the really big ones, have thousands of domains. Go publish SPF, DKIM key,
>
> For the umpteenth time, the issue isn't managing a DNS zone. That's the easy
> part. The hard part is knowing what to put in it. Many companies, not even
> the really big ones, have thousands of domains. Go publish SPF, DKIM key,
> and
> DMARC records for 4,000 domains and then tell me it
On Wednesday, April 15, 2015 02:41:36 PM Hector Santos wrote:
> On 4/15/2015 2:08 PM, Murray S. Kucherawy wrote:
> > On Tue, Apr 14, 2015 at 3:41 PM, Terry Zink
> >
> > wrote:
> >> 1. For Hotmail, every mailing list that our users are signed up for would
> >> result in a new DNS entry. How do we
> For example,
> the MS Security Bulletins it has message ADID and SDID values such as:
> DKIM-Signature: d=email.microsoftemail.com
> From: e-mail.microsoft.com
> That is a third party. All you need to do is add a ATPS DNS TXT record:
> base64(sha1("email.microsoftemail.com")._atps
On 4/15/2015 2:08 PM, Murray S. Kucherawy wrote:
On Tue, Apr 14, 2015 at 3:41 PM, Terry Zink
wrote:
1. For Hotmail, every mailing list that our users are signed up for would
result in a new DNS entry. How do we manage the lifecycle around that?
Should we automate its addition? Should we automa
On Tue, Apr 14, 2015 at 3:41 PM, Terry Zink
wrote:
> 1. For Hotmail, every mailing list that our users are signed up for would
> result in a new DNS entry. How do we manage the lifecycle around that?
> Should we automate its addition? Should we automate its removal? Do we
> delay email before the
Hi Terry,
I understand your point. Just consider, Microsoft still has its DNS
TXT record for its original Caller ID for Email Protocol (CEP), the
original clone of SPF that eventually became Sender-ID:
D:\Users\Administrator>lmap _ep.hotmail.com
Server: ns.santronics.com
Address: 208
11 matches
Mail list logo
