Subject: Pine Problem.

From: [email-masked] (mr.David Mehler Mehler)
Date: Mon, 11 Aug 1997 12:17:35 EDT

Hello,
	I've got problems with Pine. I'm using several different systems,
so I'll be specific.
	First, my computer is a 486 dx 100 mhz with 16 megs of ram,
running Dos 6.22 and Windows 3.1. I'm using a dosbased telecommunications
program, called {Commo} to get to where I need to go.
	Alright, first situation. I use {Commo} in conjunction with a
telnet app to go to my College, where they have a shell account, running
Pine. I try to compose to a news group, but whenever I press enter to
advance to the next line, it asks me for a file to attach, of course, I
don't want this, so I hit control c, but it keeps asking me this, and
won't let me do anything else, there version of Pine is 3.93.
	Second situation, I'm telneting to my ISP, to get on there pine.
There using version 3.95. I type in pine, but I get ppiinnee instead and
it says that it doesn't recognize my terminal.
	You may be wondering why I don't just get pc-pine and be done
with it. Well, I did, one for a dos packet driver, it was difficult to
find one. Whenever I use it, it says that it can't open my inbox, no such
folder. Then it says, when I change the inbox from {} to [] invalid
specification. It also says I can't send messages without an open remote
folder.
	I've included my pinerc file, my current wattcp.cfg file, and how
it was by default

# Updated by Pine(tm) 3.96, copyright 1989-1996 University of Washington.
#
# Pine configuration file -- customize as needed.
#
# This file sets the configuration options used by Pine and PC-Pine.  If
you
# are using Pine on a Unix system, there may be a system-wide
configuration
# file which sets the defaults for these variables.  There are comments
in
# this file to explain each variable, but if you have questions about
# specific settings see the section on configuration options in the Pine
# notes.  On Unix, run pine -conf to see how system defaults have been
set.
# For variables that accept multiple values, list elements are separated
# by commas.  A line beginning with a space or tab is considered to be a
# continuation of the previous line.  For a variable to be unset its
value
# must be blank.  To set a variable to the empty string its value should
# be "".  You can override system defaults by setting a variable to the
# empty string.  Switch variables are set to either "yes" or "no", and
# default to "no".
# Lines beginning with "#" are comments, and ignored by Pine.

########################### Essential Parameters
###########################

y next line# Over-rides your full name from Unix password file. Required
for PC-Pine.
personal-name=dave

# Your login/e-mail user name
user-id=example 

# Sets domain part of From: and local addresses in outgoing mail.
user-domain=shell.example.net
# List of SMTP servers for sending mail. If blank: Unix Pine uses
sendmail.
smtp-server=mail.example.net

# NNTP server for posting news. Also sets news-collections for news
reading.
nntp-server=news.example.net

# Path of (local or remote) INBOX, e.g. ={mail.somewhere.edu}inbox
# Normal Unix default is the local INBOX (usually /usr/spool/mail/$USER).
inbox-path=[pop.example.net/pop3]INBOX

# List of incoming msg folders besides INBOX, e.g. ={host2}inbox,
{host3}inbox
# Syntax: optnl-label {optnl-imap-host-name}folder-path
incoming-folders=

# List of directories where saved-message folders may be. First one is
# the default for Saves. Example: Main {host1}mail/[], Desktop mail\[]
# Syntax: optnl-label {optnl-imap-hostname}optnl-directory-path[]
folder-collections=

# List, only needed if nntp-server not set, or news is on a different
host
# than used for NNTP posting. Examples: News *[] or News *{host3/nntp}[]
# Syntax: optnl-label *{news-host/protocol}[]
news-collections=

# List of folder pairs; the first indicates a folder to archive, and the
# second indicates the folder read messages in the first should
# be moved to.
incoming-archive-folders=

# List of context and folder pairs, delimited by a space, to be offered
for
# pruning each month.  For example: {host1}mail/[] mumble
pruned-folders=

# Over-rides default path for sent-mail folder, e.g. =old-mail (using
first
# folder collection dir) or ={host2}sent-mail or ="" (to suppress
saving).
# Default: sent-mail (Unix) or SENTMAIL.MTX (PC) in default folder
collection.
default-fcc=

# Over-rides default path for saved-msg folder, e.g. =saved-messages
(using
first
# folder collection dir) or ={host2}saved-mail or ="" (to suppress
saving).
# Default: saved-messages (Unix) or SAVEMAIL.MTX (PC) in default folder
collection.
default-saved-msg-folder=

# Over-rides default path for postponed messages folder, e.g. =pm (which
uses
# first folder collection dir) or ={host4}pm (using home dir on host4).
# Default: postponed-msgs (Unix) or POSTPOND.MTX (PC) in default fldr
coltn.
postponed-folder=

# If set, specifies where already-read messages will be moved upon
quitting.
read-message-folder=

# Over-rides default path for signature file. Default is ~/.signature
signature-file=

# List of file or path names for global/shared addressbook(s).
# Default: none
# Syntax: optnl-label path-name
global-address-book=

# List of file or path names for personal addressbook(s).
# Default: ~/.addressbook (Unix) or \PINE\ADDRBOOK (PC)
# Syntax: optnl-label path-name
address-book=

############################### Preferences
################################

# List of features; see Pine's Setup/options menu for the current set.
# e.g. feature-list= select-without-confirm, signature-at-bottom
# Default condition for all of the features is no-.
feature-list=

# Pine executes these keys upon startup (e.g. to view msg 13:
i,j,1,3,CR,v)
initial-keystroke-list=

# Only show these headers (by default) when composing messages
default-composer-hdrs=

# Add these customized headers (and possible default values) when
composing
customized-hdrs=

# When viewing messages, include this list of headers
viewer-hdrs=

# Determines default folder name for Saves...
# Choices: default-folder, by-sender, by-from, by-recipient,
last-folder-used.
# Default: "default-folder", i.e. "saved-messages" (Unix) or "SAVEMAIL"
(PC).
saved-msg-name-rule=

# Determines default name for Fcc...
# Choices: default-fcc, by-recipient, last-fcc-used.
# Default: "default-fcc" (see also "default-fcc=" variable.)
fcc-name-rule=

# Sets presentation order of messages in Index. Choices:
# subject, from, arrival, date, size. Default: "arrival".
sort-key=

# Sets presentation order of address book entries. Choices: dont-sort,
# fullname-with-lists-last, fullname, nickname-with-lists-last, nickname
# Default: "fullname-with-lists-last".
addrbook-sort-rule=

# Sets the default folder and collectionoffered at the Goto Command's
prompt.
goto-default-rule=

# Reflects capabilities of the display you have. Default: US-ASCII.
# Typical alternatives include ISO-8859-x, (x is a number between 1 and
9).
character-set=

# Specifies the program invoked by ^_ in the Composer,
# or the "enable-alternate-editor-implicitly" feature.
editor=

# Specifies the program invoked by ^T in the Composer.
speller=

# Specifies the column of the screen where the composer should wrap.
composer-wrap-column=

# Specifies the string to insert when replying to  message.
reply-indent-string=

# Specifies the string to use when sending a  message with no to or cc.
empty-header-message=

# Program to view images (e.g. GIF or TIFF attachments).
image-viewer=

# If "user-domain" not set, strips hostname in FROM address. (Unix only)
use-only-domain-name=

########## Set within or by Pine: No need to edit below this line
##########

# Your default printer selection
printer=

# List of special print commands
personal-print-command=

# Which category default print command is in
personal-print-category=

# Set by Pine; controls beginning-of-month sent-mail pruning.
last-time-prune-questioned=97.7

# Set by Pine; controls display of "new version" message.
last-version-used=3.96

# This names the path to an alternative program, and any necessary
arguments,
# to be used in posting mail messages.  Example:
#                    /usr/lib/sendmail -oem -t -oi
# or,
#                    /usr/local/bin/sendit.sh
# The latter a script found in Pine distribution's contrib/util
directory.
# NOTE: The program MUST read the message to be posted on standard input,
#       AND operate in the style of sendmail's "-t" option.
sendmail-path=

# This names the root of the tree to which the user is restricted when
reading
# and writing folders and files.  For example, on Unix ~/work confines
the
# user to the subtree beginning with their work subdirectory.
# (Note: this alone is not sufficient for preventing access.  You will
also
# need to restrict shell access and so on, see Pine Technical Notes.)
# Default: not set (so no restriction)
operating-dir=

# This variable takes a list of programs that message text is piped into
# after MIME decoding, prior to display.
display-filters=

# This defines a program that message text is piped into before MIME
# encoding, prior to sending
sending-filters=

# A list of alternate addresses the user is known by
alt-addresses=

# This is a list of formats for address books.  Each entry in the list is
made
# up of space-delimited tokens telling which fields are displayed and in
# which order.  See help text
addressbook-formats=

# This gives a format for displaying the index.  It is made
# up of space-delimited tokens telling which fields are displayed and in
# which order.  See help text
index-format=

# The number of lines of overlap when scrolling through message text
viewer-overlap=

# Number of lines from top and bottom of screen where single
# line scrolling occurs.
scroll-margin=

# The number of seconds to sleep after writing a status message
status-message-delay=

# The approximate number of seconds between checks for new mail
mail-check-interval=

# Full path and name of NEWSRC file
newsrc-path=

# Path and filename of news configation's active file.
# The default is typically "/usr/lib/news/active".
news-active-file-path=

# Directory containing system's news data.
# The default is typically "/usr/spool/news"
news-spool-directory=

# Path and filename of the program used to upload text from your terminal
# emulator's into Pine's composer.
upload-command=

# Text sent to terminal emulator prior to invoking the program defined by
# the upload-command variable.
# Note: _FILE_ will be replaced with the temporary file used in the
upload.
upload-command-prefix=

# Path and filename of the program used to download text via your
terminal
# emulator from Pine's export and save commands.
download-command=

# Text sent to terminal emulator prior to invoking the program defined by
# the download-command variable.
# Note: _FILE_ will be replaced with the temporary file used in the
downlaod.
download-command-prefix=

# Sets the search path for the mailcap cofiguration file.
# NOTE: colon delimited under UNIX, semi-colon delimited under
DOS/Windows/OS2.
mailcap-search-path=

# Sets the search path for the mimetypes cofiguration file.
# NOTE: colon delimited under UNIX, semi-colon delimited under
DOS/Windows/OS2.
mimetype-search-path=

# Sets the time in seconds that Pine will attempt to open a network
# connection.  The default is 30, the minimum is 5, and the maximum is
# system defined (typically 75).
tcp-open-timeout=

# Sets the time in seconds that Pine will attempt to open a UNIX remote
# shell connection.  The default is 15, min is 5, and max is unlimited.
# Zero disables rsh altogether.
rsh-open-timeout=

# Sets the version number Pine will use as a threshold for offering
# its new version message on startup.
new-version-threshold=

# Extension used for local folder names (".MTX" by default).
folder-extension=

# Choose: black,blue,green,cyan,red,magenta,yellow,or white
(CAPS=BLINKING).
normal-foreground-color=
normal-background-color=
reverse-foreground-color=
reverse-background-color=

domainslist=example.net
nameserver=206.26.98.2
popuser=dmm
poppass=dave*1*
popserver=pop.example.net
mailserver=mail.example.net
newsserver=news.example.net
netmask=255.255.255.254
hostname=example.net
my_ip=206.30.146.156
gateway=206.26.98.1
sockdelay=120
mss=512
boxname=userid
nameserver=206.26.98.6

---

From: "Robin S. Socha" <[email-masked]>
Date: 11 Aug 1997 19:58:09 +0200

>> "DMM" == David Mehler Mehler <[email-masked]> writes:
[snipped "information"]

DMM> I type in pine, but I get ppiinnee instead and it says that it
DMM> doesn't recognize my terminal.  

a) Turn off local echo in your term-emu
b) Ask your ISP which term-emu to use and set it appropriately

DMM> You may be wondering why I don't just get pc-pine and be done
DMM> with it. 

Err, no :-/

DMM> Well, I did , one for a dos packet driver, it was difficult
DMM> to find one. Whenever I use it, it says that it can't open my
DMM> inbox, no such folder. 

RTFM. There's a chapter on how to set this value.

DMM> Then it says, when I change the inbox from {} to [] invalid
DMM> specification.  It also says I can't send messages without an
DMM> open remote folder.  

Dito.

DMM> I've included my pinerc file, my current wattcp.cfg file, and how
DMM> it was by default

Thank. That's just what we needed. How about reading the docu first
before heaping this stuff in everybody's inbox?

BTW, your RN is broken, mr.David Mehler Mehler. juno.com... figures
:-/

[snipped 999 lines of junk]

-- 
Robin S. Socha, M.A.
Political Science Dept., Bonn University, Bonn
On the package it said: "Requires MS Windows 3.11 or better"  
                                  ... so I got myself Linux.

---

From: Edward M Greshko <[email-masked]>
Date: Tue, 12 Aug 1997 06:45:02 +0800 (GMT)

> DMM> You may be wondering why I don't just get pc-pine and be done

If you check the archives, this "awesome" fellow has been trying to use
PC-pine with POP3.  He has been told numerous times that PC-pine does not
support POP3.  Terry Gray told him PC-pine does not support POP3.  

Maybe "awesome" doesn't mean what it should in his case?

-- 
Edward M. Greshko                  Technical Manager, Electronic Commerce
                                   Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287        6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197             Taipei, Taiwan R.O.C

---

From: Mike Brudenell <[email-masked]>
Date: Tue, 12 Aug 1997 10:01:19 +0100 (BST)

> won't let me do anything else, there version of Pine is 3.93.

This sounds as if your terminal emulator might be sending both a Carriage
Return (CR) and Line Feed (LF) character whenever you press the return
key.

Pine interprets CR as "start a new line", and LF (which is the same as
Ctrl/J) as either "Attach a file" (if your cursor is on a header line in
the Compose Message screen) or "Justify" (if your cursor is in the message
text area instead).

Try checking your terminal emulator to see if there is some option to
select between CR or CR+LF when the return key is pressed.

By the way, I think I have seen this referred to as "Berkeley 4.3 CR Mode"
in NCSA Telnet on the Macintosh (I have this turned _off_), so you may
find it hiding under some not terribly obvious name like this one.

By the way the current version of Pine (both UNIX and PC variants) is
3.96.  Try and get your 3.93 version upgraded.

> There using version 3.95. I type in pine, but I get ppiinnee instead

This is because you have got "local echo" turned on in your terminal
emulator program.  "Local Echo" means that whenever you press a key your
terminal emulator displays the character on the screen as well as sending
it to the UNIX host.  In a normal configuration the UNIX host echoes
received characters back to the terminal, which then displays it again:
hence the double characters.

One solution would be to turn off this remote echoing.  However this is
not a standard way of working these days and may break other programs.

Instead you should stop your terminal emulator echoing the character
locally.  Look through its menu options/configuration file and turn off
the local echo option.

By the way...

Because you are seeing this problem at the UNIX command line prompt you
should have deduced that it is therefore nothing to do with Pine (which
isn't even running yet).  Instead it is affecting your whole UNIX session
and hence is obviusly either a problem with your computerhardware/software
setup, or that of your ISP.  In either case the Pine forum is not an
appropriate place to sort this one out; you should have contacted your ISP
for help (after you're paying them! :-)

> and it says that it doesn't recognize my terminal.

This might be caused by the "local echo" being turned on, causing the UNIX
host not to be able to figure out what sort of terminal you are using.

However usually the terminal type information is passed in a different way
to normal typed input, so I suspect this problem _won't_ be due to local
echo being turned on. 

Instead it is probably because the terminal type that your terminal
emulator specified/negotiated with your ISP account when you logged in
isn't one that Pine understands. 

Check this as follows... Straight after logging in try displaying the
terminal type that your UNIX command shell thinks you're using: 

	echo $TERM

If this is unset, or is set to something obscure then Pine (and perhaps
many other programs) won't know what escape sequences to send to control
the screen, and so complain about an unknown terminal type.

Usually this option is set by the local Telnet program on your computer.
For example the copy of NCSA Telnet on my Mac allows you to select either
VT100 or VT220 emulation; it then informs the UNIX system which one you
are using as you connect to it.

If you need further help on getting your Telnet program configured to use
a sensible terminal emulation please speak to your ISP's Help Desk.

> specification.
>	[snip!]

There are two problems here:

1.  The correct syntax for the inbox-path variable is:

	inbox-path={pop.example.net/pop3}INBOX

Note the use of curlies (braces) rather than squares (brackets).

The "folder-collections" variable requires a "placeholder" instead of a
particular filder name.  This placeholder is the character sequence "[]",
thus:

	folder-collections={pop.example.net/pop3}[]

2.  The second problem is that the above won't work either!  This is
because no version of PC-Pine yet supports POP access.  It instead _must_
connect to an IMAP server to access your mail.

POP and IMAP are very different protocols; your ISP may offer one, the
other, or both.  You will need to check with them if they offer an IMAP
service.  If they do then you will need to find out from them the IP name
of the machine it is running on and replace the machine names in the above
examples with it (and delete the "/pop" qualifier too!).

If your ISP doesn't offer an IMAP service then PC-Pine is not currently an
option for you.

> It also says I can't send messages without an open remote folder. 

This is correct.  PC-Pine requires you to prove who you are by having you
first login to the IMAP server with a username and password.  This
authentication step proves that you are "you".  PC-Pine then includes this
authenticiation information (minus the password!) in any messages you
send.  This is a laudable effort to try and help reduce mail forging on
the Internet. 

Cheers,

-- 
Mike Brudenell                                         <[email-masked]>
------------------------------------------------------------------------
The Computing Service, University of York, Heslington, York, YO1 5DD, UK
Tel: +44-1904-433811  FAX: +44-1904-433740  http://www.york.ac.uk/~pmb1/

* Unsolicited commercial e-mail is NOT welcome at this e-mail address. *