I suddenly got the implication of what you're saying: Given that my primary
issue today is why mail is incorrectly classified to be quarantined, the
certificate issue between the MTA and the quarantine node is not the
problem. The classification happens on the MTA--in this case, in the very
first router:
quarantine:
driver = manualroute
condition = ${if eq{$header_x-gm-spam:}{1}}
transport = remote_smtp
route_data = ${lookup {$domain}lsearch*{/etc/exim/mailfilter_routes}}
no_more
So the question is better asked, "Why is that x-gm-spam header being
inserted?" Which points me back upstream, true?
On Tue, Apr 26, 2022 at 10:48 AM Jeremy Harris via Exim-users <
exim-users@???> wrote:
> On 26/04/2022 16:36, Johnnie W Adams via Exim-users wrote:
> > That's helpful! Let me ask a more focused question: Does this mean my
> > cert/key combo on this node is bad? That's the path I'm going down right
> > now.
>
> It says there's a certs issue between this MTA and your quarantine node.
> That's separate from why it got to this router, probably.
> --
> Cheers,
> Jeremy
>
> --
> ## List details at https://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
>
--
John Adams
Senior Linux/Middleware Administrator | Information Technology Services
+1-501-916-3010 | jxadams@??? |
http://ualr.edu/itservices
*UA Little Rock*
Reminder: IT Services will never ask for your password over the phone or
in an email. Always be suspicious of requests for personal information that
come via email, even from known contacts. For more information or to
report suspicious email, visit IT Security
<
http://ualr.edu/itservices/security/>.
