Thread: Bogus bounces from paul@paulweiss.info

Bogus bounces from paul@paulweiss.info

From
Tom Lane
Date:
The last few emails I've sent to pgsql-bugs have drawn error responses
like the attached.  I believe that in the past, we've treated broken
servers that send complaints to the original poster and not the mailing
list server to be sufficient grounds for immediate de-subscription.

            regards, tom lane

------- Forwarded Message

Date:    Mon, 6 Jan 2020 06:21:46 +0000
From:    <postmaster@outlook.com>
To:      <tgl@sss.pgh.pa.us>
Subject: Undeliverable: Re: BUG #16190: The usage of NULL pointer in refint.c

--d3dcb57a-c66a-4e4a-9904-ae603194af4c
Content-Type: multipart/alternative; differences=Content-Type;
    boundary="c73c3012-9f53-4b6a-8095-2db6131b2112"

--c73c3012-9f53-4b6a-8095-2db6131b2112
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

p3plibsmtp01-10.prod.phx3.secureserver.net rejected your message to the fol=
lowing email addresses:

paul@paulweiss.info<mailto:paul@paulweiss.info>
The address you sent your message to wasn't found at the destination domain=
. It might be misspelled or it might not exist. Try to fix the problem by d=
oing one or more of the following:

  1.  Send the message again, but before you do, delete and retype the addr=
ess. If your email program automatically suggests an address to use, don't =
select it.
  2.  Clear the recipient AutoComplete cache in your email program by follo=
wing the steps in this article: Status code 5.1.1<https://go.microsoft.com/=
fwlink/?LinkId=3D389363>. Then resend the message, but before you do, be su=
re to delete and retype the address.
  3.  Contact the recipient by some other means (by phone, for example) to =
confirm you're using the right address. Ask them if they've set up an email=
 forwarding rule that could be forwarding your message to an incorrect addr=
ess.



p3plibsmtp01-10.prod.phx3.secureserver.net gave this error:
104.47.70.103 is not allowed to send from <sss.pgh.pa.us> per its SPF Recor=
d. Please inspect your SPF settings, and try again. IB508 <http://x.co/srbo=
unce>







Diagnostic information for administrators:

Generating server: BN7NAM10HT147.mail.protection.outlook.com

paul@paulweiss.info
p3plibsmtp01-10.prod.phx3.secureserver.net
Remote Server returned '550 5.1.1 104.47.70.103 is not allowed to send from=
 <sss.pgh.pa.us> per its SPF Record. Please inspect your SPF settings, and =
try again. IB508 <http://x.co/srbounce>'

Original message headers:

Received: from BN7NAM10FT003.eop-nam10.prod.protection.outlook.com
 (10.13.156.60) by BN7NAM10HT147.eop-nam10.prod.protection.outlook.com
 (10.13.156.187) with Microsoft SMTP Server (version=3DTLS1_2,
 cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2602.11; Mon, 6 J=
an
 2020 06:21:45 +0000
Received: from MWHPR15MB1839.namprd15.prod.outlook.com (10.13.156.55) by
 BN7NAM10FT003.mail.protection.outlook.com (10.13.157.141) with Microsoft S=
MTP
 Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) =
id
 15.20.2602.11 via Frontend Transport; Mon, 6 Jan 2020 06:21:45 +0000
X-IncomingTopHeaderMarker: OriginalChecksum:4A7614DD8E67CB7904A11B346EBB8FF=
3EFF9634EA39A6BCA96DC281434BE856C;UpperCasedChecksum:BE5A4C3C81B955BA2FEC61=
20F0AA86076D247F5D610BF10D82F96B7454B8819F;SizeAsReceived:16748;Count:126
Resent-From: <libcub@hotmail.com>
Received: from MWHPR15MB1839.namprd15.prod.outlook.com ([::1]) by
 MWHPR15MB1839.namprd15.prod.outlook.com ([fe80::6c84:ae5c:f808:75ad%12]) w=
ith
 Microsoft SMTP Server id 15.20.2602.015; Mon, 6 Jan 2020 06:21:44 +0000
Authentication-Results: spf=3Dpass (sender IP is 217.196.149.56)
 smtp.mailfrom=3Dlists.postgresql.org; hotmail.com; dkim=3Dnone (message no=
t
 signed) header.d=3Dnone;hotmail.com; dmarc=3Dnone action=3Dnone
 header.from=3Dsss.pgh.pa.us;
Received-SPF: Pass (protection.outlook.com: domain of lists.postgresql.org
 designates 217.196.149.56 as permitted sender)
 receiver=3Dprotection.outlook.com; client-ip=3D217.196.149.56;
 helo=3Dmalur.postgresql.org;
X-IncomingTopHeaderMarker: OriginalChecksum:F8403C58FEC96A2132E9E2CC749EB3A=
31D5616214C3B36CB9C37F018860D5292;UpperCasedChecksum:E3BCD830DA155AF852C467=
0867D91AB2D2238B25B340A2FCEB97E6557151902B;SizeAsReceived:2137;Count:25
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
CC: starbugs@qq.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16190: The usage of NULL pointer in refint.c
In-Reply-To: <20200106051800.GL3598@paquier.xyz>
References: <16190-70181c803641c3dc@postgresql.org> <20200106051800.GL3598@=
paquier.xyz>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
        message dated "Mon, 06 Jan 2020 14:18:00 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset=3D"UTF-8"
Content-ID: <1233.1578291695.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 06 Jan 2020 01:21:35 -0500
Message-ID: <1234.1578291695@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Precedence: bulk
List-Unsubscribe: <https://lists.postgresql.org/unsub/37/526829306c213811bb=
c373281d7fd3837dda19cf37b33924fce835cd0b2bbae7/>
X-IncomingHeaderCount: 25
Return-Path: tgl@sss.pgh.pa.us
X-EOPAttributedMessage: 1
X-EOPTenantAttributedMessage: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa:0
X-Forefront-Antispam-Report: EFV:NLI;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: ea05ea28-90c7-4aa5-9489-08d79270b2=
b7
X-MS-TrafficTypeDiagnostic: AM5EUR02HT073:|BN7NAM10HT147:
X-MS-Exchange-EOPDirect: true
X-Sender-IP: 217.196.149.56
X-SID-PRA: TGL@SSS.PGH.PA.US
X-SID-Result: NONE
X-Microsoft-Antispam: BCL:2;
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT073
X-MS-Exchange-Transport-EndToEndLatency: 00:00:01.1052366
X-MS-Exchange-Processed-By-BccFoldering: 15.20.2602.010
X-MS-Exchange-Transport-Forked: True
X-MS-Exchange-Inbox-Rules-Loop: libcub@hotmail.com
X-IncomingHeaderCount: 126
X-MS-Exchange-Transport-CrossTenantHeadersStripped: BN7NAM10FT003.eop-nam10=
.prod.protection.outlook.com
X-OriginatorOrg: outlook.com


--c73c3012-9f53-4b6a-8095-2db6131b2112
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<Head></head><body>
<p><b><font color=3D"#000066" size=3D"3" face=3D"Arial">p3plibsmtp01-10.pro=
d.phx3.secureserver.net rejected your message to the following email addres=
ses:</font></b></p>
<font color=3D"#000000" size=3D"2" face=3D"Tahoma"><p><a href=3D"mailto:pau=
l@paulweiss.info">paul@paulweiss.info</a><br>
</font>
<font color=3D"#000000" size=3D"3" face=3D"Arial">The address you sent your=
 message to wasn't found at the destination domain. It might be misspelled =
or it might not exist. Try to fix the problem by doing one or more of the f=
ollowing:<ol><li>Send the message again, but before you do, delete and rety=
pe the address. If your email program automatically suggests an address to =
use, don't select it.</li><li>Clear the recipient AutoComplete cache in you=
r email program by following the steps in this article: <a href=3D"https://=
go.microsoft.com/fwlink/?LinkId=3D389363">Status code 5.1.1</a>. Then resen=
d the message, but before you do, be sure to delete and retype the address.=
</li><li>Contact the recipient by some other means (by phone, for example) =
to confirm you're using the right address. Ask them if they've set up an em=
ail forwarding rule that could be forwarding your message to an incorrect a=
ddress.</li></ol><br>
</font>
<font color=3D"#000000" size=3D"2" face=3D"Tahoma"><br>

<p><b>p3plibsmtp01-10.prod.phx3.secureserver.net gave this error:<br>
104.47.70.103 is not allowed to send from <sss.pgh.pa.us> per its SPF=
 Record. Please inspect your SPF settings, and try again. IB508 <http://=
x.co/srbounce> <br>
</b></p>
</p>
</font>
<br><br><br><br><br><br>
<font color=3D"#808080" size=3D"2" face=3D"Tahoma"><p><b>Diagnostic informa=
tion for administrators:</b></p>
<p>Generating server: BN7NAM10HT147.mail.protection.outlook.com<br>
</p>
<p>paul@paulweiss.info<br>
p3plibsmtp01-10.prod.phx3.secureserver.net<br>
Remote Server  returned '550 5.1.1 104.47.70.103 is not allowed to send fro=
m <sss.pgh.pa.us> per its SPF Record. Please inspect your SPF setting=
s, and try again. IB508 <http://x.co/srbounce>'<br>
</p>
<p>Original message headers:</p>
<pre>Received: from BN7NAM10FT003.eop-nam10.prod.protection.outlook.com
 (10.13.156.60) by BN7NAM10HT147.eop-nam10.prod.protection.outlook.com
 (10.13.156.187) with Microsoft SMTP Server (version=3DTLS1_2,
 cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2602.11; Mon, 6 J=
an
 2020 06:21:45 +0000
Received: from MWHPR15MB1839.namprd15.prod.outlook.com (10.13.156.55) by
 BN7NAM10FT003.mail.protection.outlook.com (10.13.157.141) with Microsoft S=
MTP
 Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) =
id
 15.20.2602.11 via Frontend Transport; Mon, 6 Jan 2020 06:21:45 +0000
X-IncomingTopHeaderMarker: OriginalChecksum:4A7614DD8E67CB7904A11B346EBB8FF=
3EFF9634EA39A6BCA96DC281434BE856C;UpperCasedChecksum:BE5A4C3C81B955BA2FEC61=
20F0AA86076D247F5D610BF10D82F96B7454B8819F;SizeAsReceived:16748;Count:126
Resent-From: <libcub@hotmail.com>
Received: from MWHPR15MB1839.namprd15.prod.outlook.com ([::1]) by
 MWHPR15MB1839.namprd15.prod.outlook.com ([fe80::6c84:ae5c:f808:75ad%12]) w=
ith
 Microsoft SMTP Server id 15.20.2602.015; Mon, 6 Jan 2020 06:21:44 +0000
Authentication-Results: spf=3Dpass (sender IP is 217.196.149.56)
 smtp.mailfrom=3Dlists.postgresql.org; hotmail.com; dkim=3Dnone (message no=
t
 signed) header.d=3Dnone;hotmail.com; dmarc=3Dnone action=3Dnone
 header.from=3Dsss.pgh.pa.us;
Received-SPF: Pass (protection.outlook.com: domain of lists.postgresql.org
 designates 217.196.149.56 as permitted sender)
 receiver=3Dprotection.outlook.com; client-ip=3D217.196.149.56;
 helo=3Dmalur.postgresql.org;
X-IncomingTopHeaderMarker: OriginalChecksum:F8403C58FEC96A2132E9E2CC749EB3A=
31D5616214C3B36CB9C37F018860D5292;UpperCasedChecksum:E3BCD830DA155AF852C467=
0867D91AB2D2238B25B340A2FCEB97E6557151902B;SizeAsReceived:2137;Count:25
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
CC: starbugs@qq.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16190: The usage of NULL pointer in refint.c
In-Reply-To: <20200106051800.GL3598@paquier.xyz>
References: <16190-70181c803641c3dc@postgresql.org> <2020010605180=
0.GL3598@paquier.xyz>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
    message dated "Mon, 06 Jan 2020 14:18:00 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset=3D"UTF-8"
Content-ID: <1233.1578291695.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 06 Jan 2020 01:21:35 -0500
Message-ID: <1234.1578291695@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Precedence: bulk
List-Unsubscribe: <https://lists.postgresql.org/unsub/37/526829306c21381=
1bbc373281d7fd3837dda19cf37b33924fce835cd0b2bbae7/>
X-IncomingHeaderCount: 25
Return-Path: tgl@sss.pgh.pa.us
X-EOPAttributedMessage: 1
X-EOPTenantAttributedMessage: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa:0
X-Forefront-Antispam-Report: EFV:NLI;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: ea05ea28-90c7-4aa5-9489-08d79270b2=
b7
X-MS-TrafficTypeDiagnostic: AM5EUR02HT073:|BN7NAM10HT147:
X-MS-Exchange-EOPDirect: true
X-Sender-IP: 217.196.149.56
X-SID-PRA: TGL@SSS.PGH.PA.US
X-SID-Result: NONE
X-Microsoft-Antispam: BCL:2;
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT073
X-MS-Exchange-Transport-EndToEndLatency: 00:00:01.1052366
X-MS-Exchange-Processed-By-BccFoldering: 15.20.2602.010
X-MS-Exchange-Transport-Forked: True
X-MS-Exchange-Inbox-Rules-Loop: libcub@hotmail.com
X-IncomingHeaderCount: 126
X-MS-Exchange-Transport-CrossTenantHeadersStripped: BN7NAM10FT003.eop-nam10=
.prod.protection.outlook.com
X-OriginatorOrg: outlook.com
</pre>
</font>
</body>
</html>=

--c73c3012-9f53-4b6a-8095-2db6131b2112--

--d3dcb57a-c66a-4e4a-9904-ae603194af4c
Content-Type: message/delivery-status

Reporting-MTA: dns;BN7NAM10HT147.mail.protection.outlook.com
Received-From-MTA: dns;MWHPR15MB1839.namprd15.prod.outlook.com
Arrival-Date: Mon, 6 Jan 2020 06:21:45 +0000

Final-Recipient: rfc822;paul@paulweiss.info
Action: failed
Status: 5.1.1
Diagnostic-Code: smtp;550 5.1.1 104.47.70.103 is not allowed to send from <sss.pgh.pa.us> per its SPF Record. Please
inspectyour SPF settings, and try again. IB508 <http://x.co/srbounce> 
Remote-MTA: dns;p3plibsmtp01-10.prod.phx3.secureserver.net


--d3dcb57a-c66a-4e4a-9904-ae603194af4c
Content-Type: message/rfc822

Received: from BN7NAM10FT003.eop-nam10.prod.protection.outlook.com
 (10.13.156.60) by BN7NAM10HT147.eop-nam10.prod.protection.outlook.com
 (10.13.156.187) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2602.11; Mon, 6 Jan
 2020 06:21:45 +0000
Received: from MWHPR15MB1839.namprd15.prod.outlook.com (10.13.156.55) by
 BN7NAM10FT003.mail.protection.outlook.com (10.13.157.141) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.2602.11 via Frontend Transport; Mon, 6 Jan 2020 06:21:45 +0000
X-IncomingTopHeaderMarker:
OriginalChecksum:4A7614DD8E67CB7904A11B346EBB8FF3EFF9634EA39A6BCA96DC281434BE856C;UpperCasedChecksum:BE5A4C3C81B955BA2FEC6120F0AA86076D247F5D610BF10D82F96B7454B8819F;SizeAsReceived:16748;Count:126
Resent-From: <libcub@hotmail.com>
Received: from MWHPR15MB1839.namprd15.prod.outlook.com ([::1]) by
 MWHPR15MB1839.namprd15.prod.outlook.com ([fe80::6c84:ae5c:f808:75ad%12]) with
 Microsoft SMTP Server id 15.20.2602.015; Mon, 6 Jan 2020 06:21:44 +0000
Authentication-Results: spf=pass (sender IP is 217.196.149.56)
 smtp.mailfrom=lists.postgresql.org; hotmail.com; dkim=none (message not
 signed) header.d=none;hotmail.com; dmarc=none action=none
 header.from=sss.pgh.pa.us;
Received-SPF: Pass (protection.outlook.com: domain of lists.postgresql.org
 designates 217.196.149.56 as permitted sender)
 receiver=protection.outlook.com; client-ip=217.196.149.56;
 helo=malur.postgresql.org;
X-IncomingTopHeaderMarker:
OriginalChecksum:F8403C58FEC96A2132E9E2CC749EB3A31D5616214C3B36CB9C37F018860D5292;UpperCasedChecksum:E3BCD830DA155AF852C4670867D91AB2D2238B25B340A2FCEB97E6557151902B;SizeAsReceived:2137;Count:25
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
CC: starbugs@qq.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16190: The usage of NULL pointer in refint.c
In-Reply-To: <20200106051800.GL3598@paquier.xyz>
References: <16190-70181c803641c3dc@postgresql.org> <20200106051800.GL3598@paquier.xyz>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
    message dated "Mon, 06 Jan 2020 14:18:00 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1233.1578291695.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 06 Jan 2020 01:21:35 -0500
Message-ID: <1234.1578291695@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Precedence: bulk
List-Unsubscribe:
<https://lists.postgresql.org/unsub/37/526829306c213811bbc373281d7fd3837dda19cf37b33924fce835cd0b2bbae7/>
X-IncomingHeaderCount: 25
Return-Path: tgl@sss.pgh.pa.us
X-EOPAttributedMessage: 1
X-EOPTenantAttributedMessage: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa:0
X-Forefront-Antispam-Report: EFV:NLI;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: ea05ea28-90c7-4aa5-9489-08d79270b2b7
X-MS-TrafficTypeDiagnostic: AM5EUR02HT073:|BN7NAM10HT147:
X-MS-Exchange-EOPDirect: true
X-Sender-IP: 217.196.149.56
X-SID-PRA: TGL@SSS.PGH.PA.US
X-SID-Result: NONE
X-Microsoft-Antispam: BCL:2;
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT073
X-MS-Exchange-Transport-EndToEndLatency: 00:00:01.1052366
X-MS-Exchange-Processed-By-BccFoldering: 15.20.2602.010
X-MS-Exchange-Transport-Forked: True
X-MS-Exchange-Inbox-Rules-Loop: libcub@hotmail.com
X-IncomingHeaderCount: 126
X-MS-Exchange-Transport-CrossTenantHeadersStripped: BN7NAM10FT003.eop-nam10.prod.protection.outlook.com
X-OriginatorOrg: outlook.com

Michael Paquier <michael@paquier.xyz> writes:
> On Mon, Jan 06, 2020 at 03:39:36AM +0000, PG Bug reporting form wrote:
>> We checked the code in file =E2=80=9Crefint.c=E2=80=9D and there is one=
 error occurring in
>> line 636.

> It could be better to switch all that to not use directly system
> calls, and rely properly on a high-level memory context with
> palloc-like allocations.

Yeah, if somebody wanted to fix this, the right way is to replace
these malloc calls with pallocs.  Some investigation would be needed
about which context to use.

> ... There could be also an argument to just
> remove the module per the lack of attention it is getting, though it
> is still useful as an example of use for SPI, and the docs mention
> it for that.

The regression tests use refint too.  Still, it's not production-grade
code by any means, and I'm not sure if there's much point in making
it so.  I won't stand in the way if somebody else wants to ;-)

            regards, tom lane



--d3dcb57a-c66a-4e4a-9904-ae603194af4c--

------- End of Forwarded Message



Re: Bogus bounces from paul@paulweiss.info

From
Magnus Hagander
Date:
That's definitely annoying. However, that email address is not
subscribed to anything. Which is probably part of the problem. AIUI
this is somebody subscribed with a different address who is then
forwarding this address to paul@paulweiss.info. It looks like it's
being forwarded *from* a microsoft address (and the IP address
rejected is from in there). (And it's also clearly buggy, because it's
doing SPF based on the From address, and SPF is supposed to be applied
to the envelope sender only -- either that or hotmail is mangling up
the sender vs from).

Digging deeper into the headers, I believe it's libcub@hotmail.com
that's forwarding the email. And that one is subscribed.

Based on that, I will unsubscribe this address from the lists now.
Once the bug is fixed on that side, they're welcome to resubscribe
again of course!

//Magnus


On Mon, Jan 6, 2020 at 7:34 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> The last few emails I've sent to pgsql-bugs have drawn error responses
> like the attached.  I believe that in the past, we've treated broken
> servers that send complaints to the original poster and not the mailing
> list server to be sufficient grounds for immediate de-subscription.
>
>                         regards, tom lane
>
> ------- Forwarded Message
>
> Date:    Mon, 6 Jan 2020 06:21:46 +0000
> From:    <postmaster@outlook.com>
> To:      <tgl@sss.pgh.pa.us>
> Subject: Undeliverable: Re: BUG #16190: The usage of NULL pointer in refint.c
>
> --d3dcb57a-c66a-4e4a-9904-ae603194af4c
> Content-Type: multipart/alternative; differences=Content-Type;
>         boundary="c73c3012-9f53-4b6a-8095-2db6131b2112"
>
> --c73c3012-9f53-4b6a-8095-2db6131b2112
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> p3plibsmtp01-10.prod.phx3.secureserver.net rejected your message to the fol=
> lowing email addresses:
>
> paul@paulweiss.info<mailto:paul@paulweiss.info>
> The address you sent your message to wasn't found at the destination domain=
> . It might be misspelled or it might not exist. Try to fix the problem by d=
> oing one or more of the following:
>
>   1.  Send the message again, but before you do, delete and retype the addr=
> ess. If your email program automatically suggests an address to use, don't =
> select it.
>   2.  Clear the recipient AutoComplete cache in your email program by follo=
> wing the steps in this article: Status code 5.1.1<https://go.microsoft.com/=
> fwlink/?LinkId=3D389363>. Then resend the message, but before you do, be su=
> re to delete and retype the address.
>   3.  Contact the recipient by some other means (by phone, for example) to =
> confirm you're using the right address. Ask them if they've set up an email=
>  forwarding rule that could be forwarding your message to an incorrect addr=
> ess.
>
>
>
> p3plibsmtp01-10.prod.phx3.secureserver.net gave this error:
> 104.47.70.103 is not allowed to send from <sss.pgh.pa.us> per its SPF Recor=
> d. Please inspect your SPF settings, and try again. IB508 <http://x.co/srbo=
> unce>
>
>
>
>
>
>
>
> Diagnostic information for administrators:
>
> Generating server: BN7NAM10HT147.mail.protection.outlook.com
>
> paul@paulweiss.info
> p3plibsmtp01-10.prod.phx3.secureserver.net
> Remote Server returned '550 5.1.1 104.47.70.103 is not allowed to send from=
>  <sss.pgh.pa.us> per its SPF Record. Please inspect your SPF settings, and =
> try again. IB508 <http://x.co/srbounce>'
>
> Original message headers:
>
> Received: from BN7NAM10FT003.eop-nam10.prod.protection.outlook.com
>  (10.13.156.60) by BN7NAM10HT147.eop-nam10.prod.protection.outlook.com
>  (10.13.156.187) with Microsoft SMTP Server (version=3DTLS1_2,
>  cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2602.11; Mon, 6 J=
> an
>  2020 06:21:45 +0000
> Received: from MWHPR15MB1839.namprd15.prod.outlook.com (10.13.156.55) by
>  BN7NAM10FT003.mail.protection.outlook.com (10.13.157.141) with Microsoft S=
> MTP
>  Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) =
> id
>  15.20.2602.11 via Frontend Transport; Mon, 6 Jan 2020 06:21:45 +0000
> X-IncomingTopHeaderMarker: OriginalChecksum:4A7614DD8E67CB7904A11B346EBB8FF=
> 3EFF9634EA39A6BCA96DC281434BE856C;UpperCasedChecksum:BE5A4C3C81B955BA2FEC61=
> 20F0AA86076D247F5D610BF10D82F96B7454B8819F;SizeAsReceived:16748;Count:126
> Resent-From: <libcub@hotmail.com>
> Received: from MWHPR15MB1839.namprd15.prod.outlook.com ([::1]) by
>  MWHPR15MB1839.namprd15.prod.outlook.com ([fe80::6c84:ae5c:f808:75ad%12]) w=
> ith
>  Microsoft SMTP Server id 15.20.2602.015; Mon, 6 Jan 2020 06:21:44 +0000
> Authentication-Results: spf=3Dpass (sender IP is 217.196.149.56)
>  smtp.mailfrom=3Dlists.postgresql.org; hotmail.com; dkim=3Dnone (message no=
> t
>  signed) header.d=3Dnone;hotmail.com; dmarc=3Dnone action=3Dnone
>  header.from=3Dsss.pgh.pa.us;
> Received-SPF: Pass (protection.outlook.com: domain of lists.postgresql.org
>  designates 217.196.149.56 as permitted sender)
>  receiver=3Dprotection.outlook.com; client-ip=3D217.196.149.56;
>  helo=3Dmalur.postgresql.org;
> X-IncomingTopHeaderMarker: OriginalChecksum:F8403C58FEC96A2132E9E2CC749EB3A=
> 31D5616214C3B36CB9C37F018860D5292;UpperCasedChecksum:E3BCD830DA155AF852C467=
> 0867D91AB2D2238B25B340A2FCEB97E6557151902B;SizeAsReceived:2137;Count:25
> From: Tom Lane <tgl@sss.pgh.pa.us>
> To: Michael Paquier <michael@paquier.xyz>
> CC: starbugs@qq.com, pgsql-bugs@lists.postgresql.org
> Subject: Re: BUG #16190: The usage of NULL pointer in refint.c
> In-Reply-To: <20200106051800.GL3598@paquier.xyz>
> References: <16190-70181c803641c3dc@postgresql.org> <20200106051800.GL3598@=
> paquier.xyz>
> Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
>         message dated "Mon, 06 Jan 2020 14:18:00 +0900"
> MIME-Version: 1.0
> Content-Type: text/plain; charset=3D"UTF-8"
> Content-ID: <1233.1578291695.1@sss.pgh.pa.us>
> Content-Transfer-Encoding: quoted-printable
> Date: Mon, 06 Jan 2020 01:21:35 -0500
> Message-ID: <1234.1578291695@sss.pgh.pa.us>
> List-Id: <pgsql-bugs.lists.postgresql.org>
> List-Help: <https://lists.postgresql.org/manage/>
> List-Subscribe: <https://lists.postgresql.org/manage/>
> List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
> List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
> List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
> Precedence: bulk
> List-Unsubscribe: <https://lists.postgresql.org/unsub/37/526829306c213811bb=
> c373281d7fd3837dda19cf37b33924fce835cd0b2bbae7/>
> X-IncomingHeaderCount: 25
> Return-Path: tgl@sss.pgh.pa.us
> X-EOPAttributedMessage: 1
> X-EOPTenantAttributedMessage: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa:0
> X-Forefront-Antispam-Report: EFV:NLI;
> X-MS-PublicTrafficType: Email
> X-MS-Office365-Filtering-Correlation-Id: ea05ea28-90c7-4aa5-9489-08d79270b2=
> b7
> X-MS-TrafficTypeDiagnostic: AM5EUR02HT073:|BN7NAM10HT147:
> X-MS-Exchange-EOPDirect: true
> X-Sender-IP: 217.196.149.56
> X-SID-PRA: TGL@SSS.PGH.PA.US
> X-SID-Result: NONE
> X-Microsoft-Antispam: BCL:2;
> X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT073
> X-MS-Exchange-Transport-EndToEndLatency: 00:00:01.1052366
> X-MS-Exchange-Processed-By-BccFoldering: 15.20.2602.010
> X-MS-Exchange-Transport-Forked: True
> X-MS-Exchange-Inbox-Rules-Loop: libcub@hotmail.com
> X-IncomingHeaderCount: 126
> X-MS-Exchange-Transport-CrossTenantHeadersStripped: BN7NAM10FT003.eop-nam10=
> .prod.protection.outlook.com
> X-OriginatorOrg: outlook.com
>
>
> --c73c3012-9f53-4b6a-8095-2db6131b2112
> Content-Type: text/html; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> <html>
> <Head></head><body>
> <p><b><font color=3D"#000066" size=3D"3" face=3D"Arial">p3plibsmtp01-10.pro=
> d.phx3.secureserver.net rejected your message to the following email addres=
> ses:</font></b></p>
> <font color=3D"#000000" size=3D"2" face=3D"Tahoma"><p><a href=3D"mailto:pau=
> l@paulweiss.info">paul@paulweiss.info</a><br>
> </font>
> <font color=3D"#000000" size=3D"3" face=3D"Arial">The address you sent your=
>  message to wasn't found at the destination domain. It might be misspelled =
> or it might not exist. Try to fix the problem by doing one or more of the f=
> ollowing:<ol><li>Send the message again, but before you do, delete and rety=
> pe the address. If your email program automatically suggests an address to =
> use, don't select it.</li><li>Clear the recipient AutoComplete cache in you=
> r email program by following the steps in this article: <a href=3D"https://=
> go.microsoft.com/fwlink/?LinkId=3D389363">Status code 5.1.1</a>. Then resen=
> d the message, but before you do, be sure to delete and retype the address.=
> </li><li>Contact the recipient by some other means (by phone, for example) =
> to confirm you're using the right address. Ask them if they've set up an em=
> ail forwarding rule that could be forwarding your message to an incorrect a=
> ddress.</li></ol><br>
> </font>
> <font color=3D"#000000" size=3D"2" face=3D"Tahoma"><br>
>
> <p><b>p3plibsmtp01-10.prod.phx3.secureserver.net gave this error:<br>
> 104.47.70.103 is not allowed to send from <sss.pgh.pa.us> per its SPF=
>  Record. Please inspect your SPF settings, and try again. IB508 <http://=
> x.co/srbounce> <br>
> </b></p>
> </p>
> </font>
> <br><br><br><br><br><br>
> <font color=3D"#808080" size=3D"2" face=3D"Tahoma"><p><b>Diagnostic informa=
> tion for administrators:</b></p>
> <p>Generating server: BN7NAM10HT147.mail.protection.outlook.com<br>
> </p>
> <p>paul@paulweiss.info<br>
> p3plibsmtp01-10.prod.phx3.secureserver.net<br>
> Remote Server  returned '550 5.1.1 104.47.70.103 is not allowed to send fro=
> m <sss.pgh.pa.us> per its SPF Record. Please inspect your SPF setting=
> s, and try again. IB508 <http://x.co/srbounce>'<br>
> </p>
> <p>Original message headers:</p>
> <pre>Received: from BN7NAM10FT003.eop-nam10.prod.protection.outlook.com
>  (10.13.156.60) by BN7NAM10HT147.eop-nam10.prod.protection.outlook.com
>  (10.13.156.187) with Microsoft SMTP Server (version=3DTLS1_2,
>  cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2602.11; Mon, 6 J=
> an
>  2020 06:21:45 +0000
> Received: from MWHPR15MB1839.namprd15.prod.outlook.com (10.13.156.55) by
>  BN7NAM10FT003.mail.protection.outlook.com (10.13.157.141) with Microsoft S=
> MTP
>  Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) =
> id
>  15.20.2602.11 via Frontend Transport; Mon, 6 Jan 2020 06:21:45 +0000
> X-IncomingTopHeaderMarker: OriginalChecksum:4A7614DD8E67CB7904A11B346EBB8FF=
> 3EFF9634EA39A6BCA96DC281434BE856C;UpperCasedChecksum:BE5A4C3C81B955BA2FEC61=
> 20F0AA86076D247F5D610BF10D82F96B7454B8819F;SizeAsReceived:16748;Count:126
> Resent-From: <libcub@hotmail.com>
> Received: from MWHPR15MB1839.namprd15.prod.outlook.com ([::1]) by
>  MWHPR15MB1839.namprd15.prod.outlook.com ([fe80::6c84:ae5c:f808:75ad%12]) w=
> ith
>  Microsoft SMTP Server id 15.20.2602.015; Mon, 6 Jan 2020 06:21:44 +0000
> Authentication-Results: spf=3Dpass (sender IP is 217.196.149.56)
>  smtp.mailfrom=3Dlists.postgresql.org; hotmail.com; dkim=3Dnone (message no=
> t
>  signed) header.d=3Dnone;hotmail.com; dmarc=3Dnone action=3Dnone
>  header.from=3Dsss.pgh.pa.us;
> Received-SPF: Pass (protection.outlook.com: domain of lists.postgresql.org
>  designates 217.196.149.56 as permitted sender)
>  receiver=3Dprotection.outlook.com; client-ip=3D217.196.149.56;
>  helo=3Dmalur.postgresql.org;
> X-IncomingTopHeaderMarker: OriginalChecksum:F8403C58FEC96A2132E9E2CC749EB3A=
> 31D5616214C3B36CB9C37F018860D5292;UpperCasedChecksum:E3BCD830DA155AF852C467=
> 0867D91AB2D2238B25B340A2FCEB97E6557151902B;SizeAsReceived:2137;Count:25
> From: Tom Lane <tgl@sss.pgh.pa.us>
> To: Michael Paquier <michael@paquier.xyz>
> CC: starbugs@qq.com, pgsql-bugs@lists.postgresql.org
> Subject: Re: BUG #16190: The usage of NULL pointer in refint.c
> In-Reply-To: <20200106051800.GL3598@paquier.xyz>
> References: <16190-70181c803641c3dc@postgresql.org> <2020010605180=
> 0.GL3598@paquier.xyz>
> Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
>         message dated "Mon, 06 Jan 2020 14:18:00 +0900"
> MIME-Version: 1.0
> Content-Type: text/plain; charset=3D"UTF-8"
> Content-ID: <1233.1578291695.1@sss.pgh.pa.us>
> Content-Transfer-Encoding: quoted-printable
> Date: Mon, 06 Jan 2020 01:21:35 -0500
> Message-ID: <1234.1578291695@sss.pgh.pa.us>
> List-Id: <pgsql-bugs.lists.postgresql.org>
> List-Help: <https://lists.postgresql.org/manage/>
> List-Subscribe: <https://lists.postgresql.org/manage/>
> List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
> List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
> List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
> Precedence: bulk
> List-Unsubscribe: <https://lists.postgresql.org/unsub/37/526829306c21381=
> 1bbc373281d7fd3837dda19cf37b33924fce835cd0b2bbae7/>
> X-IncomingHeaderCount: 25
> Return-Path: tgl@sss.pgh.pa.us
> X-EOPAttributedMessage: 1
> X-EOPTenantAttributedMessage: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa:0
> X-Forefront-Antispam-Report: EFV:NLI;
> X-MS-PublicTrafficType: Email
> X-MS-Office365-Filtering-Correlation-Id: ea05ea28-90c7-4aa5-9489-08d79270b2=
> b7
> X-MS-TrafficTypeDiagnostic: AM5EUR02HT073:|BN7NAM10HT147:
> X-MS-Exchange-EOPDirect: true
> X-Sender-IP: 217.196.149.56
> X-SID-PRA: TGL@SSS.PGH.PA.US
> X-SID-Result: NONE
> X-Microsoft-Antispam: BCL:2;
> X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT073
> X-MS-Exchange-Transport-EndToEndLatency: 00:00:01.1052366
> X-MS-Exchange-Processed-By-BccFoldering: 15.20.2602.010
> X-MS-Exchange-Transport-Forked: True
> X-MS-Exchange-Inbox-Rules-Loop: libcub@hotmail.com
> X-IncomingHeaderCount: 126
> X-MS-Exchange-Transport-CrossTenantHeadersStripped: BN7NAM10FT003.eop-nam10=
> .prod.protection.outlook.com
> X-OriginatorOrg: outlook.com
> </pre>
> </font>
> </body>
> </html>=
>
> --c73c3012-9f53-4b6a-8095-2db6131b2112--
>
> --d3dcb57a-c66a-4e4a-9904-ae603194af4c
> Content-Type: message/delivery-status
>
> Reporting-MTA: dns;BN7NAM10HT147.mail.protection.outlook.com
> Received-From-MTA: dns;MWHPR15MB1839.namprd15.prod.outlook.com
> Arrival-Date: Mon, 6 Jan 2020 06:21:45 +0000
>
> Final-Recipient: rfc822;paul@paulweiss.info
> Action: failed
> Status: 5.1.1
> Diagnostic-Code: smtp;550 5.1.1 104.47.70.103 is not allowed to send from <sss.pgh.pa.us> per its SPF Record. Please
inspectyour SPF settings, and try again. IB508 <http://x.co/srbounce>
 
> Remote-MTA: dns;p3plibsmtp01-10.prod.phx3.secureserver.net
>
>
> --d3dcb57a-c66a-4e4a-9904-ae603194af4c
> Content-Type: message/rfc822
>
> Received: from BN7NAM10FT003.eop-nam10.prod.protection.outlook.com
>  (10.13.156.60) by BN7NAM10HT147.eop-nam10.prod.protection.outlook.com
>  (10.13.156.187) with Microsoft SMTP Server (version=TLS1_2,
>  cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2602.11; Mon, 6 Jan
>  2020 06:21:45 +0000
> Received: from MWHPR15MB1839.namprd15.prod.outlook.com (10.13.156.55) by
>  BN7NAM10FT003.mail.protection.outlook.com (10.13.157.141) with Microsoft SMTP
>  Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
>  15.20.2602.11 via Frontend Transport; Mon, 6 Jan 2020 06:21:45 +0000
> X-IncomingTopHeaderMarker:
OriginalChecksum:4A7614DD8E67CB7904A11B346EBB8FF3EFF9634EA39A6BCA96DC281434BE856C;UpperCasedChecksum:BE5A4C3C81B955BA2FEC6120F0AA86076D247F5D610BF10D82F96B7454B8819F;SizeAsReceived:16748;Count:126
> Resent-From: <libcub@hotmail.com>
> Received: from MWHPR15MB1839.namprd15.prod.outlook.com ([::1]) by
>  MWHPR15MB1839.namprd15.prod.outlook.com ([fe80::6c84:ae5c:f808:75ad%12]) with
>  Microsoft SMTP Server id 15.20.2602.015; Mon, 6 Jan 2020 06:21:44 +0000
> Authentication-Results: spf=pass (sender IP is 217.196.149.56)
>  smtp.mailfrom=lists.postgresql.org; hotmail.com; dkim=none (message not
>  signed) header.d=none;hotmail.com; dmarc=none action=none
>  header.from=sss.pgh.pa.us;
> Received-SPF: Pass (protection.outlook.com: domain of lists.postgresql.org
>  designates 217.196.149.56 as permitted sender)
>  receiver=protection.outlook.com; client-ip=217.196.149.56;
>  helo=malur.postgresql.org;
> X-IncomingTopHeaderMarker:
OriginalChecksum:F8403C58FEC96A2132E9E2CC749EB3A31D5616214C3B36CB9C37F018860D5292;UpperCasedChecksum:E3BCD830DA155AF852C4670867D91AB2D2238B25B340A2FCEB97E6557151902B;SizeAsReceived:2137;Count:25
> From: Tom Lane <tgl@sss.pgh.pa.us>
> To: Michael Paquier <michael@paquier.xyz>
> CC: starbugs@qq.com, pgsql-bugs@lists.postgresql.org
> Subject: Re: BUG #16190: The usage of NULL pointer in refint.c
> In-Reply-To: <20200106051800.GL3598@paquier.xyz>
> References: <16190-70181c803641c3dc@postgresql.org> <20200106051800.GL3598@paquier.xyz>
> Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
>         message dated "Mon, 06 Jan 2020 14:18:00 +0900"
> MIME-Version: 1.0
> Content-Type: text/plain; charset="UTF-8"
> Content-ID: <1233.1578291695.1@sss.pgh.pa.us>
> Content-Transfer-Encoding: quoted-printable
> Date: Mon, 06 Jan 2020 01:21:35 -0500
> Message-ID: <1234.1578291695@sss.pgh.pa.us>
> List-Id: <pgsql-bugs.lists.postgresql.org>
> List-Help: <https://lists.postgresql.org/manage/>
> List-Subscribe: <https://lists.postgresql.org/manage/>
> List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
> List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
> List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
> Precedence: bulk
> List-Unsubscribe:
<https://lists.postgresql.org/unsub/37/526829306c213811bbc373281d7fd3837dda19cf37b33924fce835cd0b2bbae7/>
> X-IncomingHeaderCount: 25
> Return-Path: tgl@sss.pgh.pa.us
> X-EOPAttributedMessage: 1
> X-EOPTenantAttributedMessage: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa:0
> X-Forefront-Antispam-Report: EFV:NLI;
> X-MS-PublicTrafficType: Email
> X-MS-Office365-Filtering-Correlation-Id: ea05ea28-90c7-4aa5-9489-08d79270b2b7
> X-MS-TrafficTypeDiagnostic: AM5EUR02HT073:|BN7NAM10HT147:
> X-MS-Exchange-EOPDirect: true
> X-Sender-IP: 217.196.149.56
> X-SID-PRA: TGL@SSS.PGH.PA.US
> X-SID-Result: NONE
> X-Microsoft-Antispam: BCL:2;
> X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT073
> X-MS-Exchange-Transport-EndToEndLatency: 00:00:01.1052366
> X-MS-Exchange-Processed-By-BccFoldering: 15.20.2602.010
> X-MS-Exchange-Transport-Forked: True
> X-MS-Exchange-Inbox-Rules-Loop: libcub@hotmail.com
> X-IncomingHeaderCount: 126
> X-MS-Exchange-Transport-CrossTenantHeadersStripped: BN7NAM10FT003.eop-nam10.prod.protection.outlook.com
> X-OriginatorOrg: outlook.com
>
> Michael Paquier <michael@paquier.xyz> writes:
> > On Mon, Jan 06, 2020 at 03:39:36AM +0000, PG Bug reporting form wrote:
> >> We checked the code in file =E2=80=9Crefint.c=E2=80=9D and there is one=
>  error occurring in
> >> line 636.
>
> > It could be better to switch all that to not use directly system
> > calls, and rely properly on a high-level memory context with
> > palloc-like allocations.
>
> Yeah, if somebody wanted to fix this, the right way is to replace
> these malloc calls with pallocs.  Some investigation would be needed
> about which context to use.
>
> > ... There could be also an argument to just
> > remove the module per the lack of attention it is getting, though it
> > is still useful as an example of use for SPI, and the docs mention
> > it for that.
>
> The regression tests use refint too.  Still, it's not production-grade
> code by any means, and I'm not sure if there's much point in making
> it so.  I won't stand in the way if somebody else wants to ;-)
>
>                         regards, tom lane
>
>
>
> --d3dcb57a-c66a-4e4a-9904-ae603194af4c--
>
> ------- End of Forwarded Message
>
>