ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@bittext.nl>
Subject: Re: Cron <context@zapf> /var/www/aanhet.net/context/bin/cron/context-mirror
Date: Wed, 7 Sep 2022 17:13:28 +0200	[thread overview]
Message-ID: <FD4ED6DB-52B2-428D-8BC0-52635ED46B60@bittext.nl> (raw)
In-Reply-To: <f8ea5157-16e8-5fcc-8b0d-e3f2543477b6@fiee.net>

As Hraban said: it is my script that checks for new ConTeXt uploads by Hans, which currently cannot connect to Hans’ server. 

Usually that is because Hans is reconfiguring something in his internal network at Pragma, and it will eventually sort itself out.

Best wishes,
Taco

> On 7 Sep 2022, at 16:51, Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl> wrote:
> 
> Don’t panic, all is well with the list. Nothing to do, nothing to see here.
> 
> Taco included the mailing list in the message recipients of the cron demon in order to get notified of ConTeXt updates.
> Seems like there is a connection problem with the pragma servers, but it doesn’t affect the list.
> 
> Hraban
> 
> Am 07.09.22 um 16:32 schrieb Ursula Hermann via ntg-context:
>> I got the same Mail.
>> Uschi Hermann
>> -----Ursprüngliche Nachricht-----
>> Von: ntg-context <ntg-context-bounces@ntg.nl> Im Auftrag von Jeong Dal via ntg-context
>> Gesendet: Mittwoch, 07. September 2022 16:27
>> An: mailing list for ConTeXt users <ntg-context@ntg.nl>
>> Cc: Jeong Dal <haksan@me.com>
>> Betreff: Re: [NTG-context] Cron <context@zapf> /var/www/aanhet.net/context/bin/cron/context-mirror
>> Dear Taco,
>> The following mail came every hour since a few days ago.
>> But I don’t get any other mail from the list.
>> I think that there is something wrong between my mail system and the server.
>> However, I don’t know how to solve it.
>> Would you please tell me what to do?
> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : https://contextgarden.net
> ___________________________________________________________________________________

— 
Taco Hoekwater              E: taco@bittext.nl
genderfluid (all pronouns)



___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-09-07 15:13 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 12:03 Cron Daemon via ntg-context
2022-09-07 14:27 ` Jeong Dal via ntg-context
2022-09-07 14:32   ` Ursula Hermann via ntg-context
2022-09-07 14:51     ` Henning Hraban Ramm via ntg-context
2022-09-07 15:13       ` Taco Hoekwater via ntg-context [this message]
2022-09-07 16:02         ` Hans Hagen via ntg-context
  -- strict thread matches above, loose matches on Subject: below --
2023-04-11 21:01 Cron Daemon via ntg-context
2023-04-11 18:01 Cron Daemon via ntg-context
2023-04-11 17:01 Cron Daemon via ntg-context
2023-04-11 16:01 Cron Daemon via ntg-context
2023-04-11 15:01 Cron Daemon via ntg-context
2023-04-01  9:01 Cron Daemon via ntg-context
2023-03-20 17:01 Cron Daemon via ntg-context
2023-03-20 16:01 Cron Daemon via ntg-context
2023-03-10 23:01 Cron Daemon via ntg-context
2023-03-10 12:01 Cron Daemon via ntg-context
2023-03-09 12:01 Cron Daemon via ntg-context
2023-03-06 23:01 Cron Daemon via ntg-context
2023-03-06 15:01 Cron Daemon via ntg-context
2023-02-23 21:01 Cron Daemon via ntg-context
2023-02-14 17:01 Cron Daemon via ntg-context
2023-02-07 19:01 Cron Daemon via ntg-context
2023-02-07 21:19 ` Giulio Bertellini via ntg-context
2023-02-06 18:01 Cron Daemon via ntg-context
2023-01-26 18:01 Cron Daemon via ntg-context
2023-01-24 14:01 Cron Daemon via ntg-context
2023-01-23 23:01 Cron Daemon via ntg-context
2023-01-15 14:01 Cron Daemon via ntg-context
2023-01-13 12:01 Cron Daemon via ntg-context
2023-01-05 19:01 Cron Daemon via ntg-context
2023-01-04 11:01 Cron Daemon via ntg-context
2022-12-29 14:01 Cron Daemon via ntg-context
2022-12-27 23:01 Cron Daemon via ntg-context
2022-12-27 21:01 Cron Daemon via ntg-context
2022-12-27 17:01 Cron Daemon via ntg-context
2022-12-22 22:01 Cron Daemon via ntg-context
2022-12-21 17:01 Cron Daemon via ntg-context
2022-12-15 18:01 Cron Daemon via ntg-context
2022-12-15  1:03 Cron Daemon via ntg-context
2022-12-09 17:01 Cron Daemon via ntg-context
2022-12-07 21:01 Cron Daemon via ntg-context
2022-12-05 22:01 Cron Daemon via ntg-context
2022-12-01 13:01 Cron Daemon via ntg-context
2022-11-29  0:01 Cron Daemon via ntg-context
2022-11-28 23:01 Cron Daemon via ntg-context
2022-11-18 13:01 Cron Daemon via ntg-context
2022-11-14 23:01 Cron Daemon via ntg-context
2022-10-22 10:01 Cron Daemon via ntg-context
2022-10-21 20:01 Cron Daemon via ntg-context
2022-10-15 10:01 Cron Daemon via ntg-context
2022-10-14  9:01 Cron Daemon via ntg-context
2022-09-16 14:01 Cron Daemon via ntg-context
2022-09-16 13:01 Cron Daemon via ntg-context
2022-09-11 19:01 Cron Daemon via ntg-context
2022-09-10  1:01 Cron Daemon via ntg-context
2022-09-10  7:49 ` Henning Hraban Ramm via ntg-context
2022-09-10  9:12   ` Hans Hagen via ntg-context
2022-09-10  9:32     ` Henning Hraban Ramm via ntg-context
2022-09-09 20:03 Cron Daemon via ntg-context
2022-09-09  0:03 Cron Daemon via ntg-context
2022-09-07 14:03 Cron Daemon via ntg-context
2022-09-07 13:03 Cron Daemon via ntg-context
2022-09-07 11:03 Cron Daemon via ntg-context
2022-09-07 10:03 Cron Daemon via ntg-context
2022-09-06  9:01 Cron Daemon via ntg-context
2022-09-06  8:03 Cron Daemon via ntg-context
2022-08-25 18:01 Cron Daemon via ntg-context
2022-08-25 16:01 Cron Daemon via ntg-context
2022-08-16  3:03 Cron Daemon via ntg-context
2022-08-05 16:01 Cron Daemon via ntg-context
2022-08-05 10:01 Cron Daemon via ntg-context
2022-08-01 19:01 Cron Daemon via ntg-context
2022-07-27 16:01 Cron Daemon via ntg-context
2022-07-24 11:01 Cron Daemon via ntg-context
2022-07-24 13:36 ` Mikael Sundqvist via ntg-context
2022-07-27  5:03   ` Aditya Mahajan via ntg-context
2022-07-27  7:32     ` Hans Hagen via ntg-context
2022-07-29  7:36       ` Jeong Dal via ntg-context
2022-07-27 16:04     ` Hans Hagen via ntg-context
2022-07-06 21:01 Cron Daemon via ntg-context
2022-06-25 17:03 Cron Daemon via ntg-context
2022-06-04 12:01 Cron Daemon via ntg-context
2022-06-04 10:01 Cron Daemon via ntg-context
2022-05-22 18:01 Cron Daemon via ntg-context
2022-05-11 10:01 Cron Daemon via ntg-context
2022-05-11  8:01 Cron Daemon via ntg-context
2022-05-10 17:01 Cron Daemon via ntg-context
2022-05-09 16:01 Cron Daemon via ntg-context
2022-05-02 15:01 Cron Daemon via ntg-context
2022-05-03  7:13 ` Taco Hoekwater via ntg-context
2022-05-03  8:35   ` Rudolf Bahr via ntg-context

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FD4ED6DB-52B2-428D-8BC0-52635ED46B60@bittext.nl \
    --to=ntg-context@ntg.nl \
    --cc=taco@bittext.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).