hmp@frc2.frc.ri.cmu.edu (Henning Pangels) (12/12/90)
We have experienced a similar problem here, indirectly, after upgrading from SunOS4.0.3 to SunOS4.1, on 3/60s and SparcStations. I say indirectly because it only occured when running xmh, which explicitly invokes send -push. In our case, however, the message got delivered with the To: and From: fields screwed up, so it may be different altogether. The workaround we found was to explicitly specify postproc: /usr/local/lib/post in .mh_profile. Somehow, I believe that the default is /usr/local/lib/spost, which seems to be at fault. Our investigation was by no means exhaustive, we just happened upon this way around it and left it at that. -Henning -- Henning Pangels Research Programmer Field Robotics Center hmp@frc2.frc.ri.cmu.edu Robotics Institute (412) 268-7088 Carnegie-Mellon University
victor@arnor.uucp (12/13/90)
I've had exactly the same problem. I'm running the version given
below on an IBM RT/PC running BSD 4.3. This caused real problems,
because I didn't realize that things weren't sent. Most of the time
when I resent things they really got resent, but once in a while it
required two or three attempts. Since getting rid of -push, I haven't
had any problems.
Here's the version of MH:
version: MH 6.7 #7[UCI] (irt) of Wed Aug 22 11:45:54 EDT 1990
options: [BSD42] [BSD43] [BIND] [TTYD] [DUMB] [NTOHLSWAP] [DBM]
[NETWORK] [RPATHS] [MHE] [MHRC] [SBACKUP='"#"'] [SENDMTS]
[SMTP]
--
Victor S. Miller (victor@ibm.com)
itinerant Number Theorist
IBM, TJ Watson Research Centerroland@ai.mit.edu (Roland McGrath) (12/13/90)
In article <VICTOR.90Dec12113528@irt.watson.ibm.com> victor@arnor.uucp writes:
I've had exactly the same problem. I'm running the version given
below on an IBM RT/PC running BSD 4.3. This caused real problems,
because I didn't realize that things weren't sent. Most of the time
when I resent things they really got resent, but once in a while it
required two or three attempts. Since getting rid of -push, I haven't
had any problems.
Here's the version of MH:
version: MH 6.7 #7[UCI] (irt) of Wed Aug 22 11:45:54 EDT 1990
options: [BSD42] [BSD43] [BIND] [TTYD] [DUMB] [NTOHLSWAP] [DBM]
[NETWORK] [RPATHS] [MHE] [MHRC] [SBACKUP='"#"'] [SENDMTS]
[SMTP]
We've definitely got the same problem. So it's not my imagination.
Anyone have a fix?
Thanks,
Roland
--
Roland McGrath
Free Software Foundation, Inc.
roland@ai.mit.edu, uunet!ai.mit.edu!rolandroland@ai.mit.edu (Roland McGrath) (12/13/90)
On an HP9000s370 (68030/68882) running mt Xinu 4.3 BSD (MORE/bsd).
version: MH 6.7 #3[UCI] (churchy.ai.mit.edu) of Mon Oct 15 00:21:14 EDT 1990
options: [BSD42] [ATZ] [BERK] [BIND] [BSD43] [MHE] [OVERHEAD] [RPATHS]
[SBACKUP='"#"'] [WHATNOW] [ZONEINFO] [TZNAME] [SENDMTS] [SMTP]
When I have:
send: -push
in ~/.mh_profile, sometimes things don't get sent. They just sit in +drafts.
If I don't use -push, it always works. Usually if I send them again (even with
-push), it works.
Has anyone seen this problem before or have any idea what it might be?
Thanks,
Roland
--
Roland McGrath
Free Software Foundation, Inc.
roland@ai.mit.edu, uunet!ai.mit.edu!rolandziegast@ENG.UMD.EDU (Eric Ziegast) (12/14/90)
I haven't heard or seen any such problems here regarding send -push.
I use it all of the time. Here are the options I used with each OS.
version: MH 6.7 #N[UCI] (HOSTNAME) of DATE
Ultrix 4.0 & 4.0.1 (DEC 3100):
options: [BIND] [BSD42] [BSD43] [ISI] [MHE] [MHRC] [NTOHLSWAP] [RPATHS]
[ZONEINFO] [FOLDPROT='"0700"'] [MSGPROT='"0600"']
[SBACKUP='"#"'] [SENDMTS]
SunOS 4.1 (SUN3 & SUN4):
options: [ATZ] [BIND] [BSD42] [BSD43] [SUN40] [ISI] [MHE] [MHRC]
[NTOHLSWAP] [RPATHS] [TZNAME] [ZONEINFO] [FOLDPROT='"0700"']
[MSGPROT='"0600"'] [SBACKUP='"#"'] [TYPESIG='void'] [SENDMTS]
SunOS 4.0.3 (SUN3 & SUN4):
options: [ATZ] [BIND] [BSD42] [BSD43] [SUN40] [ISI] [MHE] [MHRC]
[NTOHLSWAP] [RPATHS] [TZNAME] [ZONEINFO] [FOLDPROT='"0700"']
[MSGPROT='"0600"'] [SBACKUP='"#"'] [TYPESIG='void'] [SENDMTS]
We use V5.61 of Sendmail as the MTS.
I've also compiled it on an IBM/RT (BSD 4.3) just fine using the High C
(/bin/hc) compiler. I don't know how well it works because Sendmail has
not yet been installed on that machine.
Since there is no Sendmail (yet), I get the following:
What now? send -push
epoxy-20: ziegast: post: unexpected response; [BHST] no pipe opened
So I assume that it at least makes it to the Sendmail pipe. I've been
assured by a sys-admin here that once he puts sendmail on the RT's, that
it should work just like our other architectures.
BSD 4.3 (IBM/RT):
options: [BIND] [BSD42] [BSD43] [ISI] [MHE] [MHRC] [NTOHLSWAP] [RPATHS]
[FOLDPROT='"0700"'] [MSGPROT='"0600"'] [SBACKUP='"#"']
[SENDMTS]
________________________________________________________________________
Eric W. Ziegast, University of Merryland, Engineering Computing Services
ziegast@eng.umd.edu - Eric@(301.405.3689)smoot@woodstock.berkeley.edu (Stephen R. Smoot) (12/14/90)
Well, I might as well throw in $0.02. I've had: $ send -push -forward -draftfolder drafts -draft N disappear with no error, delete the message, and not send it. It happened in batches (Ie, write ten messages, send them all, none ever arrive). The system I'm using is: Ultrix-32 V3.1 (Rev. 9) System #8 And all options are the defaults, 'cept as noted above. -s