-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
"Markus Stausberg" <[EMAIL PROTECTED]> writes: > I dont want to use APOP auth, because not all of the clients can > say that word (e.g. kmail, as of slink), but is it true that the only > alternative is to store a worthy login passwd at every client's mail > reader (retyping is unbearable.) ? There is always RPOP, if kmail can handle that. And if you can find a POP3 server which handles it. But RPOP is a Bad Thing (tm). It relies on the username returned by identd. If you trust the client systems to return an accurate identd, then you might consider it... As an alternative. Do you have shared home directories? If so, how about delivering mail directly to the home directory - say for instance ~/.mail? Then folks can treat it like a standard Unix mbox, which more clients will support. One word of warning with that method. If you're using NFS, make sure NFS file locking is supported by the clients and the server. Otherwise you'll wind up with mysterious mailbox corruption. - -- Graeme. [EMAIL PROTECTED] "Life's not fair," I reply. "But the root password helps." - BOFH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) iD8DBQE5IAuNPjGH3lNt65URAnnEAKDRO5zHFE9koKfcZHzCNN4KFXzYGgCg0ZvP 8xvi8HGqQwUkTfwlFflN+bw= =OFTO -----END PGP SIGNATURE-----
