Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #255388

Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

From Christoph Brinkhaus <c.brinkhaus@t-online.de>
Newsgroups linux.debian.user
Subject Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')
Date 2023-02-26 17:30 +0100
Message-ID <G3s4p-8ER5-1@gated-at.bofh.it> (permalink)
References (5 earlier) <G20tz-7Jto-3@gated-at.bofh.it> <G2I1z-8bOW-1@gated-at.bofh.it> <G2LiN-8dKn-3@gated-at.bofh.it> <G329X-8ogY-3@gated-at.bofh.it> <G3ri1-8Ek5-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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.

Back to linux.debian.user | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Remove route  '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-19 17:30 +0100
  Re: Remove route  '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-19 17:40 +0100
    Re: Remove route  '169.254.0.0/16 dev ovs-system' Stefan Monnier <monnier@iro.umontreal.ca> - 2023-02-19 18:30 +0100
      Re: Remove route  '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-19 20:00 +0100
        Re: Remove route  '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-19 20:20 +0100
        Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-20 05:40 +0100
    Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-20 04:00 +0100
      Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-20 05:20 +0100
      Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-20 15:50 +0100
        Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-21 17:10 +0100
          Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-21 18:50 +0100
            Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-21 19:10 +0100
              Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-21 19:30 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-21 19:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' <tomas@tuxteam.de> - 2023-02-21 20:10 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-22 19:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-22 20:10 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Greg Wooledge <greg@wooledge.org> - 2023-02-22 20:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Darac Marjal <mailinglist@darac.org.uk> - 2023-02-22 21:10 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-22 16:30 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-22 17:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-22 19:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-24 16:20 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-24 19:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-24 20:30 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-24 22:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-25 03:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-26 12:20 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Reco <recoverym4n@enotuniq.net> - 2023-02-26 14:20 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-26 15:20 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Reco <recoverym4n@enotuniq.net> - 2023-02-26 15:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-27 23:00 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Reco <recoverym4n@enotuniq.net> - 2023-02-28 07:10 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-26 16:20 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-26 18:10 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-25 04:00 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-25 04:40 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-25 13:50 +0100
                unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Max Nikulin <manikulin@gmail.com> - 2023-02-26 16:40 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-26 17:30 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-26 19:10 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') David Wright <deblis@lionunicorn.co.uk> - 2023-02-26 20:30 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-28 11:30 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Max Nikulin <manikulin@gmail.com> - 2023-03-02 15:30 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-03-02 16:30 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Max Nikulin <manikulin@gmail.com> - 2023-03-03 16:20 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-03-03 16:30 +0100
            Re: Remove route '169.254.0.0/16 dev ovs-system' Reco <recoverym4n@enotuniq.net> - 2023-02-21 19:30 +0100
  Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-20 07:00 +0100
    Re: Remove route '169.254.0.0/16 dev ovs-system' <tomas@tuxteam.de> - 2023-02-20 08:30 +0100
      Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-20 08:50 +0100
        Re: Remove route '169.254.0.0/16 dev ovs-system' tomas@tuxteam.de - 2023-02-20 10:10 +0100
          Re: Remove route '169.254.0.0/16 dev ovs-system' rhkramer@gmail.com - 2023-02-20 15:30 +0100
            Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-20 16:10 +0100
  Re: Remove route  '169.254.0.0/16 dev ovs-system' The Wanderer <wanderer@fastmail.fm> - 2023-02-20 16:20 +0100

csiph-web