RFC 3464 2.3.5? In this case, the message is being forwarded from Google to the domain's onsite server, so that's the server we attempted to forward to.
Brandon On Thu, Feb 23, 2017 at 1:14 PM, Luke Martinez via mailop <mailop@mailop.org > wrote: > Super helpful. Thanks. > > This may be a stupid question, but can you help me understand what > "Remote-MTA" means in this context? I'm a little confused as to how that > works. > > On Thu, Feb 23, 2017 at 2:04 PM, Brandon Long <bl...@google.com> wrote: > >> >> >> On Thu, Feb 23, 2017 at 12:00 PM, Aaron Richton <rich...@nbcs.rutgers.edu >> > wrote: >> >>> On Thu, 23 Feb 2017, Luke Martinez via mailop wrote: >>> >>> Some G Suite domains are returning this response to us long after the >>>> messages are delivered. More of a curiosity than anything else. Wondering >>>> if anyone has seen this behavior before. >>>> >>> [...] >>> >>>> Reporting-MTA: dns; googlemail.com >>>> Received-From-MTA: dns; bounces+2323606-70a0-ccrawford= >>>> spotsylvania.k12.va...@sendmail.joezooapp.com >>>> Arrival-Date: Wed, 15 Feb 2017 05:45:07 -0800 (PST) >>>> X-Original-Message-ID: <EFwvC250TXmBEZae6eaHrw@ismtpd >>>> 0005p1iad1.sendgrid.net> >>>> >>>> Final-Recipient: rfc822; ccrawf...@spotsylvania.k12.va.us >>>> Action: failed >>>> Status: 4.4.2 >>>> Remote-MTA: dns; 205.174.120.102 (205.174.120.102, the server for the >>>> domain.) >>>> Diagnostic-Code: smtp; read error: generic::failed_precondition: read >>>> error (0): error >>>> Last-Attempt-Date: Wed, 22 Feb 2017 09:37:18 -0800 (PST) >>>> >>> [...] >>> >>> It sounds like this is a generic "they didn't talk the protocol I >>> wanted" from the G Suite MTA (which presumably is trying to forward/cc/etc. >>> from b...@google.hosted.us --> onpremises@[205.174.120.102] living >>> under spotsylvania.k12.va.us.) >>> >>> Seeing that a connection to 205.174.120.102:25 smells like a PIX, it's >>> quite likely that Google is getting some awful Ciscoized SMTP, which may >>> indeed not be the protocol they want. >>> >>> If you have available bandwidth to Fix The World, pinging >>> spotsylvania.k12.va.us to check their SMTP logs (especially at any >>> middleboxes in the way) might be enlightening. Or in the event my crystal >>> ball is fully functional today just point them to: >>> >>> https://community.spiceworks.com/how_to/42809-cisco-asa-disa >>> ble-smtp-fixup-in-asdm >> >> >> Yeah, that error from us basically means that the remote server hung up >> while we were waiting for data. >> >> And yeah, they get a bunch of errors every day for that, you could try >> mailing postmas...@spotsylvania.k12.va.us >> >> Brandon >> >> > > > -- > > Luke Martinez > Team Lead | Email Delivery > 520.400.5693 <(520)%20400-5693> > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
