From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New email address |
Date: | 2015-11-24 12:33:19 |
Message-ID: | CABUevEzPm11mw60GqpbjFwtxzccL-W=U_r8SiiG0NHPJk0EpEA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 24, 2015 at 12:58 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:
> Magnus Hagander wrote:
>
> > That's a direct effect of the dmarc policy change. Yahoo no longer
> supports
> > their customers using mailing lists. They changed their policies for such
> > emails to hard reject, which makes Gmail (and presumably others) stick
> them
> > in spam.. It would happen to all the emails except the ones where you are
> > on direct cc.
>
> FWIW we've been rejecting posts coming from @yahoo.com addresses for a
> long time now, since DMARC was first introduced. We didn't get around
> to blocking other domains owned by Yahoo such as ymail.com or national
> yahoo subdomains, but I assume (without checking) that those will cause
> trouble too and we will have to block them out in order not to fill our
> queues with useless bounces.
>
Yes. The difference is they changed it from a soft fail to a hard reject,
AIUI. From all of their domains (Kevin forwarded me the responses from
Yahoo support). So the problem got worse, but it's the same basic one.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2015-11-24 12:59:50 | Re: parallelism and sorting |
Previous Message | Greg Stark | 2015-11-24 12:25:31 | Re: Revisiting pg_stat_statements and IN() (Was: Re: pg_stat_statements fingerprinting logic and ArrayExpr) |