2/7 Has anyone got Pine to work in the new CSUA environment? I
didn't see anything in the FAQ that described this. When I open
up Pine I get:
[Can't open /var/mail/theeric: not a selectable folder]
When I try to do anything (i.e move up or down with arrow, hit I
for mail), I get another error:
[Command " " not defined for this screen. Use ? for help
\_ I don't understand why anyone would sit down at a shell for
the first time and choose the most broken and least functional
mail client given so many other quality choices.
\_ I use /usr/bin/mail. -- !OP
\_ Maybe because your claim that it's "most broken" is idiotic?
Maybe because it's easy to work and you don't have to read any
documentation to use it effectively?
\_ There are lots of easy to use mail clients that require no
reading. Judging from our local population either pine is
very hard to use or pine users are much less intelligent
since the overwhelming majority of mail client problems on
the motd are pine related going back many years. <s> Sorry
if you're one of the very few pine genius gurus out there and
got "offended". </sarcasm> The best thing root@soda could
do for the mail users here is delete the pine install. Anyone
clued enough to install their own can figure out the rest,
while those who can't figure it out can use something better.
\_ Why don't you name a few that's not 'broken'?
\_ I'll ignore your poor grammar and name one: mutt.
For the record, I haven't run a command line mail
reader in years, these days I use Mail.app. But that
doesn't change the fact that mutt is a spectacularly
better command line mail client than pine. -dans
\_ PP's claim that pine is the most broken mail client, while
hyperbolic, is pretty close to the mark. Unfortunately, Mark
Crispin hangs like an albatross over all UW mail related
software including pine and IMAP. In the case of pine, he
merely actively contributes to its sucking. In the case of
IMAP, what he has done is far worse since, last I checked,
UW-IMAP is the RFC reference implementation, and he has
single-handedly crippled numerous useful IMAP features while
slowing its adoption and driving back the day when POP is
just a bad memory.
cf: http://www.courier-mta.org/fud
-dans
\_ I got this error message a few days ago, since then, I
removed my .procmailrc, and now pine seems to work fine.
However I can't get to any of the mail files on
/var/mail/$USER. I do see incoming mails...
\_ I figured it out, you need to create "cur, new, tmp" in
/var/mail/$USER directory, then pine and mutt will work fine.
\_ Except that the new mail isn't being delivered to those dirs.
\_ any idea what those dirs are for? They are all empty, new mails
are in /var/mail/$USER folder, but pine does not see them.
\_ I have no idea where pine is getting my mails, my
/var/mail/$USER directory is empty with the exception
of these 3 directories, yet pine/mutt says my inbox
has X mails.
\_ It's getting them from those directories. There's no
question about that. However, that does not seem to
be where the mailer is delivering mail. At least,
my mail is just being stuffed into /var/mail/$USER/msg.????
and I am not using procmail or anything else. What
is the default behavior supposed to be for mail
delivery now?
\_ in our .pinerc, add a line like this:
maildir-location=/var/username/brett
maildir-location=/var/mail/$USER
maildir-location=/var/username/mail
\_ Thanks everyone who helped with the Pine issues. I'm always
pleasantly surprised when the motd helps those that don't live &
breath UNIX daily. It's a nice change from the condescending
attitude you generally tend to get at UNIX boards. I was able to
fix Pine by:
1) creating "cur, new, tmp" in /var/mail/$USER directory
2) removing my .procmailrc file
3) removing my .forward which had a spam forward in place
(procmail) |
http://csua.com/feed/