#325 atomic host two week release emails don't make it to the atomic-devel list
Closed: Fixed 3 years ago Opened 3 years ago by dustymabe.

We sent the emails to the list but it doesn't make it there.

https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-August/thread.html

You can see my reply to the announcement, but not the announcement itself.

https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-August/msg00027.html

I have added noreply@fedoraproject.org to the subscribers to the list but this
did not help.


This is still an issue for the email we sent yesterday to atomic-devel about the 2 week release.

I know @puiterwijk and @misc have talked about a solution to this problem. Can we narrow it down further?

As i said, I do not have any access to that server (managed by IT), I can't do much.

However, where the mail are sent from, could it be a SPF issue ?

As i said, I do not have any access to that server (managed by IT), I can't do much.
However, where the mail are sent from, could it be a SPF issue ?

We had a long chat in IRC about this two weeks ago with patrick when I first brought it up. He seemed to think it was because of the split dns/routing between internal RH and Fedora.

This has been applied, and should now be fixed.

This has been applied, and should now be fixed.

thanks patrick. will leave open until our next atomic host release email goes out and makes it to the list.

Metadata Update from @dustymabe:
- Issue tagged with: infra

3 years ago

still not working - the release announcement did not make it to the list but my reply did.

Here is the thread view: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-October/thread.html

Update from Patrick:

11:15:29    dustymabe | hey puiterwijk - the 2 week atomic release emails still don't seem to be making it to the atomic-devel mailing list
11:16:41          <-- | miminar (miminar@nat/redhat/x-vlxfkiszhbgukohj) has quit (Ping timeout: 240 seconds)
11:16:52   puiterwijk | dustymabe: at this moment, there's nothing I can do about that, since the projectatomic.io mailservers are actively refusing
                      | our connection
11:17:43          --> | crose (~crose@132.237.154.126) has joined #atomic
11:17:59    dustymabe | puiterwijk: question: did we get farther this time? i.e. was there a dns problem before (now fixed) and now there is a
                      | connection refused problem? 
11:18:12   puiterwijk | dustymabe: yes, we got much farther. There was no DNS issues
11:18:28    dustymabe | puiterwijk: thanks, can you update the issue with that information? 
11:18:31   puiterwijk | Oct  5 13:25:08 bastion01 postfix/smtp[6427]: 5486361F01C4: to=<atomic-devel@projectatomic.io>, relay=none, delay=38278,
                      | delays=38275/3/0.08/0, dsn=4.4.1, status=deferred (connect to mx2.redhat.com[10.11.203.6]:25: Connection refused)
11:18:43    dustymabe | i can try to resolve it with misc
11:19:00   puiterwijk | misc can't help with that. You'll need RHIT
11:19:33    dustymabe | sure - but I need someone to handle talking to RHIT, I believe 
11:19:45   puiterwijk | dustymabe: servicenow :)
11:20:24    dustymabe | so no one in OSAS is at least somewhat responsible for the lists? 
11:20:38    dustymabe | i would have assumed misc
11:20:49   puiterwijk | Nope, nobody

Ok so I did open a ticket with our IT and will handle information gathering, etc, etc. I can't promise a miracle (and for tracking purpose, our internal ticket number is "INC0617469")

Ok so I did open a ticket with our IT and will handle information gathering, etc, etc. I can't promise a miracle (and for tracking purpose, our internal ticket number is "INC0617469")

thanks so much @misc - I really appreciate it. If possible feel free to add me to the ticket and I'll provide any information I can to help make this successful.

IT is asking to me what is the IP used to connect. I suspect that's bastion01 and likely another one ?

After @misc and @puiterwijk worked with IT we are now receiving emails. Here is the first one from today's release.

Metadata Update from @dustymabe:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata