FYI that the missing domain in the tempfail message should now be fixed
(thanks to Wei)! Please let me know if you are not seeing it.
On Thu, Feb 15, 2024 at 11:50 PM Stefano Bagnara via mailop <
mailop@mailop.org> wrote:
> On Fri, 16 Feb 2024 at 05:02, Evan Burke wrote:
>
>> It sounds like you'
This was caused by a temporary issue reaching the DNS servers. Let me pass
this along to see if it can be turned into a temporary (4xy) error.
On Tue, Feb 27, 2024 at 9:56 PM Marco Moock via mailop
wrote:
> Am Tue, 27 Feb 2024 16:54:31 -0600
> schrieb Jarland Donnell via mailop :
>
> > Is it pla
Thanks for flagging this. Looks like it was because the message had a
temporary error resolving SPF. I'll see if I can improve the behavior here.
On Thu, Feb 15, 2024 at 11:54 AM Eric J Esslinger via mailop <
mailop@mailop.org> wrote:
> Still getting bounces. Trying to engage with Google through
ARC trust is not just a binary. There are also ways that the ARC headers
can be used even if the ARC sealer is not 100% trusted. In this case,
adding ARC headers would help solve this particular issue (assuming the
original message was authenticated with at least one of SPF or DKIM).
You can see G
Hi Jason,
One additional thing worth investigating is adding ARC headers for the
forwarding cases. That has the potential to help with both downstream DMARC
evaluation as well as unauthenticated bounces. This is particularly
important if the DKIM signature is breaking or wasn't present in the firs
