Re: pgsql-announce not working?

Greetings,

* Tatsuo Ishii (ishii(at)sraoss(dot)co(dot)jp) wrote:
> Today I and my colleague tried to send a message to pgsql-announce but
> no moderation message was returned. Also the message is not in the
> moderation queue. Anything wrong with the list?

Based on the log messages, the email did get to the list and into the
queue for moderation, and a message was sent back saying that the post
was being held for moderation and then *that* post bounced back to us.
When that happens, we drop the post. The initial inbound log says:

New mail from pengbo(at)sraoss(dot)co(dot)jp to pgsql-announce(at)lists(dot)postgresql(dot)org(dot)

Our logs for the 'held for moderation' email show:

2018-01-09 09:24:17 [21705] 1eYq8n-0005e5-Nh <=
pgsql-announce-notice+M2757-a005b0e0d001d2fe559987e062b925de7bee398ac30176f2942ac8b3a965d4c3(at)lists(dot)postgresql(dot)org H=localhost (malur.postgresql.org) [127.0.0.1] P=esmtp S=1515 id=20180109092218(dot)2256(dot)93481(at)malur(dot)postgresql(dot)org
2018-01-09 09:24:20 [21721] 1eYq8n-0005e5-Nh => pengbo(at)sraoss(dot)co(dot)jp R=dnslookup T=remote_smtp H=osb.sraoss.co.jp [54.65.152.222] C="250 2.0.0 Ok: queued as 16BDA2027A" QT=3s DT=3s
2018-01-09 09:24:20 [21721] 1eYq8n-0005e5-Nh Completed QT=3s

So, the email was accepted by the osb.sraoss.co.jp system but then we
apparently got a bounce, here:

2018-01-09 09:24:25 [21765] 1eYq8v-0005f3-DW <= <> H=magus.postgresql.org [2a02:c0:301:0:ffff::29] P=esmtps X=TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256 CV=no S=4709 id=20180109092420(dot)7B5C02A1599(at)sraigw2(dot)sra(dot)co(dot)jp
2018-01-09 09:24:25 [21767] 1eYq8v-0005f3-DW => pgsql-announce <pgsql-announce-notice+M2757-a005b0e0d001d2fe559987e062b925de7bee398ac30176f2942ac8b3a965d4c3(at)lists(dot)postgresql(dot)org> R=pglister_router_sender T=pglister_pipe QT=0s DT=0s
2018-01-09 09:24:25 [21767] 1eYq8v-0005f3-DW Completed QT=0s

When we get back a bounce of the 'held for moderation' notice email, we
drop the post.

If you can talk to the administrators of the osb.sraoss.co.jp systems,
perhaps they can identify why they generated a bounce for the 16BDA2027A
email. We don't currently keep those bounces, so I don't have the
bounce email to see if it says anything interesting, unfortunately.
Perhaps we'll get that changed, since it seems like we could use that
information sometimes.

Thanks!

Stephen