public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
* [Mailer-Daemon@nevyn.them.org: Mail delivery failed: returning message to sender]
@ 2005-11-14 15:16 Daniel Jacobowitz
  2005-11-14 15:21 ` Christopher Faylor
  0 siblings, 1 reply; 2+ messages in thread
From: Daniel Jacobowitz @ 2005-11-14 15:16 UTC (permalink / raw)
  To: overseers

Still no idea what causes this?  It seems to be happening more often...


----- Forwarded message from Mail Delivery System <Mailer-Daemon@nevyn.them.org> -----

Date: Mon, 14 Nov 2005 08:48:51 -0500
From: Mail Delivery System <Mailer-Daemon@nevyn.them.org>
Subject: Mail delivery failed: returning message to sender
To: drow@nevyn.them.org

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  gdb@sources.redhat.com
    SMTP error from remote mail server after HELO nevyn.them.org:
    host sources.redhat.com [209.132.176.174]: 500 Unrecognized command

------ This is a copy of the message, including all the headers. ------

Return-path: <drow@nevyn.them.org>
Received: from drow by nevyn.them.org with local (Exim 4.54)
	id 1Ebegz-0005bh-6x; Mon, 14 Nov 2005 08:48:17 -0500
Date: Mon, 14 Nov 2005 08:48:17 -0500
From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sources.redhat.com
Subject: Re: RFC: GDB as a loader 3/3: --eval-command option
Message-ID: <20051114134816.GA21373@nevyn.them.org>
Mail-Followup-To: Andrew STUBBS <andrew.stubbs@st.com>,
	Eli Zaretskii <eliz@gnu.org>, gdb@sources.redhat.com
References: <4354DD31.3020809@st.com> <436B4B87.1060801@st.com> <20051105025059.GB20989@nevyn.them.org> <uzmojtnv8.fsf@gnu.org> <436F610C.5080508@st.com> <uzmogdw4w.fsf@gnu.org> <437085AF.9080602@st.com> <20051113173801.GE1945@nevyn.them.org> <43787849.6060303@st.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43787849.6060303@st.com>
User-Agent: Mutt/1.5.8i

On Mon, Nov 14, 2005 at 11:43:05AM +0000, Andrew STUBBS wrote:
> Daniel Jacobowitz wrote:
> >On Tue, Nov 08, 2005 at 11:02:07AM +0000, Andrew STUBBS wrote:
> >
> >>Eli Zaretskii wrote:
> >>
> >>>>Should I add a 6.5 section for my changes?
> >>>
> >>>
> >>>Only if we decide not to commit them to the branch as well.
> >>>Personally, I don't see why not have them in 6.4, they cannot possibly
> >>>harm anything.
> >>
> >>Anybody object to my putting --return-child-result (including the header 
> >>file update) and --eval-command into 6.4?
> >>
> >>Anybody else in favour?
> >
> >
> >Sounds reasonable to me.
> >
> 
> Is that an 'OK, go ahead', or just part of the discussion?

Please go ahead.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


----- End forwarded message -----

-- 
Daniel Jacobowitz
CodeSourcery, LLC

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [Mailer-Daemon@nevyn.them.org: Mail delivery failed: returning message to sender]
  2005-11-14 15:16 [Mailer-Daemon@nevyn.them.org: Mail delivery failed: returning message to sender] Daniel Jacobowitz
@ 2005-11-14 15:21 ` Christopher Faylor
  0 siblings, 0 replies; 2+ messages in thread
From: Christopher Faylor @ 2005-11-14 15:21 UTC (permalink / raw)
  To: overseers

On Mon, Nov 14, 2005 at 09:46:37AM -0500, Daniel Jacobowitz wrote:
>Still no idea what causes this?  It seems to be happening more often...

You'd think you'd take the hint by now...  :-)

I'm testing a new version of qpsmtpd with the hopes that it will solve
the problem.

cgf

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-11-14 14:48 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-11-14 15:16 [Mailer-Daemon@nevyn.them.org: Mail delivery failed: returning message to sender] Daniel Jacobowitz
2005-11-14 15:21 ` Christopher Faylor

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