[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Returned mail: Local configuration error




Nolan Darilek - please fix your mail configuration.  Your return
address is shown as "nolan@localhost.vassar.edu", but mail addressed
there bounces.  (For everyone else - sorry about the extra traffic.)

                           - Jim Van Zandt


>Date: Tue, 31 Mar 1998 21:53:22 -0500 (EST)
>From: Mail Delivery Subsystem <MAILER-DAEMON@mercury.mv.net>
>Content-Type: multipart/report; report-type=delivery-status;
>	boundary="VAA19150.891399202/mercury.mv.net"
>Auto-Submitted: auto-generated (failure)
>
>This is a MIME-encapsulated message
>
>--VAA19150.891399202/mercury.mv.net
>
>The original message was received at Tue, 31 Mar 1998 21:53:05 -0500 (EST)
>from root@vanzandt.mv.com [207.22.8.81]
>
>   ----- The following addresses had permanent fatal errors -----
><nolan@localhost.vassar.edu>
>
>   ----- Transcript of session follows -----
>553 localhost.vassar.edu. config error: mail loops back to me (MX problem?)
>554 <nolan@localhost.vassar.edu>... Local configuration error
>
>--VAA19150.891399202/mercury.mv.net
>Content-Type: message/delivery-status
>
>Reporting-MTA: dns; mercury.mv.net
>Received-From-MTA: dns; vanzandt.mv.com
>Arrival-Date: Tue, 31 Mar 1998 21:53:05 -0500 (EST)
>
>Final-Recipient: rfc822; nolan@localhost.vassar.edu
>Action: failed
>Status: 5.5.0
>Remote-MTA: dns; localhost.vassar.edu
>Last-Attempt-Date: Tue, 31 Mar 1998 21:53:11 -0500 (EST)
>
>--VAA19150.891399202/mercury.mv.net
>Content-Type: message/rfc822
>
>Return-Path: jrv@vanzandt.mv.com
>Received: from vanzandt.mv.com (root@vanzandt.mv.com [207.22.8.81]) by mercury.mv.net (8.8.8/mem-971025) with ESMTP id VAA19139; Tue, 31 Mar 1998 21:53:05 -0500 (EST)
>Received: by vanzandt.mv.com
>	via sendmail with stdio
>	id <m0yKD61-0006IiC@vanzandt.mv.com> (Debian Smail3.2.0.101)
>	for nolan@localhost.vassar.edu; Tue, 31 Mar 1998 21:17:45 -0500 (EST) 
>Message-Id: <m0yKD61-0006IiC@vanzandt.mv.com>
>Date: Tue, 31 Mar 1998 21:17:45 -0500 (EST)
>From: "James R. Van Zandt" <jrv@vanzandt.mv.com>
>To: nolan@localhost.vassar.edu
>CC: emacspeak@cs.vassar.edu, jrv@vanzandt.mv.com
>In-reply-to: <m0yK9c9-001wwWC@localhost> (message from Nolan Darilek on Tue,
>	31 Mar 1998 16:34:41 -0600 (CST))
>Subject: Re: Emacspeak problems with emacs20
>References:  <m0yK9c9-001wwWC@localhost>
>
>
>Nolan -
>
>You write "I am running the Debian packages for emacs20 and emacspeak
>7.0"
>
>I am glad to hear someone is taking advantage of the Debian packages.
>You did not quote the version numbers of your packages.  The most
>recent ones are emacspeak_7.0-4 and emacs20_20.2-4.  If yours are
>older, I suggest you upgrade.  Unfortunately, I do not know that any
>relevant changes have been made in either package.
>
>If you kill emacs and restart, does the problem go away for another
>twenty minutes?
>
>Are you using a DECtalk Express?  What version of firmware? (use M-x
>emacspeak-dtk-speak-version, or C-e d V)
>
>I also suggest you record your disk usage (with "df") and memory usage
>(with "free"), both just after starting emacs and after the problem
>appears.  You could also record the emacs process statistics with "ps
>alx|grep emacs".
>
>                              - Jim Van Zandt
>
>
>--VAA19150.891399202/mercury.mv.net--
>
>
>


Emacspeak Files | Subscribe | Unsubscribe