[Top][All Lists]

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

Re: [Nmh-workers] masquerade settings & spost

From: David Levine
Subject: Re: [Nmh-workers] masquerade settings & spost
Date: Mon, 27 Feb 2012 20:49:12 -0500

Bill wrote:

> David Levine <address@hidden> writes:
> >> >I've had this in my .mh_profile almost since I started using nmh:
> >> >
> >> >  postproc: /usr/libexec/nmh/spost
> >>
> >> Wow, how did you ever know to use it?
> >
> > That's in the FAQ.  Should be removed, I think.
> There seemed to be some legitimate reasons for its use. Even I used
> spost for some time. There's been few questions that I've completely
> removed.

I agree.  I'm not arguing for removal of spost from nmh.

The problem is where the mention of spost appears in the FAQ.
The complete question and answer are below.  spost is in the
last recommendation, #7.  For the purpose of answering this
question, does #7 do anything that "mts: sendmail" does not?

The explanation for #7 sounds like the user wants to work around
a server problem.  If they're going to edit their config file,
why not remove that server?  If it's a transient problem, they
wouldn't have to edit the config if they used the -server option
to send.

#5 should say "mts: smtp" and "mts: sendmail" instead of
"mta: sendmail/smtp" and "mta: sendmail", respectively.

#6 should be removed from this answer because the sendmail
executable is not run when using SMTP.


Subject: 06.04 Fixing "post: problem initializing server; [BHST] no
servers available"
From: Peter Marvit <marvit at hplabs.hpl.hp.com>,
        Eric Bracken <bracken at bacon.performance.com>
Date: Tue, 1 Nov 1994 00:00:00 -0800

  The error message itself is essentially correct. However, what this
  really means is: MH's post cannot connect to a running sendmail over
  an SMTP port (MH configured with SMTP and SENDMTS).

  The potential problems:

  1. Your local sendmail daemon is dying or not running for some

  2. You use BIND and your local nameserver is not responding.
     Solution: Delete "/etc/resolv.conf."

  3. Your $MHLIB/mts.conf (mtstailor) has its "servers:" pointing to a
     non-existent machine or a machine which is a) not reachable or b)
     not running the sendmail daemon.

From: Bdale Garbee <bdale at col.hp.com>,
        Eric Bracken <bracken at bacon.performance.com>
Date: Sun, 1 May 1994 00:00:00 -0800

  4. The hostname localhost [] is missing from /etc/hosts.

     Solution: add an entry for "localhost" to /etc/hosts or your DNS
     database or add the following to $MHLIB/mts.conf (mtstailor):

       servers: \01localnet

From: Larry Daffner <ldaffner at convex.com>
Date: 3 Mar 1996 14:39:54 -0600

  5. Your load average is so high that sendmail is refusing

     Solution: Change your configuration from "mta: sendmail/smtp" to
     "mta: sendmail" so that a sendmail processes is spawned to
     deliver the message. This is a double-edged sword since the extra
     process only makes the load worse.

From: Corbin Covault <cec8 at po.cwru.edu>
Date: Sun, 02 Sep 2001 02:13:42 -0400

  6. Sendmail may not be located on the path that MH expects.

     Solution: Try specifying the path explicitly by adding a line to
     mts.conf thus:
       sendmail: /usr/sbin/sendmail
     or wherever your sendmail daemon executable lives.

From: Neil W Rickert <rickert+nn at cs.niu.edu>
Date: 13 Apr 2001 18:47:43 -0500

  7. You don't want to use an available server.

     Solution: Try

       postproc: /usr/local/lib/mh/spost

     in your MH profile (but check the path first). That should use
     command line sendmail.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]