On 18/11/2021 14:53, Matt Corallo via Exim-users wrote:
>
> Received: from o13.mailer.shopify.com ([149.72.221.62])
> by mail.as397444.net with esmtps TLS1.3 id 1mmjFb-0034Ki-02
> (envelope-from <bounces+11006833-f9b2-vmstfpodc=mattcorallo.com@???>)
> for vmstfpodc@???; Mon, 15 Nov 2021 21:10:54 +0000
>
> Specifically, it seems Spamassassin is looking for something more postfix-esque like
> Received: from o13.mailer.shopify.com (o13.mailer.shopify.com [149.72.221.62])
>
> I haven't dug into any relevant RFCs to see who's fault it really is, but it seems Spamassassin and Exim don't agree on how to communicate validated DNS.
RFC 5321, Section 4.4 has the relevant ABNF. Selected bits:
Time-stamp-line = "Received:" FWS Stamp <CRLF>
Stamp = From-domain By-domain Opt-info [CFWS] ";"
FWS date-time
From-domain = "FROM" FWS Extended-Domain
Extended-Domain = Domain /
( Domain FWS "(" TCP-info ")" ) /
( address-literal FWS "(" TCP-info ")" )
TCP-info = address-literal / ( Domain FWS address-literal )
; Information derived by server from TCP connection
; not client EHLO.
I thinks Exim's line fits that with
TCP-info = [149.72.221.62] ; an address-literal
Domain = o13.mailer.shopify.com
You can define the Received line to suit yourself; it is a option in
the Exim config file.
--
Cheers,
Jeremy
