From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Matthias Apitz <gurucubano(at)googlemail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us> |
Subject: | Re: BUG #18822: mailing lists reject mails due to DKIM-signature |
Date: | 2025-02-24 16:44:07 |
Message-ID: | CABUevEx3Did_LKMmxfDwPKey=DBAkE513i+O_yTXexNUvuWjaw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Feb 24, 2025 at 3:48 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> > Unsigned mails(these days SPF, DKIM and DMARFC are not optional any
> > more) are basically undeliverable at scale to all large mail providers
> > other than if you are a super low volume sender - so that is a complete
> > non-starter for us.
>
> Yeah. The key point here is that we are not constrained only by
> what it says in the RFCs. We have to stay on the good side of the
> anti-spam policies at gmail and other large email providers, or
> we'll be blocked from delivering to large swaths of our user base.
>
>
Yes, indeed.
At one point not too long ago we had something like 60+% of our emails to
gmail getting delayed or dropped, leaving us with delivery queues exceeding
I think 2 million emails to gmail based destinations. Implementing this
DKIM fix is one of the things we did to get off that list...
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | João felipe Chiarelli Bourscheid | 2025-02-24 18:26:07 | Bug in Configuration Setting Functions after a Commit |
Previous Message | Greg Sabino Mullane | 2025-02-24 16:11:04 | Re: BUG #18822: mailing lists reject mails due to DKIM-signature |