From 5ad95abd711a7a0a619246fd2bb4a7cfe60acc1b Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Thu, 26 Sep 1996 15:57:33 +0000 Subject: No more rpopid field. svn path=/trunk/; revision=162 --- fetchmail.man | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'fetchmail.man') diff --git a/fetchmail.man b/fetchmail.man index 14a41526..ffc95d43 100644 --- a/fetchmail.man +++ b/fetchmail.man @@ -244,11 +244,10 @@ the correct user-id and password for your mailbox account. POP3 versions up to the RFC1225 version supported an alternate authentication mechanism called RPOP intended to remove the security risk inherent in sending unencrypted account passwords across the net -(in RFC1460 this facility was replaced with APOP). If your .fetchmailrc -file specifies an RPOP id and a connection port in the privileged -range (1..1024), +(in RFC1460 this facility was replaced with APOP). If you specify the +RPOP protocol and a connection port in the privileged range (1..1024), .I fetchmail will -ship the id with an RPOP command rather than sending a password. +ship your password entry to the mail server as an RPOP id. (Note: you'll need to be running fetchmail setuid root for RPOP to work -- .I fetchmail @@ -395,7 +394,6 @@ Legal keywords are: protocol (or proto) username (or user) password (or pass) - rpopid remotefolder (or remote) localfolder (or local) mda -- cgit v1.2.3