Re: ietf.announce, ietf.rfc.announce problem

Brian Jongekryg <[email protected]> writes:

> With the NNTP server move, there seems to be a problem with the group
> to mailing list mapping.
>
> Prior to January 15, gmane.ietf.announce has messages from the
> i-d-announce IETF mailing list, but now appears to have messages from 
> the ietf-announce list.
>
> The gmane.ietf.rfc.announce group used to have the messages from the
> ietf-announce list, but since January 15 has received no new messages.

To take the latter first, all the messages in that group have

To: [email protected], [email protected]

but the subscription to that group is from the latter:

gmane.ietf.rfc.announce   [email protected]

But signing up for the list fails:

2020-02-12 11:22:20 1j1p09-0000NO-1b == [email protected] R=dnslookup T=remote_smtp defer (-44) H=rfc-editor.org [4.31.198.49]: SMTP error from remote mail server after RCPT TO:<[email protected]>: 450 4.1.1 <[email protected]>: Recipient address rejected: unverified address: mail for mailman.rfc-editor.org loops back to myself

So there's a misconfiguration on the rfc-editor.org side.

For the ietf.announce group, I've now unsubbed ietf-announce and subbed
i-d-announce.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no