Taylor UUCP version 1.07 uucico I use Taylor UUCP on my laptop and mail server. Mails send from laptop are send to the mail server via uucp over ssh, mails received by the mail server are spooled for later uucp calls to download to laptop. Postfix or Exim calls uux with no -r option, which in return calls uucico with no problem. Mails for both directions are transfered. When Postfix or Exim calls uux with -r option to spools the mails to /var/spool/uucp/, manually invoked uucico -x all -r1 -f -s $MailServer from laptop doesn't work. Mails don't transfered. No UUCP Debug and Log info are output, uucico becomes child process of systemd --user with controlling tty of pseudoterminal pts/N (N = 0 or 1 ...), the exit code of invoking uucico is 0. Then the uucico process do nothing and can't be killed, even the root user.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I'll close that one as a duplicate - as there is similar old report against uucico executed from interactive shell. *** This bug has been marked as a duplicate of bug 1398404 ***