When I start the daemon it exits with the following errors: [root@wednesday]/var/log/httpd# journalctl -b -u postfix-mta-sts-resolver Oct 08 23:54:03 wednesday.degler.net systemd[1]: Starting postfix-mta-sts-resolver.service - Provide MTA-STS policy map to Postfix... Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: 2025-10-08 23:54:04 INFO MAIN: MTA-STS daemon starting... Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: 2025-10-08 23:54:04 INFO MAIN: Starting eventloop... Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: 2025-10-08 23:54:04 INFO MAIN: uvloop is not available. Falling back to built-in event loop. Oct 08 23:54:04 wednesday.degler.net python3[50975]: detected unhandled Python exception in '/usr/bin/mta-sts-daemon' Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: Traceback (most recent call last): Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: File "/usr/bin/mta-sts-daemon", line 8, in <module> Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: sys.exit(main()) Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: ~~~~^^ Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: File "/usr/lib/python3.14/site-packages/postfix_mta_sts_resolver/daemon.py", line 144, in main Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: evloop = asyncio.get_event_loop() Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: File "/usr/lib64/python3.14/asyncio/events.py", line 715, in get_event_loop Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: raise RuntimeError('There is no current event loop in thread %r.' Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: % threading.current_thread().name) Oct 08 23:54:04 wednesday.degler.net mta-sts-daemon[50975]: RuntimeError: There is no current event loop in thread 'MainThread'. Oct 08 23:54:04 wednesday.degler.net systemd[1]: postfix-mta-sts-resolver.service: Main process exited, code=exited, status=1/FAILURE Oct 08 23:54:04 wednesday.degler.net systemd[1]: postfix-mta-sts-resolver.service: Failed with result 'exit-code'. Fix #1 /usr/lib/python3.14/site-packages/postfix_mta_sts_resolver/daemon.py line 144 has: evloop = asyncio.get_event_loop() it should be evloop = asyncio.new_event_loop() to avoid a crash at startup Fix #2 Additionally the package depends on the python3-aiosqlite package, but its not expressed as a dependency. Reproducible: Always Steps to Reproduce: install package; attempt to start daemon. For me it always fails. Actual Results: deamon crashes with message above Expected Results: properly running daemon
Thanks for raising this. I need to give this RPM spec some proper love in the near future (bug 2371774) but these should be quicker fixes. > Additionally the package depends on the python3-aiosqlite package, but its not expressed as a dependency. This RPM follows how the upstream package models its dependencies. In https://github.com/Snawoot/postfix-mta-sts-resolver/blob/master/setup.py#L28 `aiosqlite` is expressed as an extra dependency. On the Fedora side this means we have a package called `postfix-mta-sts-resolver+sqlite` that you can install which will pull it in. I believe this isn't part of the main package as there's also PostgreSQL extras as an alternative backend. You'll need to raise this with the upstream project if you think it should change. On the RPM side, I suppose we could do something like this if you think that'd help? Recommands: (postfix-mta-sts-resolver+sqlite or postfix-mta-sts-resolver+postgres) This is also why that `uvloop` warning appears. Installing `postfix-mta-sts-resolver+uvloop` should clear that. > /usr/lib/python3.14/site-packages/postfix_mta_sts_resolver/daemon.py > line 144 has: > evloop = asyncio.get_event_loop() > it should be > evloop = asyncio.new_event_loop() > to avoid a crash at startup I've submitted this to the upstream project as https://github.com/Snawoot/postfix-mta-sts-resolver/pull/114. I'll push that to Fedora 43 and 44 now (as those are the versions who use `python` to mean 3.14), Bodhi will post links to those builds on this ticket as soon as they're done. Could you test them and upvote on Bodhi if it fixes your issue please?
Thanks for the quick response. I can certainly test. I raised the aiosqlite issue because the resolver would not start without it, so I'm wondering how it can be optional. Maybe something changed upstream?
FEDORA-2025-21e3c8a3f6 (postfix-mta-sts-resolver-1.5.0-6.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2025-21e3c8a3f6
FEDORA-2025-edd4780dd9 (postfix-mta-sts-resolver-1.5.0-6.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-edd4780dd9
FEDORA-2025-21e3c8a3f6 (postfix-mta-sts-resolver-1.5.0-6.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
(In reply to Stephen Degler from comment #2) > Thanks for the quick response. I can certainly test. > > I raised the aiosqlite issue because the resolver would not start without > it, so I'm wondering how it can be optional. Maybe something changed > upstream? I'd need to see the exact exception to answer that, but kinda odd that it's the one it's trying to use. https://github.com/Snawoot/postfix-mta-sts-resolver/blob/master/postfix_mta_sts_resolver/utils.py#L218-L241 shows all the supported cache options, but https://github.com/Snawoot/postfix-mta-sts-resolver/blob/master/postfix_mta_sts_resolver/defaults.py#L11 makes internal the default... Oh, the Fedora config overrides that https://src.fedoraproject.org/rpms/postfix-mta-sts-resolver/blob/rawhide/f/mta-sts-daemon.yml#_7 Given that, I think we should put a `Recommends` on the `sqlite` subpackage.
I downloaded the rpms from bohdi FEDORA-2025-edd4780dd9 and installed postfix-mta-sts-resolver-1.5.0-6.fc43.noarch.rpm. That worked fine. Daemon starts. I tried to install postfix-mta-sts-resolver+uvloop-1.5.0-6.fc43.noarch.rpm but it complains with the following error: [root@wednesday]/var/tmp/bohdi# rpm -Uvh postfix-mta-sts-resolver+uvloop-1.5.0-6.fc43.noarch.rpm error: Failed dependencies: python3.14dist(uvloop) >= 0.11 is needed by postfix-mta-sts-resolver+uvloop-1.5.0-6.fc43.noarch [root@wednesday]/var/tmp/bohdi# However pip install (as root) lists uvloop 0.21.0 on this system.
FEDORA-2025-1c3d752b8b (postfix-mta-sts-resolver-1.5.1-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-1c3d752b8b
tested postfix-mta-sts-resolver-1.5.1-1.fc43 and it is working as well. The uvloop package issue persists for me.
FEDORA-2025-1c3d752b8b has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-1c3d752b8b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-1c3d752b8b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
(In reply to Stephen Degler from comment #7) > [root@wednesday]/var/tmp/bohdi# rpm -Uvh > postfix-mta-sts-resolver+uvloop-1.5.0-6.fc43.noarch.rpm > error: Failed dependencies: > python3.14dist(uvloop) >= 0.11 is needed by > postfix-mta-sts-resolver+uvloop-1.5.0-6.fc43.noarch Yeah it looks like uvloop has been retired from Fedora due to bug 2326210 and missing Python 3.14 support. I'm going to remove the uvloop subpackage to clear things up, if uvloop returns to Fedora then I can reintroduce it. > However pip install (as root) lists uvloop 0.21.0 on this system. dnf only considers Python packages that came from RPMs when it's looking for dependencies. https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/installing_and_using_dynamic_programming_languages/assembly_packaging-python-3-rpms_installing-and-using-dynamic-programming-languages has some relevant info here.
FEDORA-2025-0357fcc7e6 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-0357fcc7e6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-0357fcc7e6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-0357fcc7e6 (postfix-mta-sts-resolver-1.5.1-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.