From owner-freebsd-questions Mon Mar 9 06:36:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21633 for freebsd-questions-outgoing; Mon, 9 Mar 1998 06:36:48 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa2-24.ix.netcom.com [206.214.137.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21584 for ; Mon, 9 Mar 1998 06:36:19 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id GAA00364; Mon, 9 Mar 1998 06:36:12 -0800 (PST) (envelope-from tomdean) Date: Mon, 9 Mar 1998 06:36:12 -0800 (PST) Message-Id: <199803091436.GAA00364@ix.netcom.com> From: Thomas Dean To: No_mail@yahoo.com CC: questions@FreeBSD.ORG In-reply-to: <3503F779.33AE@yahoo.com> (message from Don on Mon, 09 Mar 1998 08:06:49 -0600) Subject: Re: fetchmailrc Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look at 'man fetchmail', carefully. ... It's possible to specify more than one user per server (this is only likely to be useful when running fetchmail in daemon mode as root). The `user' keyword leads off a user description, and every user specification in a multi- user entry must include it. Here's an example: poll pop.provider.net proto pop3 port 3111 user jsmith with pass secret1 is smith here user jones with pass secret2 is jjones here This associates the local username `smith' with the pop.provider.net username `jsmith' and the local username `jjones' with the pop.provider.net username `jones'. ... Be careful with the permissions on the .fetchmailrc, it contains passwords. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message