Steffen Nurpmeso:
> Steffen Nurpmeso wrote in
> <20220929213725.gar4l%stef...@sdaoden.eu>:
> |Viktor Dukhovni wrote in
> | :
> ||On Thu, Sep 29, 2022 at 07:25:48PM +0200, Steffen Nurpmeso wrote:
> ||> But on FreeBSD (only VM here for some years) on fresh install
> ||> i always have sendmail h
Viktor Dukhovni wrote in
:
|On Thu, Sep 29, 2022 at 07:25:48PM +0200, Steffen Nurpmeso wrote:
|> But on FreeBSD (only VM here for some years) on fresh install
|> i always have sendmail hang minutes upon startup (i interrupt to
|> come to login, which thankfully works), because it is of the
|>
Steffen Nurpmeso wrote in
<20220929213725.gar4l%stef...@sdaoden.eu>:
|Viktor Dukhovni wrote in
| :
||On Thu, Sep 29, 2022 at 07:25:48PM +0200, Steffen Nurpmeso wrote:
||> But on FreeBSD (only VM here for some years) on fresh install
||> i always have sendmail hang minutes upon startup (i inte
> On Sep 29, 2022, at 14:37, Viktor Dukhovni wrote:
>
> On Thu, Sep 29, 2022 at 01:33:58PM -0700, Dan Mahoney wrote:
>
>> I've always figured "if you configure your sendmail with both a client
>> cert and a server cert, you might as well use it, after all, you paid
>> for the thing".
>
> Wel
On Thu, Sep 29, 2022 at 01:33:58PM -0700, Dan Mahoney wrote:
> I've always figured "if you configure your sendmail with both a client
> cert and a server cert, you might as well use it, after all, you paid
> for the thing".
Well, to what end? What do you do you with any client certificate you
mi
Dan Mahoney:
> All,
>
> Using sendmail, I've been asking for client certs for a long time.
> I've always figured "if you configure your sendmail with both a
> client cert and a server cert, you might as well use it, after
> all, you paid for the thing". (This may have been the sunk-cost
> fallacy
All,
Using sendmail, I've been asking for client certs for a long time. I've always
figured "if you configure your sendmail with both a client cert and a server
cert, you might as well use it, after all, you paid for the thing". (This may
have been the sunk-cost fallacy back when I was paying
On 2022-09-29 at 11:14:12 UTC-0400 (Thu, 29 Sep 2022 17:14:12 +0200)
is rumored to have said:
strange
systemd's start command is
ExecStart=/usr/sbin/postfix start
.. and when trying to "postfix -vvv start" at shell, postfix starts!
Remove ALL of the 'v' flags. There's almost never an
On Thu, Sep 29, 2022 at 07:25:48PM +0200, Steffen Nurpmeso wrote:
> But on FreeBSD (only VM here for some years) on fresh install
> i always have sendmail hang minutes upon startup (i interrupt to
> come to login, which thankfully works), because it is of the
> opinion that the hostname is not val
Wietse Venema wrote in
<4mdf5130zdzj...@spike.porcupine.org>:
|Wietse Venema:
|> Viktor Dukhovni:
|>> On Thu, Sep 29, 2022 at 05:14:12PM +0200, michae...@rocketmail.com \
|>> wrote:
|>>
|>>> systemd's start command is
|>>>
|>>> ExecStart=/usr/sbin/postfix start
...
|>>> .. and when try
Wietse Venema:
> Viktor Dukhovni:
> > On Thu, Sep 29, 2022 at 05:14:12PM +0200, michae...@rocketmail.com wrote:
> >
> > > systemd's start command is
> > >
> > > ExecStart=/usr/sbin/postfix start
> > >
> > > .. and when trying to "postfix -vvv start" at shell, postfix starts!
> > >
> > > But tak
Viktor Dukhovni:
> On Thu, Sep 29, 2022 at 05:14:12PM +0200, michae...@rocketmail.com wrote:
>
> > systemd's start command is
> >
> > ExecStart=/usr/sbin/postfix start
> >
> > .. and when trying to "postfix -vvv start" at shell, postfix starts!
> >
> > But takes very, very long. So I'll search
On Thu, Sep 29, 2022 at 11:19:34AM -0400, Viktor Dukhovni wrote:
> On Thu, Sep 29, 2022 at 05:14:12PM +0200, michae...@rocketmail.com wrote:
>
> > systemd's start command is
> >
> > ExecStart=/usr/sbin/postfix start
> >
> > .. and when trying to "postfix -vvv start" at shell, postfix starts!
> >
On Thu, Sep 29, 2022 at 05:14:12PM +0200, michae...@rocketmail.com wrote:
> systemd's start command is
>
> ExecStart=/usr/sbin/postfix start
>
> .. and when trying to "postfix -vvv start" at shell, postfix starts!
>
> But takes very, very long. So I'll search for increasing timeouts for systemd
strange
systemd's start command is
ExecStart=/usr/sbin/postfix start
.. and when trying to "postfix -vvv start" at shell, postfix starts!
But takes very, very long. So I'll search for increasing timeouts for systemd
service units, next.
Thanks !!!
Am 29.09.22 um 16:45 schrieb PGNet De
# journalctl -r -u postfix
Sep 29 15:55:48 vserver systemd[1]: Failed to start Postfix Mail Transport
Agent.
Sep 29 15:55:48 vserver systemd[1]: postfix.service: Failed with result
'timeout'.
1st quick check is to exec the systemd service's start cmd manually at shell.
Postfix 3.5.9-5.9.2 on OpenSUSE Leap 15.4
Postfix does not start anymore after reboot today.
Unfortunately no a very detailed error msg logged:
# journalctl -r -u postfix
Sep 29 15:55:48 vserver systemd[1]: Failed to start Postfix Mail Transport
Agent.
Sep 29 15:55:48 vserver systemd[1]
17 matches
Mail list logo
