Berkeley CSUA MOTD:Entry 45682
Berkeley CSUA MOTD
 
WIKI | FAQ | Tech FAQ
http://csua.com/feed/
2024/11/23 [General] UID:1000 Activity:popular
11/23   

2007/2/7-11 [Computer/SW/Mail] UID:45682 Activity:high
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)
ERROR, url_link recursive (eces.Colorado.EDU/secure/mindterm2) 2024/11/23 [General] UID:1000 Activity:popular
11/23   

You may also be interested in these entries...
2012/10/15-12/4 [Computer/SW/Mail] UID:54501 Activity:nil
10/15   What's the soda email client these days?
        \_ Don't know.  /usr/bin/mail hasn't been working for a while.
        \_ forward to Gmail.
        \_ mutt works for me
	...
2012/8/29-11/7 [Computer/SW/Security] UID:54467 Activity:nil
8/29    There was once a CSUA web page which runs an SSH client for logging
        on to soda.  Does that page still exist?  Can someone remind me of the
        URL please?  Thx.
        \_ what do you mean? instruction on how to ssh into soda?
           \_ No I think he means the ssh applet, which, iirc, was an applet
              that implemented an ssh v1 client.  I think this page went away
	...
2011/11/14-30 [Computer/SW/Security] UID:54228 Activity:nil
11/14   Social Engineering call centers:
        http://www.itbusiness.ca/it/client/en/home/News.asp?id=64887
	...
2011/2/14-4/20 [Computer/SW/Unix] UID:54039 Activity:nil
2/14    You sure soda isn't running windows in disguise?  It would explain the
        uptimes.
        \_ hardly, My winbox stays up longer.
        \_ Nobody cares about uptime anymore brother, that's what web2.0 has
           taught us.  Everything is "stateless".
           \_ You;d think gamers would care more about uptime.
	...
2011/4/6-20 [Computer/SW/Mail, Computer/SW/Unix, Industry/Startup] UID:54078 Activity:nil
4/6     My company is evaluating version control systems. Our two candidates
        are Perforce and Subversion. Anyone worked with both and have good
        arguments one way or the other? (These are the only two options we
        have.) We're most interested in client performance, ease of use, and
        reasonable branching.
        \_ I'll be 'that guy'. If perforce and subversion are optins, why isn't
	...
2010/8/8-9/7 [Computer/SW/Languages/C_Cplusplus, Computer/SW/Languages/Web] UID:53914 Activity:nil
8/8     Trying to make a list of interesting features languages have
        touted as this whole PL field comes around, trying to see if they
        have basis in the culture of the time: feel free to add some/dispute
        1970 C, "portability"
        1980 C++, classes, oop, iterators, streams, functors, templates
             expert systems
	...
2010/7/29-8/9 [Computer/SW/Mail] UID:53905 Activity:nil
7/29    How do I get pine to work with mail? I have 1900 mails and I want
        to delete them. Or is there a better one to use? never learned
        'mail'..
        \_ mutt
           \_ so why doesn't alpine work? What setting should I use to have
              it work with my csua mail folder? Thanks!
	...
2010/3/10-30 [Computer/SW/Mail] UID:53751 Activity:nil
3/10    What email program do people in Cal CS use nowadays?  In my school days
        people used /usr/bin/mail, then RMail in emacs, then VMail in emacs.
        After my days people used Elm, Pine, Mutt (I forgot which order).  In
        my first two jobs we could tell the seniority of fellow engineers based
        on which email program they use at work, because everyone used what
        they used to use in their school years.  In my last two jobs though,
	...
Cache (5472 bytes)
www.courier-mta.org/fud -> www.courier-mta.org/fud/
FUD attack, or when I strongly suspect that someone's merely repeating the same FUD without being aware of its historical background. Rather than having to rebut the same, worn-out FUD every time, I now refer people to this web page. My spirited detractors always seem to forget to mention a few details, before condemning me to the tenth level of Hades.. I think that people need to be aware of the following history before forming any conclusions. All of the following historical timeline was pulled straight out of Google archives. Google files from that time period are somewhat sketchy, but still contain enough detail to piece together most of the key events. Well, as it turned out, Bernstein eventually won this argument, even though working in Crispin's favor (and supporting his position) were certain other technical problems with the RFC 931 document. Maildirs addressed several long-standing shortcomings of the traditional Bezerkeley mbox mail format (the default mail format used by the UW-IMAP server) that have been known for some time. Between 1995 and 1999 Qmail gained popularity until it became the second most popular mail server on the Internet. With Qmail's popularity growing, people began asking Crispin about adding support for Qmail's maildirs to the UW-IMAP server. Crispin, still simmering over losing the flame war over RFC 931, flogged this opportunity for all it was worth. Although he was always quick in gratuitously declining all requests to add maildir support to the UW-IMAP server, he wasn't too forthcoming in explaining his reasoning why maildirs were so supposedly inefficient in an IMAP context. Sometimes he went as far as mentioning some filesystem-specific factors, but that was far from a complete explanation. Furthermore, he never told anyone about his old flame war with Dan Bernstein. Chapter III This remained the status quo until early 2000. After the first few public releases, many people quickly discovered this fast, small, IMAP server, which simply defied the notion that it was not possible to have an efficient IMAP server based on maildirs. People stopped pestering Crispin about adding maildir support to the UW-IMAP server, because a viable, working alternative was now available. Suddenly, Crispin was no longer able to get his jollies by badmouthing maildirs (and taking indirect swipes at Qmail and Bernstein). Publicly, he went on the offensive, claiming that there was something improper, or non-compliant, about the IMAP implementation in Courier (but, like always, short on details). original link) Epilogue And that's how this FUD started. My response to claims that Courier-IMAP is not a compliant IMAP server is very simple: there was no such thing as a "compliant" IMAP server, because Crispin's IMAP specification makes that an impossible goal. RFC 3501 identified over a hundred corrections to RFC 2060. Observe that RFC 3501 does not define a new version of the IMAP protocol. This is a "revised" document, which attempts to clarify and address numerous issues and inaccuracies in the original specification (some of which I noted publicly). And, to make things even more interesting, as of this date there are already several reported errata to 3501. Furthermore, RFC 3501 actually changed the IMAP protocol, adding several new requirements, but it kept the IMAP4rev1 version. In other words: the protocol has changed, but it's still the same protocol, officially. So, how is it possible to define what exactly is a "compliant" IMAP server, when the IMAP specification is such a moving target? I am unable to come up with any other Internet protocol: * of similar complexity * with a similar record of interoperability problems between various clients and servers * that has this evolutionary trend of evolving, changing, and mutating, while still carrying the same same version number Some IMAP clients certainly do have problems with the Courier-IMAP server, from time to time. Crispin always blames Courier-IMAP But, it's just as true that some clients will also have a problem with the UW-IMAP server. It won't take a long time to find published reports of interoperability issues between the UW-IMAP server and some mail clients. My position is that the fault for this lies squarely on the specification. You can take SMTP, or POP3, or IRC, or most any other wire protocol; and have a fairly good chance of having your end result work, more or less, with other software. The same cannot be said for IMAP To have any reasonable chance of coming up with a working client or server, it is always necessary to use a working counterpart, and examine its input or output in order to figure out how IMAP's supposed to work. It's quite obvious to see how some cookies got frosted over this. I also learned (via other channels) of a few lame attempts lobby this rogue Internet provider into changing their mind. I note that the original party line was that the UW-IMAP server is the only well-written IMAP server in world (and the only well-written IMAP mail reader is pine). Recently (and probably because of the recent developments with this ISP), both UW-IMAP and Cyrus are now officially blessed; the apparent goal is a tactical decision to steer people away to these two servers, and away from the uppity Courier. I get the impression that my occasional kind words about UW-IMAP really annoy some people, who are incapable of saying anything nice about Courier, no matter how true it might be.