I suggest all using the CNAME capability to avoid to overload the TXT record at the root, which will create some issues with your SPF. Suddenly the TXT query does not fit in a single DNS packet....
On Thu, Jul 9, 2015 at 8:57 PM, Gil Bahat <g...@magisto.com> wrote: > Much appreciated, +1. > > Registration: > The GWT auth system has capability for delegated access, which other > postmaster consoles (SNDS/mail.ru/yandex) don't implement. activating > that would make it very easy to share this data with our ESP. Another thing > you to consider is to connect that with Google apps for domains, for quick > signup. For us it was a swift signup. > > Stream control: > One thing I note is that it will seemingly happily mix Envelope and From > senders. we have 4 major mail streams (Transactional, marketing, corporate, > support) and when I specify 'magisto.com' (from address) I will get all 4 > streams. when I specify 'ntdc.magisto.com' I will get only transactional > (our transactional envelope). It would be great if we could separate the > streams somehow. they all use different 'from' senders. > It will also be good to clarify whether the IP reputation refers to our > own traffic segment within a shared IP or the reputation of the shared IP > for all senders using it. > > Researching the data: > feature-wise I would rank it much better than SNDS but far behind > mail.ru/yandex.ru consoles. the feature we'd like to see the most is the > ability to partition by identifiers (list_id for yandex / > x-Postmaster-MsgType for mail.ru) or by sender, both of which exist in > the other consoles. If abuse of the data is of concern you may want to > limit 'higher resolution' to accounts in good standing. > > also significantly appreciated are encryption and auth stats - we've been > wanting to clear our mail streams from unencrypted senders and to deploy a > p=reject DMARC record, this helps a lot and I hope other consoles follow > suit. > > All in all this makes a great addition to our toolset and we'll definitely > make use and recommend it. > > Gil Bahat, > DevOps/Postmaster, > Magisto Ltd. > > On Fri, Jul 10, 2015 at 3:12 AM, Brandon Long <bl...@google.com> wrote: > >> We announced our new postmaster tools today. These are targeted at >> higher volume "good" senders, and give you a bunch of high level stats on >> the mail from your domain that we're seeing. If you don't have access, >> your mail is either too spammy or you don't send enough of it. >> >> Unfortunately, it re-uses the webmaster tools domain ownership stuff, so >> it's not as easy as say receiving email for postmaster@ your domain... >> you need to be able to muck with DNS. And it's a separate DNS entry for >> every user, so I don't know if you want to share a single new gmail login >> or something to avoid that or if you want to all sign up at once so you can >> make only a single DNS change with all of them... >> >> And, apparently we don't publish how much volume you need to send to >> qualify and won't see whether your domain qualifies until you verify, so >> sorry if you go through all that trouble and then don't get anything (my >> personal domain doesn't qualify, for example). >> >> Anyways, welcome feedback on the tool and what we can do to improve it, >> I'll be happy to pass it along. Even more "Arghs" about the annoyances >> I've already outlined ;) (I gave them that feedback already, but perhaps >> more will help) >> >> blog post: >> http://gmailblog.blogspot.com/2015/07/the-mail-you-want-not-spam-you-dont.html >> tool: https://gmail.com/postmaster/ >> >> Brandon >> >> _______________________________________________ >> mailop mailing list >> mailop@mailop.org >> http://chilli.nosignal.org/mailman/listinfo/mailop >> >> > > _______________________________________________ > mailop mailing list > mailop@mailop.org > http://chilli.nosignal.org/mailman/listinfo/mailop > >
_______________________________________________ mailop mailing list mailop@mailop.org http://chilli.nosignal.org/mailman/listinfo/mailop
