Subject: Interference with Pine Attachments?

From: "Sheryl A. Lemma" <[email-masked]>
Date: Tue, 01 Sep 1998 11:14:08 -0400

Hi,

We've successfully installed wu-ftp with 90% of our system users chroot'ed
to their own directory. Ftp is now shored up exactly as we need it to be.
However, Pine Mail is failing to attach files with the messages:

When trying to attach, this message comes up:
[ Problem attaching: /usr/users/students/a_ziffel/./JIMNJILL.jpg ]

After moving from the attachment area, this message appears:
[ Attachments allowed only from /usr/users/students/a_ziffel/./ ]

I've unsuccessfully searched the archives of both Pine and WU-FTP to find
the answer to this problem. What do I need to do to fix this?

Thanks in advance,

	Sheryl Lemma

% % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % %
%  Sheryl A. Lemma                           Internet: [email-masked]  %
%  Assistant Director                           Voice: (717)867-6060  %
%  Administrative Computing                       FAX: (717)867-6019  %
%                                                                     %
%            L E B A N O N    V A L L E Y    C O L L E G E            %
%                                                                     %
% DEC Unix 3.2d/4.0D, Coll: Live 14v5, Dev 16, Ben: Live 4.3, Dev 5.0 %
%                                                                     %
%                    Visit my Personal Web Page at                    %
%       http://www.geocities.com/Heartland/Plains/4407/index.html     %
%                                                                     %
%                Never underestimate the power of a smile!            %
% % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % %

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

---

From: George McConnell <[email-masked]>
Date: Tue, 1 Sep 1998 11:43:12 -0400 (EDT)

> [ Problem attaching: /usr/users/students/a_ziffel/./JIMNJILL.jpg ]

it sounds like you need to check the permissions of the file and/or
directory you are trying to attach.

> [ Attachments allowed only from /usr/users/students/a_ziffel/./ ]

again, sounds like a permissions problem.

-- 
In the force if Yoda's so strong, construct a sentence with words in
the proper order then why can't he?

---

From: "Sheryl A. Lemma" <[email-masked]>
Date: Tue, 01 Sep 1998 11:54:41 -0400

George,

The test file (as with the other test files) is readable, writable and
executable by all. Permissions do not appear to be the problem. I have a
strong feeling it is the chroot, since everything was working up until we
installed ftp.

	Sheryl

---

From: Joe DiBenedetto <[email-masked]>
Date: Tue, 1 Sep 1998 12:24:34 -0400 (EDT)

Sheryl,

What about the '/./' at the end of the path?  Perhaps that's a config
problem in wu-ftp that's throwing Pine?

Joe:D
-------------------------------------------------------------------------------
Joe DiBenedetto		23 Park Row			Tel: 212-238-9010
Director of MIS		4th Floor			Fax: 212-238-9127
J&R Electronics		New York, NY 10038-2305		E-mail: [email-masked]
-------------------------------------------------------------------------------

---

From: "Sheryl A. Lemma" <[email-masked]>
Date: Tue, 01 Sep 1998 17:12:11 -0400

Joe,

Ay, there's the rub. The /./ is the chroot command included in the passwd
entry that restricts the user to his/her own directory for ftp purposes.
Works wonderfully for keeping nosy little students from getting the
/etc/passwd file. 

Based on the answers I've received, it seems that no one is using Pine in
conjunction with wu-ftp. Is this really the case? If so, what are other
schools/institutions doing to restrict access to the password file?

	Sheryl

---

From: "Ed Greshko" <[email-masked]>
Date: Wed, 2 Sep 1998 07:58:43 +0800

Sheryl,

> schools/institutions doing to restrict access to the password file?

Are you looking to restrict access to the password file because you don't
want everyone to know who else has an account or is it because you don't
want folks running "crack" against the file.  If it is the latter then you
should determine if your system can run with a "shadow" password file.  The
put the password in a file called "shadow" which is not readable.  Most
systems these days run in that manner.  Some need to be coaxed into that
configuration.

Regards,
Ed

---

From: "Sheryl A. Lemma" <[email-masked]>
Date: Wed, 02 Sep 1998 08:30:39 -0400

Hi Ed (and Joe, who asked the same question),

We are restricting the password file because we cannot run shadowed
passwords. The same machine that holds our student accounts also holds our
Library system (Unicorn, from Sirsi). Sirsi won't work with shadowed
passwords. Great software, huh?

Anyway, outside of moving all student accounts to another machine (for
which we don't have the money) we are stuck with our current setup. 

Over the past few months, we had problems with the password file being both
ftp'd and pulled into Pine either as text or an attachment. We have plugged
the Pine holes (very easy), and this summer we installed wu-ftp for the ftp
protection. Basically, the ftp program works by doing a chroot in the
passwd file so that a person sees his/her directory as the top level
directory. Any attempts to cd out of the directory will just be an error,
because the ftp sees this directory as the root directory. There's only one
catch ... in order to do listing, you must provide a statically linked copy
(or hard-link to such) of the ls program in each home directory. This is
only for the ftp program, though. All of our other programs work if using a
telnet session; with, of course, the exception of the Pine attachments.

No one else is really using this combination, huh?

Thanks for the continuous feedback (I have yet to hear from the wu-ftp list),

	Sheryl

---

From: Joe DiBenedetto <[email-masked]>
Date: Wed, 2 Sep 1998 09:48:41 -0400 (EDT)

Sheryl,

No, I don't think too many people are using that combo.

Speaking of links, what if you put a symbolic link to the directory where
the pine attachments are?  Maybe that would help?

Joe:D

---

From: Russell Heilling <[email-masked]>
Date: Wed, 2 Sep 1998 15:38:15 +0100 (BST)

> the pine attachments are?  Maybe that would help?

If the destination is outside the chrooted area then a symbolic link won't
work, but a hard link would.

-- 
Russell Heilling   --   Technical Manager    --   NetDirect Internet Ltd
 Tel: +441812937000 email: [email-masked] Fax: +441812936000
     "That which doesn't kill you will make you bitter and cynical"

---

From: "Sheryl A. Lemma" <[email-masked]>
Date: Wed, 02 Sep 1998 11:01:47 -0400

>work, but a hard link would.

That's the problem ... the destination shouldn't be outside the chrooted
area. A student cannot attach anything even in his own directory! When you
^J, ^T and look in Pine, you can see the files in your home directory. It's
just that when you select it, it gives the problem attaching message ( [
Problem attaching: /usr/users/a_ziffel/./JIMNJILL.jpg ] ), then when you
move past the attachment line, it tells you ( [ Attachments allowed only
from /usr/users/students/a_ziffel/./ ] ).

It seems like Pine does not understand the . in the path.

Again, many thanks for scratching your collective heads with me on this.

Regards,

	Sheryl

P.S. I've now posted to FOUR lists with this problem ... if I ever do get
the answer to this and it's not from this list, I'll be sure to post it! :)

---

From: Shawn Jeffries <[email-masked]>
Date: Wed, 2 Sep 1998 11:17:16 -0400 (EDT)

Do your users have "use-current-dir" set or unset by default?

                            FEATURE: use-current-dir
 
This feature controls an aspect of several commands. If set, your
"current working directory" (which, at least for your current Pine
"session," is "/home/xxxxx") will be used instead of your home
directory (which, in the present configuration of your system, is
"/home/xxxxx") for all of the following operations:
 *  Export in the MESSAGE INDEX and MESSAGE TEXT screens
 *  Attachment Save in the MESSAGE TEXT and ATTACHMENT TEXT screens
 *  Ctrl-R file inclusion in the COMPOSER
 *  Ctrl-J file attachment in the COMPOSER
 
--------------------------------------------------------

    Shawn Jeffries
    [email-masked]

---

From: Michael Thomas Cope <[email-masked]>
Date: Wed, 2 Sep 1998 08:58:34 -0700 (PDT)

> the answer to this problem. What do I need to do to fix this?
As shown here, I have successfully attached a file from my home directory
with my home directory set as you have stated

[8:54am] mcope@orion (~/var/log): grep mcope /etc/passwd
mcope:x:14870:14750:Michael Thomas Cope:/home/hmc_2000/mcope/./:/usr/local/bin/tcsh

This is Pine 4.02 with Solaris 2.6 compiled with gcc 2.8.1. 

-Mike 
-- 
Michael Cope: Harvey Mudd College '00; Armand Hammer UWC '96
E-mail: [email-masked]

---

From: Jeff Goswick <[email-masked]>
Date: Wed, 2 Sep 1998 18:28:23 -0600 (MDT)

I've been trying to send an email with an HTML attachment so that another pine
user can read it inline.  I'd like to send it as an attachment, not
in the body of the message.

Pine attaches and sends it fine, but when I CC: myself and read it in Pine,
the HTML file can only be read via an external viewer -> the pine viewer won't
show it.

If I save the message to a folder, then change the attachment's MIME
HEADER from:

     Content-Disposition: attachment; filename="temp.html"

to:

     Content-Disposition: inline; filename="temp.html"

then pine shows the attachment inline, as I'd like.

Is there anyway to configure pine to do this at send time? (ie. to attach HTML
files, or text files in general, as inline attachments so that pine will
display them in the normal message display)?

How did the Pine developers expect pine users to send HTML so that it is
viewable by Pine, attachements or in the message body?

Thanks,
Jeff

---

From: Steve Ekwall <[email-masked]>
Date: Thu, 3 Sep 1998 00:03:34 -0600 (MDT)

Hi Jeff, 

As it should be! (sigh/grin:) TWO DIFFERENT CRITTERS (like a
removable floppy vs a Hard Drive vs a CDROM = data yes, rwxALL=NO!).
</grip mode ON>THANKS
  Oh, Please please dont' try to M_A_K_E pine be forced to read HTML.
HTML doesn't even BELONG in e-mail at all! It has its domain, it has its
FUNCTION, but that is like asking, I want to send e-mail with ALL of my
data files attached!  This neither is a function of e-mail, this is a
function of a file transferring feature. ftp etc.
  Besides slowing down e-mail (html gutted in bulk) It *IS NOT* read or
readable by everyone out there </grip mode OFF>
-----
All the funny letters just to say THANKS!
<suggestion on>
<NextYears= ">2001 FONTS /active on rem kill9 ##########@domain.##?/
:/Interlaced active:GO: THANKS:/"/"interlaced inactive/active OFF</End
FONTS 2001></NextYears)
</suggestion on/off>

Plus it is so much F_U_N and so EASY to read too :) PUSH THANKS

Bonus thought:) filter it to ascii folder, or show him how to do that?? 
and send it, as links (forms/cgi-bin+)
will be off-line line anyway and really slow down the net (sigh).. can't
you just type in Hey! "go chekc out http://abvc.abc.com  *cool site*"
Every E-mail I get from Bill Gate'rs out there, that come up I can't
display it, I JUST DELETE IT... I already *GET* Enough Junk Mail.
 Nothing personal against you Jeff (heck I don't even know you <grin>),
BUT HTML *Anything* in E-mail is asking for stuffed mailboxes, not speed
and global E_MAIL access. Some system restrict the SIZE of each piece of
mail already to prevent this, so odds are it might get attached, yet never
get through. If you're just trying to show him a *cool* url, point him to
it in ascii or add a few keystrokes in your
a href="[email-masked]#"       <----- Thats all and FAST F_A_S_T!
:)

Hope this helps, I know , N_O_T Quit your question, BUT, html doesn't
belong in e-mail.  It belongs in URL's & home pages, & books on HTMLD.

-=se=-
steve (plus it's really a bear to read for others:) ekwall
[email-masked]
 
-----------snip--------------

On Wed, 2 Sep 1998, Jeff Goswick wrote:

     

     to:

     
     
     Thanks,
     Jeff

---

From: Jeff Goswick <[email-masked]>
Date: Fri, 4 Sep 1998 19:09:26 -0600 (MDT)

Yea Steve, while I won't rant & rave about it, I mostly agree.  HTML ain't
good email.  But, this was more a question about how Pine works than about
email etiquette.  

As far as sending a link, there isn't a WWW link to send.  It is possible to
read this file with an external browser, but then you need either an X-server,
or lynx, neither of which are available.

Anyway, I figure the tool is designed to read HTML, and send HTML,  seems
it should be able to read the HTML it sends.

Anyone else know how to send HTML with Pine so that the MIME header for the
attachment reads: "Content-Disposition:inline", or how to get Pine to read
text/html attachments when the header reads "Content-Disposition: attachment"?

Regards,
Jeff

On Thu, 3 Sep 1998, Steve Ekwall wrote:

> Date: Thu, 3 Sep 1998 00:03:34 -0600 (MDT)
> From: Steve Ekwall <[email-masked]>
> To: Pine Discussion Forum <[email-masked]>
> Subject: Re: How to send HTML so pine reads it inline.
> 
> Hi Jeff, 
> 

-- SNIP --

>  I've been trying to send an email with an HTML attachment so that another
>  pine user can read it inline.  I'd like to send it as an attachment, not in
>  the body of the message.
> 
>  the HTML file can only be read via an external viewer -> the pine viewer
>  won't show it.
> 
>  If I save the message to a folder, then change the attachment's MIME HEADER
>  from:
> 
>  Is there anyway to configure pine to do this at send time? (ie. to attach
>  HTML files, or text files in general, as inline attachments so that pine
>  will display them in the normal message display)?
> 
>  Thanks, Jeff