Re: OFF TOPIC: Mail going into Trash/Spam

[gbWilly <gbWilly@xxxxxxxxxxxxxx>]

On Thursday, January 23rd, 2025 at 16:31, T Lee Davidson <t.lee.davidson@xxxxxxxxx> wrote:

> On 1/23/25 9:16 AM, gbWilly wrote:
> 
> > It looks like you're trying to send emails from your @protonmail.com address, but using a third-party service - am I correct?
> 
> [snip]
> 
> > Please note that since you intend on sending emails from a third-party platform, [...]
> 
> 
> If you are using the Protonmail interface, either via web or desktop client, to send mail from your @protonmail.com address,
> then you are not using a third-party service as they are assuming. And if you are indeed not using a third-party service, they
> should be corrected on that point so they do not continue to assume "user error" and ignore the issue.
>

Thanks Lee, that where my thoughts too.

Meanwhile I received an answer to my reply (see below), so if someone can help how to react correctly to this please elaborate.

-- quote --
Hello Willy,
 
Thank you for responding.
 
Keep in mind that the 'List-Unsubscribe:List-Unsubscribe-Post' portion you see in the headers is not likely to be the cause of the problem you are experiencing. That being said, may I please ask that you elaborate on the exact setup being used with regards to the mailing list so that we can get a better understanding of the issue and then advise you on how to fix it? 
 
As far as I can tell from the EMLs you've provided, the <gbWilly@xxxxxxxxxxxxxx> address is being utilized to send the emails in question, but you're using a third-party platform - likely HostSharing - to do so. Since we do not authorize HostSharing to send emails on behalf of our domains (e.g. protonmail.com as above), their messages will fail SPF, DKIM, and, by extension. DMARC. 
 
What may be happening is that you're sending out the email first from <gbWilly@xxxxxxxxxxxxxx> using our app (1) and to the mailing list, but the mailing list then relies on the abovementioned third-party platform to deliver the emails to the intended recipients (2). 
 
However, in doing so, SPF authentication is automatically broken and since the mailing list platform seems to edit the content (or the headers) of the message substantially, the DKIM signature is also broken. 
 
If both SPF and DKIM fail, as here, DMARC will also fail. 
 
Looking forward to your reply.
-- end quote --

My technical know how on how all works is insufficient, so any help is welcome.

gbWilly