Subject: Re: Trying to get Web Alpine to work - msg#00092

Previous Message by Date:

Re: [Alpine-announce] Alpine 1.10 is now available

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Jeff Franklin wrote: > This note is to announce the availability of the Alpine Message System > version 1.10. This release introduces some new functionality and > addresses some bugs found in earlier versions. FYI, I updated the FreeBSD port a few days ago, no complaints yet. :) The binary packages for 1.10 should start hitting the FTP servers soon. hth, Doug - -- This .signature sanitized for your protection -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iEYEAREDAAYFAkfisOgACgkQyIakK9Wy8PuQxQCeNHzloDtCwerLjUCE49x3NWiu /UsAoIW8i1KU9zoOz4BA02zqvt0kjHoZ =44dK -----END PGP SIGNATURE-----

Next Message by Date:

OS X Keychain authentication support?

Bump for no responses. Any other suggestions as to where to look/ ask? -- KeS ==================================================== Can anyone point me at documentation on this feature? When I start up Alpine, I am asked for password, then asked if I want to cache the password for next logon. I choose default (Y)es, then get a message at the bottom of the main menu: "[Stop "Preserve passwords?" prompts by deleting Alpine Keychain entry]" In fact, my password is never cached (I have to enter it each time I start Alpine); and AFAIK there is no Alpine Keychain entry, at least not one that I can find. This behavior is constant across Alpine 1.00 and 1.10. I'm running 10.5.x (Leopard), and using dovecot as my IMAP service. Both releases were downloaded as tarballs and compiled successfully with the osx OS type, on the same system they are installed on and executed from. I've leafed and grepped through the docs several times without finding any reference to an OS X specific authenticator or password feature, so I'm kind of lost now. Tx! KeS

Previous Message by Thread:

Re: Trying to get Web Alpine to work

Greetings - On 14 Mar 2008, at 21:39, Joshua Daniel Franklin wrote: By the way, if you ever get it fully configured I would really appreciate it if you could post a summary of the steps. As promised, I've knocked up a PDF document describing the steps I've gone through to get Web Alpine up and running on our Sun Solaris test server. This is from the current Alpine-1.10 source distribution. We are using the Blastwave-distributed versions of OpenSSL and OpenLDAP: hence the directory paths beginning "/opt/csw". NB: If building from source you need the Open LDAP Developer kit installing (Blastwave name "openldap_devel") I'd recommend building this version using "--with-ldap" even if you aren't planning to use LDAP at the moment... there's a bijou bug lurking that otherwise gives a Nasty Error Message when the user clicks on "Configuration" then the "Address Books" tab. (I've reported this.) You can find the document at http://www-users.york.ac.uk/~pmb1/alpine/InstallingWebAlpine.pdf Do note that it is largely a set of notes for our/my own reference, so you'll have to alter path names, decide on your own settings, etc. However the sequence has let me get Web Alpine up and running, and so far I'm very very impressed by its functionality and speed. (And the mocked-up idea for the revised user interface in v2.0 will make it look even better!) Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

Next Message by Thread:

Re: Trying to get Web Alpine to work

Greetings - On 20 Mar 2008, at 23:06, Gary Mills wrote: I didn't know that web alpine could be used without Kerberos, as it seemed to depend on Kerberos for its single-signon facility. How did you get it to work without Kerberos? My ignorance is a wonderful thing... it didn't occur to me that it might *require* Kerberos so I assumed it didn't. Basically when I ran the ./configure script I added "--without-krb5" and it configured and compiled cleanly. The Web Alpine web pages aren't password-protected themselves. Instead you complete a form on its login page to supply your username and password for the IMAP server; Web Alpine then uses these to connect, presumably caching them for any subsequent authentications that might become necessary. So I'm guessing I'm just not using single-signon... I assume that would let me authenticate just once to a set of web servers and access any of their content, including the Web Alpine service, without having to enter my username/password again. We treat our Webmail Service as a standalone service, hence for our needs we use Web Alpine just fine without either Kerberos or the UW Single Signon Cookie. Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *