On Fri, 9 Oct 2015 19:41:42 +0200, Gilles Chehade said:
| EHLO package maintainers,
| It would be nice if we had a list and-or IRC channel to communicate with
| you and synchronize before releases.
| Should I setup something ?
Sure, although I think there was an IRC channel
On Sat, Oct 10, 2015 at 08:20:47PM +0100, Raf Czlonka wrote:
> On Sat, Oct 10, 2015 at 04:28:42PM BST, Allyn Bottorff wrote:
> > >
> > > Can you please post your smtpd.conf?
>
> That was also meant to be my next question :^)
>
> > > Maybe this has something to do with the name chosen for the
>
> Because 'network.target' doesn't actually wait for any of the interfaces
> to be up - what you want is 'network-online.target'[0].
>
> Regards,
>
> Raf
>
> [0] https://wiki.freedesktop.org/www/Software/systemd/NetworkTarget/
Thanks, I wasn't aware of that. This hasn't solved the problem,
On Sat, Oct 10, 2015 at 04:28:42PM BST, Allyn Bottorff wrote:
> >
> > Can you please post your smtpd.conf?
That was also meant to be my next question :^)
> > Maybe this has something to do with the name chosen for the
> > listening interface.
>
> # This is the smtpd server system-wide
>
> Can you please post your smtpd.conf?
>
> Maybe this has something to do with the name chosen for the
> listening interface.
# This is the smtpd server system-wide configuration file.
# See smtpd.conf(5) for more information.
# To accept external mail, replace with: listen on all
listen on
On Sat, 10 Oct 2015 07:44:51 -0700, Allyn Bottorff
wrote:
Because 'network.target' doesn't actually wait for any of the interfaces
to be up - what you want is 'network-online.target'[0].
Regards,
Raf
[0] https://wiki.freedesktop.org/www/Software/systemd/NetworkTarget/
On Sat, Oct 10, 2015 at 03:44:51PM BST, Allyn Bottorff wrote:
> > Because 'network.target' doesn't actually wait for any of the
> > interfaces to be up - what you want is 'network-online.target'[0].
> >
> > Regards,
> >
> > Raf
> >
> > [0]
On 2015-10-09 Fri 19:40 PM |, Gilles Chehade wrote:
>
> The report taught us a few things and helped us spot weak points that we
> will work on hardening to make sure. I'll summarize a bit,
MTAs could be the most complex daemon commonly deployed.
For a very small, part time team, this is a huge