The final Received header (ie, the first one) is the time at which the message reached the gmail account mailbox. It looks like we did take 18s for that, which is slower than normal.
Delays to the clients are interesting and complicated, I do imagine that "refresh" for what that's worth is supposed to poll the mailbox directly... especially mobile clients can have various delays on purpose, as notifications and wakeups get coalesced and delayed to reduce the number of wakeups of the device and the radio in order to reduce power usage. If you have the app open, however, it should be pretty short, assuming you have good connectivity. The example in the web page from 2020 is an actual delay in delivery, no real way to know now why that delay occurred. We do sometimes explicitly take longer to deliver messages depending on their content, and sometimes our systems are just busy. We do monitor our delivery pipeline and have internal objectives for delivery performance, like I'm sure everyone else does. Generally speaking, there is no expected performance difference between forwarded email and regular email. Brandon On Mon, Oct 11, 2021 at 6:02 PM Jarland Donnell via mailop < mailop@mailop.org> wrote: > This is a pretty weird one to dive into, but I'd like to hear if others > experience the same. I hate email forwarding, but I'm going to pretend > for a moment that I don't. > > My customers often complain of Gmail being slow to deliver forwarded > email to them, despite Google receiving the email from us rarely more > than 5 seconds after we initially receive it. I can confirm it. In one > case I actually confirmed it in the headers and documented it: > https://mxroute.com/delayed-delivery-to-gmail/ > > In a more recent attempt just today, I confirmed it yet again but > without the gap in time in the headers. I could refresh Gmail on mobile > and desktop, no email. Several minutes after Google had accepted it, > they delivered it to the inbox. The headers would show timestamps > indicating that they had received it exactly when they said they did in > my logs: > > Delivered-To: jarl...@gmail.com > Received: by 2002:a05:6a11:200d:0:0:0:0 with SMTP id nf13csp6279777pxb; > Mon, 11 Oct 2021 17:37:58 -0700 (PDT) > X-Google-Smtp-Source: > > ABdhPJxYCryvkSRT8bYyyUYJEeVFiB83XGUWuuW47EAOVwsIJGTkwnD0m7VAiRDiBk6Zo7MVMrhh > X-Received: by 2002:aca:3bd7:: with SMTP id > i206mr1514327oia.166.1633999078456; > Mon, 11 Oct 2021 17:37:58 -0700 (PDT) > > Some of my customers are getting a bit belligerent over it, and it seems > quite obvious to me to say "There is nothing that I can do about this." > That doesn't stop them from demanding it though, it surely must be "my > problem." So I'd like to get the opinion of other experts. Do you > experience this? Is there some magic detail that influences this that > everyone is aware of but me? > > <3 > > Jarland > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
