5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: passwordless ...
FromSent OnAttachments
Mark T. ValitesJul 10, 2002 12:28 pm 
Sam VarshavchikJul 10, 2002 2:29 pm 
Mark T. ValitesJul 11, 2002 10:12 am 
Sam VarshavchikJul 11, 2002 2:37 pm 
Mark T. ValitesJul 11, 2002 7:02 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Re: passwordless key-based ssh authentication to courier imapdActions...
From:Mark T. Valites (vali@geneseo.edu)
Date:Jul 11, 2002 10:12:50 am
List:net.sourceforge.lists.courier-users

No go. The more & more I think about it, the more I wonder how this even works. I have a feeling the courier imapd binary in /usr/bin/ that does the preauth stuff was made for doing stuff similar to this (& the uw passwdless way in the previous post).

Perhaps it's more of a pine question, but how & when does pine call the ssh-command? Why do I have to specify an inbox or imap server if my mail ends of coming through the ssh command that calls the stdio imapd binary?

Was this type of thing what was in mind for the preauth imapd binary?

On Wed, 10 Jul 2002, Sam Varshavchik wrote:

Date: Wed, 10 Jul 2002 17:29:04 -0400 From: Sam Varshavchik <mrs@courier-mta.com> To: cour@lists.sourceforge.net Subject: [courier-users] Re: passwordless key-based ssh authentication to courier imapd

Mark T. Valites writes:

Is it possible to get passwdless, key based ssh authentication from pine to courier imapd?

Try installing this script as /etc/rimapd, instead of a soft link, with the execute bit set:

#!/bin/sh

exec /usr/lib/courier-imap/bin/imapd $HOME/Maildir 2>/dev/null