emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: emacs-orgmode@gnu.org
Cc: nicholas.dokos@hp.com
Subject: Delays in mailing list server?
Date: Thu, 16 Jun 2011 11:27:58 -0400	[thread overview]
Message-ID: <11296.1308238078@alphaville.dokosmarshall.org> (raw)

I replied to Fil earlier through the list (not sure if the direct reply
to him got there quickly) and it took a long time for the round-trip
through the list server to get back to me:

| ...
| Received: from localhost ([::1]:59909 helo=lists.gnu.org)
| 	by lists.gnu.org with esmtp (Exim 4.71)
| 	(envelope-from <emacs-orgmode-bounces+nicholas.dokos=hp.com@gnu.org>)
| 	id 1QXDNL-0008Ik-MT
| 	for nicholas.dokos@hp.com; Thu, 16 Jun 2011 10:16:51 -0400
| Received: from eggs.gnu.org ([]:35691)
| 	by lists.gnu.org with esmtp (Exim 4.71)
| 	(envelope-from <nick@dokosmarshall.org>) id 1QXCnI-0006kD-J9
| 	for emacs-orgmode@gnu.org; Thu, 16 Jun 2011 09:39:38 -0400
| ...

It looks as if it bounced around lists.gnu.org for 36 minutes or so.
Anybody else seeing these delays?


             reply	other threads:[~2011-06-16 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 15:27 Nick Dokos [this message]
2011-06-16 20:32 ` Delays in mailing list server? Sebastien Vauban
2011-06-17  3:09   ` Nick Dokos

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=11296.1308238078@alphaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \


* 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.
Code repositories for project(s) associated with this public inbox


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 read-only IMAP folder(s) and NNTP newsgroup(s).