On 11/03/2016 01:06 AM, Brian Inglis wrote:
> On 2016-11-02 09:47, Gerry Reno wrote:
>> Is there some automated way I can stop Windows 10 updates from
>> continuously causing these fork retry no child process issues after
>> every damn update?
>> We use an application based on Cygwin (2.6.0) on our
On 2016-11-02 09:47, Gerry Reno wrote:
Is there some automated way I can stop Windows 10 updates from
continuously causing these fork retry no child process issues after
every damn update?
We use an application based on Cygwin (2.6.0) on our clients that
gets wrecked everytime a Windows 10 update
On 11/02/2016 01:31 PM, Evgeny Grin wrote:
> On 02.11.2016 18:47, Gerry Reno wrote:
>> Is there some automated way I can stop Windows 10 updates from continuously
>> causing these fork retry no child process
>> issues after every damn update?
>> We use an application based on Cygwin (2.6.0) on our
On Tue, Nov 1, 2016 at 7:41 AM, Jon Turney wrote:
> On 01/11/2016 13:04, Keith Christian wrote:
>>
>> On Sat, Oct 29, 2016 at 12:17 PM, Keith Christian wrote:
>>>
>>> While I use a few X11 packages, I find that I don't need the KDE or
>>> GNOME categories.
>>>
>>> Are the command line switches to
On 02.11.2016 18:47, Gerry Reno wrote:
> Is there some automated way I can stop Windows 10 updates from continuously
> causing these fork retry no child process
> issues after every damn update?
> We use an application based on Cygwin (2.6.0) on our clients that gets
> wrecked everytime a Windows
Is there some automated way I can stop Windows 10 updates from continuously
causing these fork retry no child process
issues after every damn update?
We use an application based on Cygwin (2.6.0) on our clients that gets wrecked
everytime a Windows 10 update occurs.
The users have no idea about C
On 11/2/2016 2:13 PM, cyg Simple wrote:
On 11/2/2016 9:04 AM, Eric Blake wrote:
On 11/02/2016 05:43 AM, Andrey ``Bass'' Shcheglov wrote:
Remote host said: 550-5.7.1 Unauthenticated email from vanav.org is not
accepted due to domain's > 550-5.7.1 DMARC policy. Please contact the
administrator
On 2016.11.02 09:04, Eric Blake wrote:
On 11/02/2016 05:43 AM, Andrey ``Bass'' Shcheglov wrote:
Remote host said: 550-5.7.1 Unauthenticated email from vanav.org is
not accepted due to domain's > 550-5.7.1 DMARC policy. Please
contact the administrator of vanav.org domain if > 550-5.7.1 this
On 11/2/2016 9:04 AM, Eric Blake wrote:
> On 11/02/2016 05:43 AM, Andrey ``Bass'' Shcheglov wrote:
>
>> Remote host said: 550-5.7.1 Unauthenticated email from vanav.org is not
>> accepted due to domain's > 550-5.7.1 DMARC policy. Please contact the
>> administrator of vanav.org domain if > 550-5.7
On 11/2/2016 6:43 AM, Andrey ``Bass'' Shcheglov wrote:
>
> Hello,
>
> Yesterday, I've received the warning message saying emails to gmail
> servers are bouncing:
>> Return-Path: <> > Received: (qmail 24363 invoked for bounce); 20 Oct 2016
>> 21:51:31
> - > Date: 20 Oct 2016 21:51:31 - >
On 11/02/2016 05:43 AM, Andrey ``Bass'' Shcheglov wrote:
> Remote host said: 550-5.7.1 Unauthenticated email from vanav.org is not
> accepted due to domain's > 550-5.7.1 DMARC policy. Please contact the
> administrator of vanav.org domain if > 550-5.7.1 this was a legitimate
> mail. Please visit >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Yesterday, I've received the warning message saying emails to gmail
servers are bouncing:
> Return-Path: <> > Received: (qmail 24363 invoked for bounce); 20 Oct 2016
> 21:51:31
- > Date: 20 Oct 2016 21:51:31 - > From:
mailer-dae...@s
12 matches
Mail list logo
