I have verify = header_sender in my config. No callout verification.
This email however fails sender verification with "No valid sender found in any header". (had to disable sender verification for it to come through) Whats the problem? Is it the linebreak in the From: that should have been soaked up by the MIME parser? The log file seem to identify the From: line correctly by putting a F in front of it, but still it seems it thinks it "invalid" for some reason. Return-path: <bounces+20765315-912c-sebastian=sebbe...@em5912.lab.teledynevisionsolutions .com> Envelope-to: [email protected] Delivery-date: Wed, 01 Jan 2025 00:49:59 +0100 Received: from localhost ([127.0.0.1] helo=sebastian-desktop) by sebbe.eu with esmtp (Exim 4_94_RC0-31-83e8da8c0-XX) (envelope-from <bounces+20765315-912c-sebastian=sebbe...@em5912.lab.teledynevisionsolutions .com>) id 1tSlzr-006bhl-77 for [email protected]; Wed, 01 Jan 2025 00:49:59 +0100 Received: from o1.b2c.flir.com ([149.72.28.138]) by sebbe.eu with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4_94_RC0-31-83e8da8c0-XX) (envelope-from <bounces+20765315-912c-sebastian=sebbe...@em5912.lab.teledynevisionsolutions .com>) id 1tSlzq-006bhg-PP for [email protected]; Wed, 01 Jan 2025 00:49:59 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lab.teledynevisionsolutions.com; h=content-type:from:mime-version:subject:to:cc:content-type:from: subject:to; s=s1; bh=5D0fvbIJLYl0b1GVIsns/M6E4JF7hvbsDR3m5h4DfxE=; b=N+yCOwFyqMHl9r4J0LwFd8wpM9ilwTnmhI4COaz3DGuLouMuEHCgwaxiH6g6f5J4Gynl DOqUHXRpfdPKUkv4JYpFd3JeNwgYuZd+b9ys7ssHVBXdi1dmyiynB99jWOYIJMT/IU8RpN pnFtcbGjnERwDHoiGFowgO1wEXWpg/5Fb4DANiDjDllkl+GWItHZByYKvUaASpkXfgNoK1 UZaZ1zgCYcLlGACo6TDjDac1QFHCvj/DO9HRqm++Fh2T/gdiiHSZzDbe7n8abhOvsuAQCc +F+zB2w0eKbrDP5kJd8PycO4F5niMo95J6edLZiYtYXSZizaOY4V2EwNEfLsAQiQ== Received: by recvd-5c8ccdbd88-5bpn7 with SMTP id recvd-5c8ccdbd88-5bpn7-1-67748324-3 2024-12-31 23:49:56.221587109 +0000 UTC m=+4069601.932234929 Received: from MjA3NjUzMTU (unknown) by geopod-ismtpd-canary-0 (SG) with HTTP id TszMZ2pLQ-WFSDxxVFc5KQ Tue, 31 Dec 2024 23:49:56.120 +0000 (UTC) Content-Type: multipart/alternative; boundary=27320206c8840e846278b874c65c2448165c8d10994ba152adf3558ebaa9 From: Teledyne Digital Platform No Reply <[email protected]> Mime-Version: 1.0 Message-ID: <TszMZ2pLQ-WFSDxxVFc5KQ@geopod-ismtpd-canary-0> X-SG-EID: =?us-ascii?Q?u001=2E5PUpBYdrsvGWCKCLSDngIkzn=2FZqCu3QAjoaqqrLA71YgTwf3Vl7L6V hcd?= =?us-ascii?Q?hRwY+nbkwJMvLAAKRxEOY3oeYn8YzsCqSzG5rll?= =?us-ascii?Q?Q0o4JkZd=2FxX8KEvlM7WJ=2FOW85klZOt7N+cL8jlM?= =?us-ascii?Q?segAMbyUq1TRENC+GuKFgZJiLxKrS4gZcq3uAro?= =?us-ascii?Q?YdMRMl5kuk8mb4YTVTKCZ0s44U4Yuru+VS6=2F6bJ?= =?us-ascii?Q?oNSUGLhbtoONlijh7QMKWnT7bkA9DzzqTcpSeyf?= =?us-ascii?Q?8Af0V17j908bz6vBgHCqqrgBElXES=2F5oAiT0OGi?= =?us-ascii?Q?41BPrjKQ=3D?= X-SG-ID: =?us-ascii?Q?u001=2ESdBcvi+Evd=2FbQef8eZF3BpTL9BgbK5wfSJMJGMsmprDsPyUTnMagHR Cjb?= =?us-ascii?Q?=2F65GublzlB3Y9=2FIo7H7XbkQNu1Qvk3nCCMKjrwU?= =?us-ascii?Q?pfAlWFW+HxTMjVp0dbXOz6VR7W8bqc37uXYY+8v?= =?us-ascii?Q?wm08lDJlM5kWbIr8uEkYO1LG2hrcs35qIYH4=3D?= To: [email protected] X-Entity-ID: u001.PDYv5yECiih2bP1dUnuC8Q== X-Trusted-Domain: fail X-DNS-Whitelist: fail X-SPF-Signature: pass (sebbe.eu: domain of em5912.lab.teledynevisionsolutions.com designates 149.72.28.138 as permitted sender) X-DKIM-Signature: pass (address=bounces+20765315-912c-sebastian=sebbe...@em5912.lab.teledynevisions olutions.com domain=lab.teledynevisionsolutions.com - signature is good) Keywords: =?UTF-8?Q?=E2=9C=94=EF=B8=8F SPF-signaturen =C3=A4r giltig,=E2=9C=94=EF=B8=8F DKIM-signaturen =C3=A4r giltig,=E2=9E=96 Ok=C3=A4nd dom=C3=A4n?= X-Priority: 3 X-Encryption-Target: internal Date: Wed, 01 Jan 2025 00:49:59 +0100 Subject: Your One-Time-Passcode -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## [email protected] ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
