unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Merritt <dmerritt@gmail.com>
Subject: Re: Undelivered Mail Returned to Sender
Date: Sat, 17 Dec 2005 19:22:26 -0400	[thread overview]
Message-ID: <3969c49e0512171522g3f96c864t9b664349d58a830a@mail.gmail.com> (raw)
In-Reply-To: <20051217231841.C73762B437@mccoy.tardis.ed.ac.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1799 bytes --]

Mail to the listed maintainer of the Emacs Windows documentation is
bouncing. My original message to him is included below.

Daniel

On 12/17/05, Mail Delivery System <MAILER-DAEMON@tardis.ed.ac.uk> wrote:
>
> This is the Postfix program at host mccoy.tardis.ed.ac.uk.
>
> I'm sorry to have to inform you that your message could not be
> be delivered to one or more recipients. It's attached below.
>
> For further assistance, please send mail to <postmaster>
>
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
>
>                        The Postfix program
>
> <skx@tardis.ed.ac.uk>: temporary failure. Command output: maildrop: Unable
> to
>    open mailbox.
>
>
> Final-Recipient: rfc822; skx@tardis.ed.ac.uk
> Action: failed
> Status: 4.0.0
> Diagnostic-Code: X-Postfix; temporary failure. Command output: maildrop:
> Unable
>    to open mailbox.
>
>
>
> ---------- Forwarded message ----------
> From: Daniel Merritt <dmerritt@gmail.com>
> To: skx@tardis.ed.ac.uk
> Date: Mon, 12 Dec 2005 18:48:15 -0400
> Subject: Emacs documentation
> Mr. Kemp,
>
> http://www.gnu.org/software/emacs/windows/faq2.html contains the
> following:
>  The latest source distribution can be found in
> http://ftp.gnu.org/gnu/windows/emacs/latest. It is distributed in two
> formats: one large gzipped tar file (emacs*.tar.gz), and a collection of
> smaller zip files that can be copied to 1.44 Mbyte floppies
> (em-src-_?.zip).
>
> http://ftp.gnu.org/gnu/windows/emacs/latest is a dead link, and presumably
> should be http://ftp.gnu.org/gnu/emacs/windows/ or something like it.
>
> Thanks for maintaining the documentation. I expect it must be a thankless
> job at times.
>
> Daniel
>
>

[-- Attachment #1.2: Type: text/html, Size: 3180 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
bug-gnu-emacs mailing list
bug-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs

       reply	other threads:[~2005-12-17 23:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051217231841.C73762B437@mccoy.tardis.ed.ac.uk>
2005-12-17 23:22 ` Daniel Merritt [this message]
2005-05-24  8:55 Undelivered Mail Returned to Sender Mail Delivery System
  -- strict thread matches above, loose matches on Subject: below --
2004-06-19  0:11 Mail Delivery System
2004-06-18 23:34 Mail Delivery System

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=3969c49e0512171522g3f96c864t9b664349d58a830a@mail.gmail.com \
    --to=dmerritt@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).