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

Brian Jongekryg <[email protected]>
Newsgroups gmane.discuss
Message-ID <[email protected]>
On 02/12/2020 4:33 AM, Lars Ingebrigtsen wrote:
> 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.
> 
Thanks for the fix for the ietf.announce group -- I see the first 
i-d-announce there already.

For the ietf.rfc.announce group, I just assumed it was from the 
ietf-announce list, but I do see now that that includes more than what 
the old ietf.rfc.announce group was getting. It does appear that it was 
just the rfc-dist list.

I was able to subscribe to that list from the mailman web interface at 
https://www.rfc-editor.org/mailman/listinfo/rfc-dist and email to/from 
it for that list used [email protected]. Could you try 
again after dropping the mailman from the domain? mailman.rfc-editor.org 
just points to rfc-editor.org anyway:

dig mx mailman.rfc-editor.org

; <<>> DiG 9.10.2 <<>> mx mailman.rfc-editor.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56302
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;mailman.rfc-editor.org.                IN      MX

;; ANSWER SECTION:
mailman.rfc-editor.org. 1800    IN      CNAME   rfc-editor.org.
rfc-editor.org.         1800    IN      MX      0 rfc-editor.org.

Thanks,
Brian
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.