On Wed, 2004-06-16 at 15:31, Bowie Bailey wrote:

> The password needs to be encrypted in the userdb file.  The usual way
> to do it is like this:
> 
>   userdbpw | userdb username pop3schnobs set pop3pw
> 

Thanks for your (and Tim's) help. Now it works, and after all the
solution was quite simple.

I'd still like to file a complaint, as I was unable to gather this from
the documentation. I took the encoding of passwords by means of userdbpw
as strictly optional -- even in hindsight, I can find no indication
about it being imperative.

> > Should pass not be sent as plaintext, but encoded/encrypted 
> > in any way? 

> The password should be sent plaintext by the client.

I asked because I have a faded memory about some allegedly "plain" login
that in fact turned out to be base-64 encoded. Must have been something else.


cu,
Schnobs



-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to