On Sunday, May 14, 2017 05:28:51 PM Michael Biebl wrote:
> Am 14.05.2017 um 17:02 schrieb Michael Biebl:
> > - debian/postfix.postinst: drop the postfix.service.d/override.conf and
> > make sure to remove that conffile on upgrades
>
> Seems due to some C&P failure I duplicated this point. I wanted
Hi guys.
I'm trying to unsubscribe this newsletter but I'm not getting success.
Can someone Help?
Many thanks in advance.
Em 14/05/2017 16:33, "Michael Biebl" escreveu:
> Am 14.05.2017 um 17:02 schrieb Michael Biebl:
> > - debian/postfix.postinst: drop the postfix.service.d/override.conf and
>
Am 14.05.2017 um 17:02 schrieb Michael Biebl:
> - debian/postfix.postinst: drop the postfix.service.d/override.conf and
> make sure to remove that conffile on upgrades
Seems due to some C&P failure I duplicated this point. I wanted to
clarify that postfix.service.d/override.conf is not actually a
Hi everyone,
a couple of comments inline
Am 08.05.2017 um 16:47 schrieb Bernhard Schmidt:
> Am 08.05.2017 um 16:18 schrieb Michael Biebl:
>
> Hi,
>
>> I'm missing context here. Can you go into more detail please? What exactly
>> is the question here?
>
> Sorry.
>
> https://bugs.debian.org/c
On May 10, 2017 12:32:59 PM EDT, Bernhard Schmidt wrote:
>Am 10.05.2017 um 17:46 schrieb Scott Kitterman:
>
>Hi Scott,
>
>>> I think network-online.target is unnecessary, as I'm not aware of
>any
>>> common postfix configurations that actually need network access to
>>> startup. At least the com
Am 10.05.2017 um 17:46 schrieb Scott Kitterman:
Hi Scott,
>> I think network-online.target is unnecessary, as I'm not aware of any
>> common postfix configurations that actually need network access to
>> startup. At least the common case of postfix or SQL the connection is
>
> If you specify an
On Tue, 9 May 2017 11:03:59 +0200 Bernhard Schmidt wrote:
> Am 08.05.2017 um 20:54 schrieb Scott Kitterman:
>
> Hi Scott,
>
>
> > In the postinst, if the debconf configuration is something other than none
or
> > local, we create an override file with After=network-online.target, which
is
>
Am 08.05.2017 um 20:54 schrieb Scott Kitterman:
Hi Scott,
> In the postinst, if the debconf configuration is something other than none or
> local, we create an override file with After=network-online.target, which is
> what I think is needed in most of these cases. I did not add it to the
>
Hi Andreas,
Am 08.05.2017 um 19:15 schrieb Andreas Henriksson:
> Hello Scott, Bernhard,
>
> On Sun, May 07, 2017 at 11:59:10PM -0400, Scott Kitterman wrote:
>> On Sunday, May 07, 2017 10:55:58 PM Bernhard Schmidt wrote:
>>> [...]
>> postfix.service has After=network.target. Why isn't that enough
Hello Scott, Bernhard,
On Sun, May 07, 2017 at 11:59:10PM -0400, Scott Kitterman wrote:
> On Sunday, May 07, 2017 10:55:58 PM Bernhard Schmidt wrote:
>> [...]
> postfix.service has After=network.target. Why isn't that enough (I have not
> had a lot of time to investigate this, but I have not giv
Am 08.05.2017 um 16:18 schrieb Michael Biebl:
Hi,
> I'm missing context here. Can you go into more detail please? What exactly is
> the question here?
Sorry.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854475 is about
several issues with postfix being started before the network is up,
f
I'm missing context here. Can you go into more detail please? What exactly is
the question here?
Regards,
Michael
Am 8. Mai 2017 16:07:12 MESZ schrieb Bernhard Schmidt :
>Am 08.05.2017 um 05:59 schrieb Scott Kitterman:
>> On Sunday, May 07, 2017 10:55:58 PM Bernhard Schmidt wrote:
>>> On Sat,
Am 08.05.2017 um 05:59 schrieb Scott Kitterman:
> On Sunday, May 07, 2017 10:55:58 PM Bernhard Schmidt wrote:
>> On Sat, Apr 15, 2017 at 11:42:37PM +0200, Marcus Jodorf wrote:
>>
>> Hi,
>>
>> is there anything I can do to get this fixed for Stretch? I can
>> pretty reliably reproduce this issue wit
On Sunday, May 07, 2017 10:55:58 PM Bernhard Schmidt wrote:
> On Sat, Apr 15, 2017 at 11:42:37PM +0200, Marcus Jodorf wrote:
>
> Hi,
>
> is there anything I can do to get this fixed for Stretch? I can
> pretty reliably reproduce this issue with all my upgraded Stretch
> systems, neither of them c
On Sat, Apr 15, 2017 at 11:42:37PM +0200, Marcus Jodorf wrote:
Hi,
is there anything I can do to get this fixed for Stretch? I can
pretty reliably reproduce this issue with all my upgraded Stretch
systems, neither of them can send mails after a reboot until Postfix is
getting restarted
An After=
On 04/15/2017 09:14 PM, Christian Schrötter wrote:
Are you sure network.target is enough?
network-online.target sounds much better for me.
Hi Christian,
No, I'm not really sure. Just tried it after finding #854475 thinking
that it might actually catch two problems at once.
Especially after
Are you sure network.target is enough?
network-online.target sounds much better for me.
--
With kind regards,
Christian Schrötter
Package: postfix
Version: 3.1.4-4
Followup-For: Bug #854475
Dear Maintainer,
I found a bug that is probably related to #854475 because it seems
also to be caused by postfix starting too early.
I have several systems where mail gets stuck in the queue with
"(Host or domain name not found. Name se
Package: postfix
Version: 3.1.4-4
Severity: important
Tags: patch
The file /lib/systemd/system/postfix@.service needs to have the line
"After=network.target" to make sure that all the network interfaces are raised
before it is started. Otherwise the startup will abort if Postfix is
configured to
19 matches
Mail list logo
