Segens' Home and Journal Me, my Life, my Interests and my online Journal.

Alpine error etc..(a bug!)

Posted on March 9, 2009

Thanks to my very good friend Chris, who pointed out the spot in the docs that I was not understanding, and providing a sample config entry; The from field in the headers is directly related to your name that is sent to the server... it is the user name sent as far as i can tell..

Anyway, that is fixed.

Then, I didn't know that the INBOX field was soposed to be the server... I thought it was a local path(thats what the help file said...) http://www.ghacks.net/2009/03/05/old-school-linux-email-with-alpine/ helped with that, its the only page i can see that shows an example entry for that space. So, server there, and i can recieve mail!  Also found that you can specify the user in that field with '/user=username' 

Then the password prompt for recieving started bugging out; placing itself off the side of the screen or throught the options list... and taking double or tripple key strokes to recognise letters. Apparently its a bug thats caused when Alpine attempts to login using "rsh",
the UNIX remote shell program.
https://bugs.launchpad.net/ubuntu/+source/alpine/+bug/199463

Including "NoRsh" will cause connections to this server to skip
the "rsh" attempt.
http://www.washington.edu/alpine/tech-notes/config-notes.html

So, added '/norsh' and its fine...Although then it fails on the secure connection, then re-tries plain, and connects fine then. I think I need an SSL library installed to fix that...

While at http://www.washington.edu/alpine/tech-notes/config-notes.html
I noticed the paramiters for '/user' It can be used on all of the server configuration fields, not just this one, so that would have been the fix I needed to begin with, that changing the 'From:'  field fixed.

Why couldn't they include all that info in that config-notes file internally in the program? would make it a lot easoer to do this for us beginers with terminal programs.

Comments (1) Trackbacks (0)
  1. I tag /novalidate-cert/ssl onto the end of my inbox server, to get the secure connection.

    Regarding the internal documentation issue: The code is open-source – why don’t you write a patch for that, and submit it to the Alpine project? Or help write some better external documentation? I know you have the spare time… ;)

Trackbacks are disabled.