Subject: How does pine actually send outgoing mail?

From: daniel lance herrick <[email-masked]>
Date: Mon, 14 Oct 2002 09:27:39 -0400 (EDT)

On my linux (redhat 7.2) box, I have pine sending
the mail fine.

I'm trying to automate the handling of a
particular class of e-mail (using procmail,
formail, and sendmail) and the headers and
envelope are not coming out right.

I know there is nothing listening on port 25 on
localhost.

So how does pine actually send the mail? Does it
make a direct connection to port 25 on the
addressee machine? Does it pipe it directly into
sendmail, itself? 

The question I am trying to answer is, "How in the
world is pine finding something that is configured
right when what I am trying to use is configured
wrong?!"

If I knew what pine is doing, I might copy it for
my automated handling. Or it might help me get
other things configured right.

dan

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Christopher Fisk <[email-masked]>
Date: Mon, 14 Oct 2002 09:43:37 -0400 (EDT)

>envelope are not coming out right.

On RedHat 7.2 by default sendmail is running.  It isn't listening on the 
public port but is just binding to the lo interface (127.0.0.1)  This 
behavior is dictated with the sendmail.mc value:  
DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')

This forces the sendmail daemon to only bind to the 127.0.0.1 interface 
and makes it so it's not possible for other machine to send email with it.

By default pine uses localhost to send e-mail.

If sendmail is not running you would need to configure the SMTP host in 
the settings of pine.

What is happening to the envelope headers of your message?  Looking I see 
localhost mentioned, then it goes to your apps server, then to the mail 
server, then out to the internet.  you can usually trace the exact path of 
your sent messages to find out where things are going.

Christopher Fisk
-- 
The problem of the day is: The Internet is being scanned for viruses.

---

From: daniel lance herrick <[email-masked]>
Date: Mon, 14 Oct 2002 10:22:19 -0400 (EDT)

> DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')

I went into the various startup scripts and
disabled things before first connecting the
computer to the net. fetchmail cannot find a
listener on port 25 to do local delivery. I'm
assuming that means pine is not finding a listener
on port 25 to hand off outgoing mail.
 
> If sendmail is not running you would need to configure the SMTP host in 

Probably I did that. I'll look.
 
> your sent messages to find out where things are going.

When Proquest switched to pine (from elm) as the
MUA for unco-operative unix users, I subscribed to
this list at the office to help me learn to use
pine effectively.

The system where I am having problems is dlh.com.
The router and mail server is cosmo.dlh.com with a
192.168.. ip address behind a dialup (diald)
connection.

The thing I am trying to automate is the e-mail
list [email-masked], which is implemented by
majordomo at [email-masked].

Based on elaborate procmail filtering on
cosmo.dlh.com, a message to [email-masked]
gets an "Approved: " header added to it and will
be handed off to [email-masked].

Right now, lists.apk.net is rejecting things
because dns does not know about cosmo.dlh.com.
Sendmail is configured to masquerade as dlh.com,
but, for some reason is exposing the domain name
cosmo.dlh.com.

At that point, I thought it might be helpful to
learn why *anything* is working. (I got e-mail
working from the router machine some months ago.
It stopped doing NAT when I dropped diald in, so
everyone is still reading their e-mail on the
router. But that's another project.)

Here are the headers of a message that came to me
at Proquest from pine on that box:

From: [email-masked]
Date: Fri, 4 Oct 2002 18:30:10 -0400 (EDT)
To: "Herrick, Daniel Lance -- daniel lance herrick"
    <[email-masked]>
Subject: Re: hi (fwd)

Looks like, whatever the transport agent was, it
exposed the domain name cosmo.dlh.com to
mailgw.bellhow.com (we sold the name Bell and
Howell and have to stop using it at the end of the
year - bellhow.com is Proquest.)

That X-Authentication-Warning looks like pine is
running sendmail. It also looks like trying to
send mail to [email-masked]
interactively from pine running on cosmo will fail
the same way the automated thing did.

dan

---

From: [email-masked]
Date: Mon, 14 Oct 2002 08:32:20 -0700 (MST)

Hi,
I am suddenly inundated by unwanted mail--this has never happened on my pine
account.  In the past the account has been secure, within the university where
I work. Can I filter my mail? How? 
Thanks,
JVan

____________________________________________________________________________

J. Clayton Van                                 
English Department LLB 542                    "let there be songs,  
Arizona State University                       to fill the air."
http://www.public.asu.edu/~jvanasu       Jerry Garcia and Robert Hunter,1971. 
____________________________________________________________________________

---

From: Alessandro Selli <[email-masked]>
Date: Mon, 14 Oct 2002 17:34:58 +0200 (CEST)

Il giorno Mon, 14 Oct 2002, daniel lance herrick così ha scritto:

|From: daniel lance herrick <[email-masked]>
|To: Pine Discussion Forum <[email-masked]>
|Date: Mon, 14 Oct 2002 10:22:19 -0400
|Subject: Re: How does pine actually send outgoing mail?
|
|
|
|On Mon, 14 Oct 2002, Christopher Fisk wrote:
|
|> On Mon, 14 Oct 2002, daniel lance herrick wrote:
|> >I'm trying to automate the handling of a
|> >particular class of e-mail (using procmail,
|> >formail, and sendmail) and the headers and
|> >envelope are not coming out right.
|>
|> On RedHat 7.2 by default sendmail is running.  It isn't listening on the
|> public port but is just binding to the lo interface (127.0.0.1)  This
|> behavior is dictated with the sendmail.mc value:
|> DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')
|
|I went into the various startup scripts and
|disabled things before first connecting the
|computer to the net. fetchmail cannot find a
|listener on port 25 to do local delivery. I'm
|assuming that means pine is not finding a listener
|on port 25 to hand off outgoing mail.
|

  Check your $HOME/.pinerc for a line beginning with "smtp-server=" which
defines the SMTP relay host Pine is to use.  Syntax:

smtp-server=SMTPserver.name[:port-number]

  On my computer I commented out the "sendmail-path=" line to prevent Pine to
attempt connecting to the unexistant MTA on localhost.

|>
|> If sendmail is not running you would need to configure the SMTP host in
|> the settings of pine.
|
|Probably I did that. I'll look.
|

  To know for sure is a MTA is active on your system, just do a telnet
localhost 25:

aselli@aselli ~$ telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 host.domain.tld ESMPT Postfix (1.1.11)
QUIT
221 Bye
Connection closed by foreign host.

  Sandro

-- 
Bellum se ipsum alet
       La guerra nutre se stessa

Livio, Ab urbe condita, XXXIV,9

---

From: Mats Dufberg <[email-masked]>
Date: Tue, 15 Oct 2002 23:26:50 +0200 (CEST)

> addressee machine? Does it pipe it directly into

By default pine runs sendmail directly, that is, it does not need any
daemon.

Mats

-----------------------------------------------------------------
Mats Dufberg                                 [email-masked]
Blåarvsgränd 42                                    +46-8-38 48 59
SE-162 45 Vällingby, Sweden                       +46-70-258 2588