unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>, Alan Mackenzie <acm@colin2.muc.de>
Cc: bug-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: bug#1004: 23.0.60; Error visiting C files
Date: Fri, 26 Sep 2008 12:08:56 +0300	[thread overview]
Message-ID: <uk5czl1ef.fsf__148.834291803901$1222421491$gmane$org@gnu.org> (raw)
In-Reply-To: <kliqskkq9u.fsf@fencepost.gnu.org>

> Date: Thu, 25 Sep 2008 14:57:01 -0400
> Cc: Alan Mackenzie <acm@colin2.muc.de>
> 
> > Alan Mackenzie wrote:
> >
> >> I just noticed this one in a Usenet spool.  I don't seem to be
> >> subscribed to bug-gnu-emacs (I thought I was) at the moment, and
> >> nothing got forwarded to me.
> 
> My previous cc to you bounced with:
> 
>   acm@colin2.muc.de
>     SMTP error from remote mail server after RCPT TO:<acm@colin2.muc.de>:
>     host mx1.muc.de [193.149.48.15]: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)

So did mine:

   This report relates to a message you sent with the following header fields:

     Message-id: <umyhwl05j.fsf@gnu.org>
     Date: Thu, 25 Sep 2008 18:23:36 +0300
     From: Eli Zaretskii <eliz@gnu.org>
     To: Alan Mackenzie <acm@colin2.muc.de>, 1004@emacsbugs.donarmstrong.com
     Subject: Re: bug#1004: 23.0.60; Error visiting C files

   Your message cannot be delivered to the following recipients:

     Recipient address: acm@colin2.muc.de
     Reason: Remote SMTP server has rejected address
     Diagnostic code: smtp;553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)
     Remote system: dns;mx1.muc.de (TCP|84.95.2.1|16553|193.149.48.15|25) (mail.muc.de ESMTP)









      reply	other threads:[~2008-09-26  9:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 16:53 bug#1004: 23.0.60; Error visiting C files Eli Zaretskii
2008-09-19 18:05 ` martin rudalics
2008-09-20 10:15   ` Eli Zaretskii
2008-09-21 11:58     ` martin rudalics
2008-09-21 17:59       ` Eli Zaretskii
2008-09-21 19:31         ` Stefan Monnier
2008-09-22  0:26           ` Glenn Morris
2008-09-26 10:11       ` Eli Zaretskii
2008-09-26 13:13         ` martin rudalics
2008-09-26 13:42           ` Juanma Barranquero
2008-09-27  8:48             ` Eli Zaretskii
2008-09-27  8:48           ` Eli Zaretskii
2008-09-19 18:13 ` Glenn Morris
2008-09-19 18:25   ` Processed: " Emacs bug Tracking System
2008-09-20  9:14   ` Eli Zaretskii
     [not found]   ` <mailman.19601.1221904429.18990.bug-gnu-emacs@gnu.org>
2008-09-25 13:08     ` Alan Mackenzie
2008-09-25 15:23       ` Eli Zaretskii
2008-09-25 15:59       ` Glenn Morris
2008-09-25 18:57         ` Glenn Morris
2008-09-26  9:08           ` Eli Zaretskii [this message]

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='uk5czl1ef.fsf__148.834291803901$1222421491$gmane$org@gnu.org' \
    --to=eliz@gnu.org \
    --cc=1004@emacsbugs.donarmstrong.com \
    --cc=acm@colin2.muc.de \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@gnu.org \
    /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).