Authentication-Results: [snip].mail.[snip].[snip].com from=someDomain.com; domainkeys=neutral (no sig); from=someDomain.com; dkim=neutral (no sig) Received: from 127.0.0.1 (EHLO smtp1.someOtherDomain.net) (184.108.40.206) by [snip ...] Received: from someOtherDomain.net ([220.127.116.11]) by smtp1.someOtherDomain.net
Email from people who work at a company whose associated domain is "someDomain.com" is forwarded to a mail hosting company,"someOtherDomain.net", via SMTP, and the email gets sent out by someOtherDomain.net to the receipient. The IP addresses (18.104.22.168) and (22.214.171.124) are, of course, obscured here, and they are associated with someOtherDomain.net, not with someDomain.com.
If a header like the one above were received at a company with fairly strict mail filters, such as a major bank, would it typically get trapped or flagged by the filters as suspect, either as potential spam or phishing, or anything else? When dkim = "neutral (no sig) and domainkeys="neutral (no sig)" is that a sign to a strict filter than the email may be from a fly-by-night organization, so to speak?