[27746] in Athena Bugs
No subject found in mail header
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Thu Jan 31 14:19:21 2019
From: Jonathon Weiss <jweiss@mit.edu>
To: <sarac@mit.edu>
In-Reply-To: Your message of "Thu, 31 Jan 2019 13:19:34 -0500."
<201901311819.x0VIJZS5007754@outgoing.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <16948.1548962357.1@neural-implant>
Date: Thu, 31 Jan 2019 14:19:17 -0500
Message-ID: <20190131t141917p16951damsjw@neural-implant>
Content-Transfer-Encoding: 8bit
Cc: bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
Hi Sara,
This is a problem with the upgraded dialups that were deployed yesterday. I'm aware, and working on the problem, and will add you to the tracking ticket I have going.
If and Debathena devs care, I believe this is identical to http://athena10.mit.edu/trac/ticket/1585
Thanks for the report, and sorry for the inconvenience.
Jonathon
Jonathon Weiss <jweiss@mit.edu>
MIT/IS&T/Cloud Platforms
<sarac@mit.edu> wrote:
> System name: ten-thousand-dollar-bill
> Type: x86_64
> Display type: VMware SVGA II Adapter
>
> Shell: /bin/athena/tcsh
> Window manager: n/a
> Desktop session: n/a
>
> 1) What were you trying to do?
>
> Send mail using nmh (using comp, but any method fails).
>
>
> 2) What happened?
>
> comp
> What now? s
> /usr/lib/mh/post: 13: exec: /usr/lib/mh/nmh/post: not found
> send: message not delivered to anyone
>
>
> 3) What should have happened?
>
> It should have sent mail.
>
> /usr/lib/mh/post is a symlink:
>
> ls -l /usr/lib/mh/*post*
> lrwxrwxrwx 1 root root 14 Aug 6 16:27 /usr/lib/mh/post -> post.debathena
> lrwxrwxrwx 1 root root 5 Sep 29 2013 /usr/lib/mh/post.debathena -> spost
> -rwxr-xr-x 1 root root 170440 Feb 28 2018 /usr/lib/mh/post.debathena-orig
> -rwxr-xr-x 1 root root 388 Feb 28 2018 /usr/lib/mh/spost
>
> to a bash script which references /usr/lib/mh/nmh/post which does not exist.
>
> If I put:
>
> postproc: /usr/lib/mh/post.debathena-orig
>
> in my .mh_profile, sending works again as long as I put a From: line
> in my mail manually.
>
>
> 4) Does this problem happen only on this workstation, or other workstations?
>
> It happens on all dialups I've used in the last few days (probably
> coinciding with the upgrade). Haven't been to campus to try a cluster
> machine.
>
> 5) If you were following instructions, please include the URL or a
> description of the documentation:
> (e.g. a "problem set for 18.03" or http://ist.mit.edu)
>
> n/a
