Re: [mailop] Gmail deferrals

[Jeffrey Williams via mailop]

Based on past experience, I'd suggest checking Google Postmaster Tools over
the next few days to see if it gives any more clues.  The report visibility
is delayed, hence the mention of over the next few days.
-Jeffrey



On Wed, Jul 3, 2024 at 5:24 PM Jason R Cowart via mailop 
wrote:

> I’m hoping someone from Gmail can reply off list.
>
>
>
> We (Stanford University—stanford.edu) are receiving a large number of
> deferrals when trying to delivery to Gmail.com.  The smtp code returned
> is:
>
>
>
> 421-4.7.28 Gmail has detected an unusual rate of mail originating from
> your SPF
>
>
>
> The best educated guess I can make as to that error is that when our
> Office365 environment last weekend began doing SRS and rewriting the sender
> address on forwarded messages (many users forward their M365 mailbox to a
> personal Gmail address) this was as a spike in mail from our domain,
> although the actual volume of mail should not have changed.
>
>
>
> In any case, the SRS was turned back off yesterday but we are still
> effectively rate limited, with 20-30k messages pending delivery to
> gmail.com.
>
>
>
> The response from the gmail.com help site was that if any mitigation was
> warranted it would take two weeks and that there was no way to reply to
> that “ticket.”
>
>
>
> Thanks,
>
> Jason Cowart
>
> University IT
>
> Stanford University
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop
>


-- 
*Jeffrey Williams, Tech Lead*
*Berkeley IT (bIT)* 
j...@berkeley.edu
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Is Google jumping the gun for SPF / DKIM requirement?

[Jeffrey Williams via mailop]

In past mailop posts, Brandon Long from Google has posted about that.  For
example, on September 12th, 2023:
"And yes, we are continuing to ramp no auth, no entry."

There was also a more recent post on the list with additional details about
their Feb. 1st changes.

Hope this helps,
-Jeffrey

On Wed, Jan 24, 2024 at 9:48 PM Grant Taylor via mailop 
wrote:

> Hi,
>
> I knew that Google was going to start requiring SPF or DKIM (in addition
> to other sender guidelines [1].  But I thought they were starting
> February 1st, per their own sender guidelines.
>
> I saw a bounce from a system (cron job output) trying to send directly
> to gmail.com, no forwarding involved.
>
> <<< 550-5.7.26 This mail has been blocked because the sender is
> unauthenticated.
> <<< 550-5.7.26 Gmail requires all senders to authenticate with
> either SPF or DKIM.
> <<< 550-5.7.26
> <<< 550-5.7.26  Authentication results:
> <<< 550-5.7.26  DKIM = did not pass
> <<< 550-5.7.26  SPF [redacted.example.net] with ip: [192.0.2.1] =
> did not pass
> <<< 550-5.7.26
> <<< 550-5.7.26  For instructions on setting up authentication, go to
> <<< 550 5.7.26
> https://support.google.com/mail/answer/81126#authentication
> d20-20020a05683025d400b006dc5452f468si4641458otu.190 - gsmtp
> 554 5.0.0 Service unavailable
>
> Am I missing something obvious or has Google started implementing this
> new requirement ahead of their published schedule?
>
> The only surprise to me is that this happened ~8 days before the
> published February 1st date.
>
> [1]
>
> https://support.google.com/a/answer/81126#zippy=%2Crequirements-for-all-senders
>
>
>
> --
> Grant. . . .
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop
>


-- 
*Jeffrey Williams, Tech Lead*
*Berkeley IT (bIT)* 
j...@berkeley.edu
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop