dustymabe added a new comment to an issue you are following:
``
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(a)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(a)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
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/325