Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin: > On 25/02/2023 19:49, Christoph Brinkhaus wrote: > > Now there are no messages reported by journald as above. > > I am curious if fixing unbound and so network-online.target helped to avoid > 169.254.x.y address in your case.
I am not sure because I have disabled/deinstalled stuff which triggered the assignment of the 149.254.x.y address. > Can fetchmail work without a kludge you > added to achieve some delay? My expectation is that unbound.service may be > dropped from Requires= and After= in fetchmail.service, but both fields > should have network-online.target. You are right, there is no need anymore to check if the mail server can be resolved before starting fetchmail. Nevertheless I still have the unbound.service and the opensmtpd.service in the Requires= and After= sections. The reason is that incoming mails are routed via opensmtpd because fetchmail runs as an unprivileged user. Additionally the setup is indemendent of the mail server. Then the mails are sorted by maildrop. As far as I remember forwarding the mails from an unprivileged fetchmail to maildrop running as my user did not work. Now incoming mails appear in /var/log/mail.log, too which is also nice. > I forgot that debugging of such issues should be started with "systemctl > --failed". I have still a lot to learn. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
