Import translated manuals from JM CVS Repository.

[linuxjm/jm.git] / manual / fetchmail / draft / man1 / fetchmail.1

'\" t
.\" ** The above line should force tbl to be used as a preprocessor **
.\"
.\" Man page for fetchmail
.\"
.\" For license terms, see the file COPYING in this directory.
.\" 
.\"WORD: message terminator     ¥á¥Ã¥»¡¼¥¸½ªÃ¼»Ò
.\"WORD: preauthentication      ͽÈ÷ǧ¾Ú
.\"WORD: poll name      poll ̾
.\"WORD: via name       via ̾
.\"WORD: server greeting time ¥µ¡¼¥Ð¤Î¥°¥ê¡¼¥Æ¥£¥ó¥°²ó¿ô
.\"WORD: public SSL certificate ¸ø³« SSL ¾ÚÌÀ½ñ
.\"WORD: negotiation    Ä´Ää
.\"WORD: validation     ¿È¸µ³Îǧ
.\"WORD: well known port        ´ûÃΤΥݡ¼¥È
.\"WORD: originator     º¹½Ð¿Í
.\" 
.\" Translated Wed Aug 18 22:35:36 JST 1999
.\"         by FUJIWARA Teruyoshi <fujiwara@linux.or.jp>
.\" Updated Sun Jan 16 04:43:32 JST 2000 to match fetchmail-5.2.3
.\"         by FUJIWARA Teruyoshi <fujiwara@linux.or.jp>
.\" Updated Tue Dec 26 05:47:25 JST 2000
.\"         by Yuichi SATO <sato@complex.eng.hokudai.ac.jp>
.\" Updated Sat Jul 14 09:59:59 JST 2001
.\"         by Yuichi SATO <ysato@h4.dion.ne.jp>
.\" Updated Sun Oct 14 01:24:38 JST 2001 by Yuichi SATO
.\" Updated Fri Nov  9 20:17:22 JST 2001 by Yuichi SATO
.\" Updated & Modified Sat Jan 19 14:57:52 JST 2002 by Yuichi SATO
.\" 
.TH fetchmail 1
.\"O .SH NAME
.SH ̾Á°
.\"O fetchmail \- fetch mail from a POP, IMAP, ETRN, or ODMR-capable server
fetchmail \- POP, IMAP, ETRN, ODMR µ¡Ç½¤ò»ý¤Ä¥µ¡¼¥Ð¤«¤é¥á¡¼¥ë¤ò¼èÆÀ¤¹¤ë

.\"O .SH SYNOPSIS
.SH ½ñ¼°
\fBfetchmail\fR [\fIoption...\fR] [\fImailserver...\fR]
.br
\fBfetchmailconf\fR

.\"O .SH DESCRIPTION
.SH ÀâÌÀ
.\"O .I fetchmail
.\"O is a mail-retrieval and forwarding utility; it fetches mail from
.\"O remote mailservers and forwards it to your local (client) machine's
.\"O delivery system.  You can then handle the retrieved mail using normal
.\"O mail user agents such as \fImutt\fR(1), \fIelm\fR(1) or \fIMail\fR(1).
.\"O The \fIfetchmail\fR utility can be run in a daemon mode to repeatedly
.\"O poll one or more systems at a specified interval.
.I fetchmail
¤Ï¥á¡¼¥ë¤ò¼èÆÀ¡¦Å¾Á÷¤¹¤ë¤¿¤á¤Î¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ç¤¹¡£
.I fetchmail
¤Ï¥ê¥â¡¼¥È¤Î¥á¡¼¥ë¥µ¡¼¥Ð¤«¤é¥á¡¼¥ë¤ò¼èÆÀ¤·¡¢
¤³¤ì¤ò¥í¡¼¥«¥ë (¥¯¥é¥¤¥¢¥ó¥È) ¥Þ¥·¥ó¤ÎÇÛÁ÷¥·¥¹¥Æ¥à¤ËžÁ÷¤·¤Þ¤¹¡£
¼õ¤±¼è¤Ã¤¿¥á¡¼¥ë¤Ï¡¢¤½¤Î¸å \fImutt\fR(1), \fIelm\fR(1), \fIMail\fR(1) ¤Ê¤É¡¢
ÉáÄ̤Υ᡼¥ë¥æ¡¼¥¶¥¨¡¼¥¸¥§¥ó¥È¤Ç°·¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
\fIfetchmail\fR ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ï¥Ç¡¼¥â¥ó¥â¡¼¥É¤Ç¼Â¹Ô¤·¡¢
»ØÄꤷ¤¿»þ´Ö´Ö³Ö¤Ç 1 ¤Ä¤¢¤ë¤¤¤ÏÊ£¿ô¤Î¥·¥¹¥Æ¥à¤ò
·«¤êÊÖ¤·¥Ý¡¼¥ê¥ó¥°¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.PP
.\"O The
.\"O .I fetchmail
.\"O program can gather mail from servers supporting any of the common
.\"O mail-retrieval protocols: POP2, POP3, IMAP2bis, IMAP4, and IMAPrev1.
.I fetchmail
¥×¥í¥°¥é¥à¤Ï°ìÈÌŪ¤Ê¥á¡¼¥ë¼èÆÀ¥×¥í¥È¥³¥ë
(POP2, POP3, IMAP2bis, IMAP4, IMAPrev1) ¤Î
¤¤¤º¤ì¤«¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¥µ¡¼¥Ð¤«¤é¥á¡¼¥ë¤ò½¸¤á¤Æ¤¯¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.\"O It can also use the ESMTP ETRN extension and ODMR.  (The RFCs describing all
.\"O these protocols are listed at the end of this manual page.)
¤Þ¤¿¡¢ESMTP ¤Î ETRN ³ÈÄ¥¤È ODMR ¤ò»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
(¤³¤ì¤é¤Î¥×¥í¥È¥³¥ë¤òÀâÌÀ¤·¤Æ¤¤¤ë RFC Á´¤Æ¤Ï¡¢
¤³¤Î¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤ÎºÇ¸å¤ËÎóµó¤·¤Þ¤¹¡£)
.PP
.\"O While
.\"O .I fetchmail
.\"O is primarily intended to be used over on-demand TCP/IP links (such as
.\"O SLIP or PPP connections), it may also be useful as a message transfer
.\"O agent for sites which refuse for security reasons to permit
.\"O (sender-initiated) SMTP transactions with sendmail.
.I fetchmail
¤Ï´ðËÜŪ¤Ë (SLIP ¤ä PPP Åù¤Î)
¥ª¥ó¥Ç¥Þ¥ó¥É TCP/IP Àܳ¾å¤Ç»È¤¦¤¿¤á¤Î¤â¤Î¤Ç¤¹¤¬¡¢
sendmail ¤ò»È¤Ã¤¿ (Á÷¿®¼Ô³«»Ï¤Î) SMTP ¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤ò
¥»¥­¥å¥ê¥Æ¥£¾å¤ÎÍýͳ¤«¤éǧ¤á¤Ê¤¤¥µ¥¤¥È¤Ç¤Ï¡¢
¥á¥Ã¥»¡¼¥¸Å¾Á÷¥¨¡¼¥¸¥§¥ó¥È¤È¤·¤Æ¤âÌòΩ¤Ä¤«¤â¤·¤ì¤Þ¤»¤ó¡£
.PP
.\"O As each message is retrieved \fIfetchmail\fR normally delivers it via SMTP to
.\"O port 25 on the machine it is running on (localhost), just as though it
.\"O were being passed in over a normal TCP/IP link.  The mail will then be
.\"O delivered locally via your system's MDA (Mail Delivery Agent, usually
.\"O \fIsendmail\fR(8) but your system may use a different one such
.\"O as \fIsmail\fR, \fImmdf\fR, \fIexim\fR, or \fIqmail\fR).  All the
.\"O delivery-control mechanisms (such as \fI.forward\fR files) normally
.\"O available through your system MDA and local delivery agents will
.\"O therefore work.
¤½¤ì¤¾¤ì¤Î¥á¥Ã¥»¡¼¥¸¤ò¼èÆÀ¤¹¤ë¤È¡¢
Ä̾ï \fIfetchmail\fR ¤Ï¼«¿È¤¬Æ°ºî¤·¤Æ¤¤¤ë¥Þ¥·¥ó (localhost) ¤Î
25 È֥ݡ¼¥È¤Ë SMTP ·Ðͳ¤Ç¤³¤Î¥á¥Ã¥»¡¼¥¸¤òÇÛÁ÷¤·¤Þ¤¹¡£
¤³¤ÎÆ°ºî¤Ï¡¢¤Á¤ç¤¦¤ÉÄ̾ï¤Î TCP/IP Àܳ¾å¤Ç
¥á¥Ã¥»¡¼¥¸¤¬ÅϤµ¤ì¤¿¤«¤Î¤è¤¦¤Ë¹Ô¤ï¤ì¤Þ¤¹¡£
¼¡¤Ë¡¢¥á¡¼¥ë¤Ï¥·¥¹¥Æ¥à¤Î MDA (Mail Delivery Agent (¥á¡¼¥ëÇÛÁ÷¥¨¡¼¥¸¥§¥ó¥È)¡¢
ÉáÄÌ¤Ï \fIsendmail\fR(8) ¤Ç¤¹¤¬¡¢¥·¥¹¥Æ¥à¤Ë¤è¤Ã¤Æ¤Ï
\fIsmail\fR, \fImmdf\fR, \fIexim\fR, \fIqmail\fR Åù¤¬
»È¤ï¤ì¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó) ·Ðͳ¤Ç¥í¡¼¥«¥ë¤ËÇÛÁ÷¤µ¤ì¤Þ¤¹¡£
¤·¤¿¤¬¤Ã¤Æ¡¢ÇÛÁ÷À©¸æµ¡¹½ (\fI.forward\fR ¥Õ¥¡¥¤¥ëÅù) ¤Ï¡¢
¥·¥¹¥Æ¥à¤Î MDA ¤È¥í¡¼¥«¥ëÇÛÁ÷¥¨¡¼¥¸¥§¥ó¥È¤òÄ̤¸¤Æ
Á´¤ÆÄ̾ïÄ̤ê»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.PP
.\"O If no port 25 listener is available, but your fetchmail compilation
.\"O detected or was told about a reliable local MDA, it will use that MDA
.\"O for local delivery instead.  At build time, fetchmail normally looks
.\"O for executable 
.\"O .IR procmail (1)
.\"O and 
.\"O .IR sendmail (1)
.\"O binaries.
25 È֥ݡ¼¥È¤Î¥ê¥¹¥Ê¤Ï¤Ê¤¤¤¬¡¢fetchmail ¤Î¥³¥ó¥Ñ¥¤¥ë»þ¤Ë
¿®Íê¤Ç¤­¤ë¥í¡¼¥«¥ë MDA ¤ò¸¡ÃΤޤ¿¤Ï»ØÄꤵ¤ì¤¿¾ì¹ç¡¢
Âå¤ï¤ê¤È¤·¤Æ¥í¡¼¥«¥ëÇÛ¿®¤Ë¤½¤Î MDA ¤ò»È¤¤¤Þ¤¹¡£
Ä̾¥Ó¥ë¥É»þ¤Ë fetchmail ¤Ï
¼Â¹Ô²Äǽ¥×¥í¥°¥é¥à
.IR procmail (1)
¤È
.IR sendmail (1)
¤Î¥Ð¥¤¥Ê¥ê¤òõ¤·¤Þ¤¹¡£
.PP
.\"O If the program
.\"O .I fetchmailconf
.\"O is available, it will assist you in setting up and editing a
.\"O fetchmailrc configuration.  It runs under X and requires that the
.\"O language Python and the Tk toolkit be present on your system.  If
.\"O you are first setting up fetchmail for single-user mode, it is
.\"O recommended that you use Novice mode.  Expert mode provides
.\"O complete control of fetchmail configuration, including the
.\"O multidrop features.  In either case, the `Autoprobe' button
.\"O will tell you the most capable protocol a given mailserver
.\"O supports, and warn you of potential problems with that server.
¥×¥í¥°¥é¥à
.I fetchmailconf
¤¬»ÈÍѲÄǽ¤Ç¤¢¤ì¤Ð¡¢¤³¤Î¥×¥í¥°¥é¥à¤ò»È¤Ã¤Æ
fetchmailrc ¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ò³Ú¤ËÀßÄꡦÊÔ½¸¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤Î¥×¥í¥°¥é¥à¤Ï X ¾å¤ÇÆ°ºî¤·¡¢
¤Þ¤¿¥·¥¹¥Æ¥à¾å¤Ë Python ¸À¸ì¤È Tk ¥Ä¡¼¥ë¥­¥Ã¥È¤¬¤¢¤ë¤³¤È¤¬É¬ÍפǤ¹¡£
ñÆȥ桼¥¶¥â¡¼¥ÉÍѤ˽é¤á¤Æ fetchmail ¤òÀßÄꤹ¤ë¾ì¹ç¤Ë¤Ï¡¢
½é¿´¼Ô¥â¡¼¥É (Novice mode) ¤ò»È¤¦¤³¤È¤ò¤ª´«¤á¤·¤Þ¤¹¡£
¾åµé¼Ô¥â¡¼¥É (Expert mode) ¤ò»È¤¦¤È¡¢
¥Þ¥ë¥Á¥É¥í¥Ã¥×µ¡Ç½¤ò´Þ¤à fetchmail ¤ÎÀßÄê¤ò´°Á´¤ËÀ©¸æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤É¤Á¤é¤Î¾ì¹ç¤Ç¤â¡¢`Autoprobe (¼«Æ°¸¡½Ð)' ¥Ü¥¿¥ó¤ò²¡¤¹¤È¡¢
»ØÄꤵ¤ì¤¿¥á¡¼¥ë¥µ¡¼¥Ð¤¬ºÇ¤â¤¦¤Þ¤¯¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¥×¥í¥È¥³¥ë¤ò¶µ¤¨¤Æ¤¯¤ì¡¢
¤½¤Î¥µ¡¼¥Ð¤Çµ¯¤³¤ë²ÄǽÀ­¤¬¤¢¤ëÌäÂê¤â»ØŦ¤·¤Æ¤¯¤ì¤Þ¤¹¡£

.\"O .SH GENERAL OPERATION
.SH °ìÈÌŪ¤ÊÁàºî
.\"O The behavior of
.\"O .I fetchmail
.\"O is controlled by command-line options and a run control file,
.\"O .IR ~/.fetchmailrc\fR ,
.\"O the syntax of which we describe in a later section (this file is what
.\"O the \fIfetchmailconf\fR program edits).  Command-line options override
.\"O .I ~/.fetchmailrc
.\"O declarations.
.I fetchmail
¤ÎÆ°ºî¤Ï¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤È¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë
.IR ~/.fetchmailrc\fR
¤ÇÀ©¸æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë¤Îʸˡ¤Ï¸å¤Î¥»¥¯¥·¥ç¥ó¤ÇÀâÌÀ¤·¤Þ¤¹
(¤³¤Î¥Õ¥¡¥¤¥ë¤Ï \fIfetchmailconf\fR ¥×¥í¥°¥é¥à¤¬ÊÔ½¸¤·¤Þ¤¹)¡£
¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤Ï¡¢
.I ~/.fetchmailrc
¤Ç¤ÎÀë¸À¤ò¾å½ñ¤­»ØÄꤷ¤Þ¤¹¡£
.PP
.\"O Each server name that you specify following the options on the
.\"O command line will be queried.  If you don't specify any servers
.\"O on the command line, each `poll' entry in your 
.\"O .I ~/.fetchmailrc
.\"O file will be queried.
Ì䤤¹ç¤ï¤»¤Ï¡¢¥³¥Þ¥ó¥É¥é¥¤¥ó¤Î¥ª¥×¥·¥ç¥ó¤Î¸å¤Ë»ØÄꤷ¤¿
Á´¤Æ¤Î¥µ¡¼¥Ð¤ËÂФ·¤Æ¹Ô¤ï¤ì¤Þ¤¹¡£
¥³¥Þ¥ó¥É¹Ô¤Ç¥µ¡¼¥Ð¤ò»ØÄꤷ¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢
.I ~/.fetchmailrc
¥Õ¥¡¥¤¥ë¤Î `poll' ¥¨¥ó¥È¥ê¤½¤ì¤¾¤ì¤ËÂФ·¤ÆÌ䤤¹ç¤ï¤»¤¬¹Ô¤ï¤ì¤Þ¤¹¡£
.PP
.\"O To facilitate the use of
.\"O .I fetchmail
.\"O in scripts and pipelines, it returns an appropriate exit code upon 
.\"O termination -- see EXIT CODES below.
.I fetchmail
¤Ï¡¢¥¹¥¯¥ê¥×¥È¤ä¥Ñ¥¤¥×¥é¥¤¥ó¤Ç»È¤¤¤ä¤¹¤¤¤è¤¦¤Ë¡¢
½ªÎ»»þ¤ËŬÀڤʽªÎ»¥³¡¼¥É¤òÊÖ¤¹¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
¸å½Ò¤Î¡Ö½ªÎ»¥³¡¼¥É¡×¥»¥¯¥·¥ç¥ó¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
.PP
.\"O The following options modify the behavior of \fIfetchmail\fR.  It is
.\"O seldom necessary to specify any of these once you have a
.\"O working \fI.fetchmailrc\fR file set up.
°Ê²¼¤Î¥ª¥×¥·¥ç¥ó¤Ç \fIfetchmail\fR ¤ÎÆ°ºî¤¬ÊѤï¤ê¤Þ¤¹¡£
°ìÅÙ¤¦¤Þ¤¯Æ°ºî¤¹¤ë \fI.fetchmailrc\fR ¥Õ¥¡¥¤¥ë¤¬ÀßÄê¤Ç¤­¤ì¤Ð¡¢¤½¤Î¸å¤Ï
¤³¤ì¤é¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ëɬÍפϤۤȤó¤É¤Ê¤¤¤Ç¤·¤ç¤¦¡£
.PP
.\"O Almost all options have a corresponding keyword which can be used to
.\"O declare them in a 
.\"O .I fetchmailrc
.\"O file.
¤Û¤È¤ó¤ÉÁ´¤Æ¤Î¥ª¥×¥·¥ç¥ó¤Ë¤ÏÂбþ¤¹¤ë¥­¡¼¥ï¡¼¥É¤¬¤¢¤ê¡¢¤³¤ì¤é¤Ï
.I fetchmailrc
¥Õ¥¡¥¤¥ë¤ÇÀë¸À¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.PP
.\"O Some special options are not covered here, but are documented instead
.\"O in sections on AUTHENTICATION and DAEMON MODE which follow.
¤³¤³¤Ç¤Ï°ìÉô¤ÎÆüì¤Ê¥ª¥×¥·¥ç¥ó¤ÏÀâÌÀ¤·¤Æ¤ª¤é¤º¡¢
Âå¤ï¤ê¤Ë¸å½Ò¤Î¡Öǧ¾Ú¡×¤È¡Ö¥Ç¡¼¥â¥ó¥â¡¼¥É¡×¤Ë´Ø¤¹¤ë¥»¥¯¥·¥ç¥ó¤ÇÀâÌÀ¤·¤Æ¤¤¤Þ¤¹¡£
.\"O .SS General Options
.SS °ìÈÌÀßÄê¤Î¥ª¥×¥·¥ç¥ó
.TP
.B \-V, --version
.\"O Displays the version information for your copy of 
.\"O .I fetchmail.
.\"O No mail fetch is performed.
.\"O Instead, for each server specified, all the option information
.\"O that would be computed if
.\"O .I fetchmail
.\"O were connecting to that server is displayed.  Any non-printables in
.\"O passwords or other string names are shown as backslashed C-like
.\"O escape sequences.  This option is useful for verifying that your
.\"O options are set the way you want them.
¤ª»È¤¤¤Î
.I fetchmail
¤Î¥Ð¡¼¥¸¥ç¥ó¾ðÊó¤òɽ¼¨¤·¤Þ¤¹¡£¥á¡¼¥ë¤Î¼èÆÀ¤Ï¹Ô¤¤¤Þ¤»¤ó¡£¤½¤ÎÂå¤ï¤ê¡¢
.I fetchmail
¤¬¼ÂºÝ¤Ë¥µ¡¼¥Ð¤ËÀܳ¤·¤¿¾ì¹ç¤Ë»È¤ï¤ì¤ë¤Ï¤º¤Î¥ª¥×¥·¥ç¥ó¾ðÊóÁ´¤Æ¤¬¡¢
»ØÄꤵ¤ì¤Æ¤¤¤ë¤½¤ì¤¾¤ì¤Î¥µ¡¼¥Ð¤Ë¤Ä¤¤¤Æɽ¼¨¤µ¤ì¤Þ¤¹¡£
¥Ñ¥¹¥ï¡¼¥É¤ä¤½¤Î¾¤Î̾¾Îʸ»úÎó¤Ë´Þ¤Þ¤ì¤ëɽ¼¨ÉÔ²Äǽ¤Êʸ»ú¤Ï¡¢
C ¸À¸ì¤ÈƱÍͤ˥Х寥¹¥é¥Ã¥·¥å¤ò»È¤Ã¤¿
¥¨¥¹¥±¡¼¥×¥·¡¼¥±¥ó¥¹¤È¤·¤Æɽ¼¨¤µ¤ì¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢
¥ª¥×¥·¥ç¥ó¤¬´õ˾Ä̤ê¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Î¤«¤á¤ëºÝ¤ËÊØÍø¤Ç¤¹¡£
.TP
.B \-c, --check
.\"O Return a status code to indicate whether there is mail waiting,
.\"O without actually fetching or deleting mail (see EXIT CODES below).
.\"O This option turns off daemon mode (in which it would be useless).  It
.\"O doesn't play well with queries to multiple sites, and doesn't work
.\"O with ETRN or ODMR.  It will return a false positive if you leave read but
.\"O undeleted mail in your server mailbox and your fetch protocol can't
.\"O tell kept messages from new ones.  This means it will work with IMAP,
.\"O not work with POP2, and may occasionally flake out under POP3.
¼ÂºÝ¤Ë¤Ï¥á¡¼¥ë¤Î¼èÆÀ¤äºï½ü¤ò¹Ô¤ï¤º¡¢
¼èÆÀÂÔ¤Á¤Î¥á¡¼¥ë¤¬¤¢¤ë¤«¤É¤¦¤«¤ò¼¨¤¹¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤À¤±¤òÊÖ¤·¤Þ¤¹
(¸å½Ò¤Î¡Ö½ªÎ»¥³¡¼¥É¡×¤ò»²¾È)¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¥Ç¡¼¥â¥ó¥â¡¼¥É¤ò̵¸ú¤Ë¤·¤Þ¤¹ (̵°ÕÌ£¤Ë¤Ê¤ë¤¿¤á)¡£
Ê£¿ô¥µ¥¤¥È¤Ø¤ÎÌ䤤¹ç¤ï¤»¤Ï¤¦¤Þ¤¯Æ°ºî¤·¤Þ¤»¤ó¤·¡¢
ETRN ¤ä ODMR ¤Ç¤âÆ°ºî¤·¤Þ¤»¤ó¡£
´ûÆɤǤ¢¤ë¤¬ºï½ü¤µ¤ì¤Æ¤¤¤Ê¤¤¥á¡¼¥ë¤¬¥µ¡¼¥Ð¤Î¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤Ë»Ä¤Ã¤Æ¤ª¤ê¡¢
¤«¤Ä¥á¡¼¥ë¼èÆÀ¤Î¥×¥í¥È¥³¥ë¤¬Êݸ¤µ¤ì¤Æ¤¤¤ë¥á¥Ã¥»¡¼¥¸¤È
¿·¤·¤¤¥á¥Ã¥»¡¼¥¸¤ò¶èÊ̤Ǥ­¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢µ¶¤òɽ¤¹Àµ¤ÎÃͤ¬ÊÖ¤µ¤ì¤Þ¤¹¡£
¤Ä¤Þ¤ê¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï IMAP ¤Ç¤ÏÆ°ºî¤·¡¢POP3 ¤Ç¤ÏÆ°ºî¤·¤Þ¤»¤ó¡£
¤Þ¤¿¡¢POP3 ¤Ç¤Ï»þ¡¹¼ºÇÔ¤¹¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
.TP
.B \-s, --silent
.\"O Silent mode.  Suppresses all progress/status messages that are
.\"O normally echoed to standard error during a fetch (but does not
.\"O suppress actual error messages).  The --verbose option overrides this.
ÀŽͥ⡼¥É¡£Ä̾ï¤Ï¥á¡¼¥ë¼èÆÀ¤ÎÅÓÃæ¤Ëɸ½à¥¨¥é¡¼½ÐÎϤ˽ÐÎϤµ¤ì¤ë¡¢
¿Ê¹Ô¾õ¶·/¥¹¥Æ¡¼¥¿¥¹¥á¥Ã¥»¡¼¥¸¤òÁ´¤Æ»ß¤á¤Þ¤¹
(¤·¤«¤·¡¢¼ÂºÝ¤Î¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Ï»ß¤á¤Þ¤»¤ó)¡£
--verbose ¥ª¥×¥·¥ç¥ó¤Ï¤³¤Î¥ª¥×¥·¥ç¥ó¤ò¾å½ñ¤­¤·¤Þ¤¹¡£
.TP
.B \-v, --verbose
.\"O Verbose mode.  All control messages passed between 
.\"O .I fetchmail
.\"O and the mailserver are echoed to stdout.  Overrides --silent.
.\"O Doubling this option (-v -v) causes extra diagnostic information
.\"O to be printed. 
¾ÜºÙɽ¼¨¥â¡¼¥É¡£
.I fetchmail
¤È¥á¡¼¥ë¥µ¡¼¥Ð¤Î´Ö¤Ç¤ä¤ê¤È¤ê¤µ¤ì¤¿À©¸æ¥á¥Ã¥»¡¼¥¸¤ò
Á´¤Æɸ½à½ÐÎϤ˽ÐÎϤ·¤Þ¤¹¡£
--silent ¥ª¥×¥·¥ç¥ó¤ò¾å½ñ¤­¤·¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò 2 ¤ÄÉÕ¤±¤ë¤È (-v -v)¡¢ÄɲäοÇÃǾðÊ󤬽ÐÎϤµ¤ì¤Þ¤¹¡£
.\"O .SS Disposal Options
.SS ¥á¡¼¥ë¤Î°·¤¤¤Ë´Ø¤¹¤ë¥ª¥×¥·¥ç¥ó
.TP
.B \-a, --all
.\"O (Keyword: fetchall)
(¥­¡¼¥ï¡¼¥É: fetchall)
.\"O Retrieve both old (seen) and new messages from the mailserver.  The
.\"O default is to fetch only messages the server has not marked seen.
.\"O Under POP3, this option also forces the use of RETR rather than TOP.
.\"O Note that POP2 retrieval behaves as though --all is always on (see
.\"O RETRIEVAL FAILURE MODES below) and this option does not work with ETRN
.\"O or ODMR.
¸Å¤¤ (´ûÆÉ) ¥á¥Ã¥»¡¼¥¸¤È¿·¤·¤¤¥á¥Ã¥»¡¼¥¸¤ò
ξÊý¤È¤â¥á¡¼¥ë¥µ¡¼¥Ð¤«¤é¼èÆÀ¤·¤Þ¤¹¡£
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¥µ¡¼¥Ð¤¬´ûÆɤΰõ¤òÉÕ¤±¤Æ¤¤¤Ê¤¤¥á¥Ã¥»¡¼¥¸¤À¤±¤ò¼èÆÀ¤·¤Þ¤¹¡£
POP3 ¤ò»È¤¦¾ì¹ç¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È
TOP ¤Ç¤Ï¤Ê¤¯É¬¤º RETR ¤¬»È¤ï¤ì¤Þ¤¹¡£
POP2 ¤Î¥á¡¼¥ë¼èÆÀ¤Ï¡¢--all ¤¬¾ï¤ËÍ­¸ú¤Ç¤¢¤ë¤«¤Î¤è¤¦¤ËÆ°ºî¤·¤Þ¤¹
(¸å½Ò¤Î¡Ö¼èÆÀ¼ºÇԥ⡼¥É¡×¤ò»²¾È)¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï ETRN ¤È ODMR ¤Ç¤ÏÆ°ºî¤·¤Þ¤»¤ó¡£
.TP
.B \-k, --keep
.\"O (Keyword: keep)
(¥­¡¼¥ï¡¼¥É: keep)
.\"O Keep retrieved messages on the remote mailserver.  Normally, messages 
.\"O are deleted from the folder on the mailserver after they have been retrieved.
.\"O Specifying the 
.\"O .B keep 
.\"O option causes retrieved messages to remain in your folder on the
.\"O mailserver.  This option does not work with ETRN or ODMR.
¼èÆÀ¤·¤¿¥á¥Ã¥»¡¼¥¸¤ò¥ê¥â¡¼¥È¤Î¥á¡¼¥ë¥µ¡¼¥Ð¤Ë»Ä¤·¤Þ¤¹¡£
Ä̾ï¤Ï¡¢¥á¡¼¥ë¤ò¼èÆÀ¤·¤¿¸å¤Ë
¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥Õ¥©¥ë¥À¤«¤é¥á¥Ã¥»¡¼¥¸¤¬ºï½ü¤µ¤ì¤Þ¤¹¡£
.B keep 
¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È¡¢
¼èÆÀ¤·¤¿¥á¥Ã¥»¡¼¥¸¤Ï¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥æ¡¼¥¶¤Î¥Õ¥©¥ë¥À¤Ë»Ä¤ê¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï ETRN ¤È ODMR ¤Ç¤ÏÆ°ºî¤·¤Þ¤»¤ó¡£
.TP
.B \-K, --nokeep
.\"O (Keyword: nokeep)
(¥­¡¼¥ï¡¼¥É: nokeep)
.\"O Delete retrieved messages from the remote mailserver.  This
.\"O option forces retrieved mail to be deleted.  It may be useful if
.\"O you have specified a default of \fBkeep\fR in your
.\"O \&\fI.fetchmailrc\fR.  This option is forced on with ETRN and ODMR.
¼èÆÀ¤·¤¿¥á¥Ã¥»¡¼¥¸¤ò¥ê¥â¡¼¥È¤Î¥á¡¼¥ë¥µ¡¼¥Ð¤«¤éºï½ü¤·¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È¡¢¼èÆÀ¤·¤¿¥á¡¼¥ë¤Ïºï½ü¤µ¤ì¤Þ¤¹¡£
\&\fI.fetchmailrc\fR Æâ ¤Ç \fBkeep\fR ¤ò¥Ç¥Õ¥©¥ë¥ÈÀßÄê¤Ë¤·¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬Ìò¤ËΩ¤Ä¤«¤â¤·¤ì¤Þ¤»¤ó¡£
ETRN ¤ä ODMR ¤ò»È¤¦¾ì¹ç¤Ë¤Ï¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤Ïɬ¤ºÍ­¸ú¤Ë¤µ¤ì¤Þ¤¹¡£
.TP
.B \-F, --flush
.\"O POP3/IMAP only.  Delete old (previously retrieved) messages from the mailserver
.\"O before retrieving new messages. This option does not work with ETRN or
.\"O ODMR.
POP3/IMAP ÀìÍѤΥª¥×¥·¥ç¥ó¤Ç¤¹¡£
¿·¤·¤¤¥á¥Ã¥»¡¼¥¸¤ò¼èÆÀ¤¹¤ëÁ°¤Ë¡¢¸Å¤¤ (°ÊÁ°¤Ë¼èÆÀ¤·¤¿)
¥á¥Ã¥»¡¼¥¸¤ò¥á¡¼¥ë¥µ¡¼¥Ð¤«¤éºï½ü¤·¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï ETRN ¤È ODMR ¤Ç¤ÏÆ°ºî¤·¤Þ¤»¤ó¡£
.\"O Warning: if your local MTA hangs and fetchmail is aborted, the next
.\"O time you run fetchmail, it will delete mail that was never delivered to you.
.\"O What you probably want is the default setting: if you don't specify `-k', then
.\"O fetchmail will automatically delete messages after successful delivery.
Ãí°Õ: ¥í¡¼¥«¥ë¤Î MTA ¤¬¥Ï¥ó¥°¤·¡¢fetchmail ¤¬°Û¾ï½ªÎ»¤·¤¿¾ì¹ç¡¢
¼¡²ó¤Ë fetchmail ¤òµ¯Æ°¤·¤¿¤È¤­¤ËÇÛÁ÷¤µ¤ì¤Æ¤¤¤Ê¤¤¥á¡¼¥ë¤¬¾Ã¤µ¤ì¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
¤¢¤Ê¤¿¤¬Îɤ¤¤È»×¤¦¤Î¤Ï¤¿¤Ö¤ó¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤Ç¤¹: `-k' ¤ò»ØÄꤷ¤Ê¤±¤ì¤Ð¡¢
fetchmail ¤ÏÇÛÁ÷¤¬À®¸ù¤·¤¿¸å¤Ë¼«Æ°Åª¤Ë¥á¥Ã¥»¡¼¥¸¤òºï½ü¤·¤Þ¤¹¡£
.\"O .SS Protocol and Query Options
.SS ¥×¥í¥È¥³¥ë¤ÈÌ䤤¹ç¤ï¤»¤Î¥ª¥×¥·¥ç¥ó
.TP
.B \-p, \--protocol <proto>
.\"O (Keyword: proto[col])
(¥­¡¼¥ï¡¼¥É: proto[col])
.\"O Specify the protocol to use when communicating with the remote 
.\"O mailserver.  If no protocol is specified, the default is AUTO.
.\"O .I proto 
.\"O may be one of the following:
¥ê¥â¡¼¥È¤Î¥á¡¼¥ë¥µ¡¼¥Ð¤ÈÄÌ¿®¤¹¤ë¤È¤­¤Ë»È¤¦¥×¥í¥È¥³¥ë¤ò»ØÄꤷ¤Þ¤¹¡£
¥×¥í¥È¥³¥ë¤¬»ØÄꤵ¤ì¤Ê¤±¤ì¤Ð¡¢¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï AUTO ¤Ç¤¹¡£
.I proto 
¤Ë¤Ï°Ê²¼¤Î¤É¤ì¤«¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:
.RS
.IP AUTO
.\"O Tries IMAP, POP3, and POP2 (skipping any of these for which support
.\"O has not been compiled in).
IMAP, POP3, POP2 ¤Ë»î¤·¤Þ¤¹
(¥µ¥Ý¡¼¥È¤¬ÁȤ߹þ¤Þ¤ì¤Æ¤¤¤Ê¤¤¥×¥í¥È¥³¥ë¤ÏÈô¤Ð¤·¤Þ¤¹)¡£
.IP POP2
.\"O Post Office Protocol 2
Post Office Protocol 2
.IP POP3
.\"O Post Office Protocol 3
Post Office Protocol 3
.IP APOP
.\"O Use POP3 with old-fashioned MD5-challenge authentication.
¸Å¤¤·Á¼°¤Î MD5 ¥Á¥ã¥ì¥ó¥¸Ç§¾ÚÉÕ¤­¤Î POP3 ¤ò»È¤¤¤Þ¤¹¡£
.IP RPOP
.\"O Use POP3 with RPOP authentication.
RPOP ǧ¾ÚÉÕ¤­¤Î POP3 ¤ò»È¤¤¤Þ¤¹¡£
.IP KPOP
.\"O Use POP3 with Kerberos V4 authentication on port 1109.
¥Ý¡¼¥È 1109 ÈÖ¤Ç Kerberos V4 ǧ¾ÚÉÕ¤­¤Î POP3 ¤ò»È¤¤¤Þ¤¹¡£
.IP SDPS
.\"O Use POP3 with Demon Internet's SDPS extensions.
Demon Internet ¤Î SDPS ³ÈÄ¥ÉÕ¤­¤Î POP3 ¤ò»È¤¤¤Þ¤¹¡£
.IP IMAP
.\"O IMAP2bis, IMAP4, or IMAP4rev1 (\fIfetchmail\fR autodetects their capabilities).
IMAP2bis, IMAP4, IMAP4rev1 ¤Î¤¤¤º¤ì¤«
(\fIfetchmail\fR ¤Ï¤³¤ì¤é¤Îµ¡Ç½¤ò¼«Æ°Åª¤Ë¸¡½Ð¤·¤Þ¤¹)¡£
.IP ETRN
.\"O Use the ESMTP ETRN option.
ESMTP ¤Î ETRN ¥ª¥×¥·¥ç¥ó¤ò»È¤¤¤Þ¤¹¡£
.IP ODMR
.\"O Use the the On-Demand Mail Relay ESMTP profile.
On-Demand Mail Relay ¤Î ESMTP ¥×¥í¥Õ¥¡¥¤¥ë¤ò»È¤¤¤Þ¤¹¡£
.RE
.P
.\"O All these alternatives work in basically the same way (communicating
.\"O with standard server daemons to fetch mail already delivered to a
.\"O mailbox on the server) except ETRN and ODMR.  The ETRN mode
.\"O allows you to ask a compliant ESMTP server (such as BSD sendmail at
.\"O release 8.8.0 or higher) to immediately open a sender-SMTP connection
.\"O to your client machine and begin forwarding any items addressed to
.\"O your client machine in the server's queue of undelivered mail.   The
.\"O ODMR mode requires an ODMR-capable server and works similarly to
.\"O ETRN, except that it does not require the client machine to have
.\"O a static DNS.
ETRN ¤È ODMR ¤ò½ü¤­¡¢¤³¤ì¤é¤ÎÁªÂò¥ª¥×¥·¥ç¥ó¤Ï´ðËÜŪ¤ËÁ´¤ÆƱ¤¸Æ°ºî¤Ç¤¹
(ɸ½à¤Î¥µ¡¼¥Ð¥Ç¡¼¥â¥ó¤ÈÄÌ¿®¤·¡¢
¥µ¡¼¥Ð¤Î¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤ËÇÛÁ÷¤µ¤ì¤Æ¤¤¤ë¥á¡¼¥ë¤ò¼èÆÀ¤·¤Þ¤¹)¡£
ETRN ¥â¡¼¥É¤ò»È¤¦¤È¡¢ESMTP ½àµò¤Î¥µ¡¼¥Ð
(BSD sendmail ¤Î¥ê¥ê¡¼¥¹ 8.8.0 °Ê¹ß¤Ê¤É) ¤Ë¡¢
¥¯¥é¥¢¥¤¥ó¥È¥Þ¥·¥ó¤Ø¤ÎÁ÷¿® SMTP Àܳ¤ò¨ºÂ¤Ë³«¤«¤»¡¢
¥µ¡¼¥Ð¤Î̤ÇÛã¥á¡¼¥ë¤Î¥­¥å¡¼¤ËÆþ¤Ã¤Æ¤¤¤ë¡¢
°¸À褬¥æ¡¼¥¶¤Î¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¤Ë¤Ê¤Ã¤Æ¤¤¤ë
Á´¤Æ¤Î¥á¡¼¥ë¤ÎžÁ÷¤ò³«»Ï¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
ODMR ¥â¡¼¥É¤Ç¤Ï ODMR ¤¬²Äǽ¤Ê¥µ¡¼¥Ð¤¬É¬Í×¤Ç ETRN ¤ÈƱÍͤËÆ°ºî¤·¤Þ¤¹¡£
¤¿¤À¤·¡¢ODMR ¥â¡¼¥É¤Ç¤Ï¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¤ËÀÅŪ DNS ¤¬É¬Íפ¢¤ê¤Þ¤»¤ó¡£
.TP
.B \-U, --uidl
.\"O (Keyword: uidl)
(¥­¡¼¥ï¡¼¥É: uidl)
.\"O Force UIDL use (effective only with POP3).  Force client-side tracking
.\"O of `newness' of messages (UIDL stands for ``unique ID listing'' and is
.\"O described in RFC1725).  Use with `keep' to use a mailbox as a baby
.\"O news drop for a group of users.
ɬ¤º UIDL ¤ò»È¤¦¤è¤¦¤Ë¤·¤Þ¤¹ (POP3 ¤Î¾ì¹ç¤Î¤ßÍ­¸ú¤Ç¤¹)¡£
¥á¥Ã¥»¡¼¥¸¤Î¡Ö¿·¤·¤µ¡×¤Î³Îǧ¤¬É¬¤º¥¯¥é¥¤¥¢¥ó¥È¦¤Ç¹Ô¤ï¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹
(UIDL ¤Ï¡Öunique ID listing (¥æ¥Ë¡¼¥¯¤Ê ID ¤ÎÎóµó)¡×¤òɽ¤·¤Þ¤¹)¡£
`keep' ¤È°ì½ï¤ËÍѤ¤¡¢¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤ò¡¢
¤¢¤ë¥æ¡¼¥¶¥°¥ë¡¼¥×ÍѤο·¤·¤¤¥Ë¥å¡¼¥¹¤òÆþ¤ì¤Æ¤ª¤¯¾ì½ê¤È¤·¤Æ»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
.TP
.\"O .B \-P, --port <portnumber>
.B \-P, --port <¥Ý¡¼¥ÈÈÖ¹æ>
.\"O (Keyword: port)
(¥­¡¼¥ï¡¼¥É: port)
.\"O The port option permits you to specify a TCP/IP port to connect on. 
.\"O This option will seldom be necessary as all the supported protocols have
.\"O well-established default port numbers.
port ¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢Àܳ¤¹¤ë TCP/IP ¤Î
¥Ý¡¼¥ÈÈÖ¹æ¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬É¬ÍפȤʤ뤳¤È¤Ï¤Û¤È¤ó¤É¤Ê¤¤¤Ç¤·¤ç¤¦¡£
¤È¤¤¤¦¤Î¤â¡¢¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ëÁ´¤Æ¥×¥í¥È¥³¥ë¤Ë¤Ï¤è¤¯ÃΤé¤ì¤Æ¤¤¤ë¥Ç¥Õ¥©¥ë¥È¤Î
¥Ý¡¼¥ÈÈֹ椬¤¢¤ë¤«¤é¤Ç¤¹¡£
.TP
.B \--principal <principal>
.\"O (Keyword: principal)
.\"O The principal option permits you to specify a service principal for
.\"O mutual authentication.  This is applicable to POP3 or IMAP with Kerberos
.\"O authentication.
(¥­¡¼¥ï¡¼¥É: principal)
principal ¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢
Áê¸ßǧ¾Ú¤Î¤¿¤á¤Î principal ¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
Kerberos ǧ¾ÚÉÕ¤­¤Î POP3 ¤È IMAP ¤Î¾ì¹ç¤Ë»ÈÍѤǤ­¤Þ¤¹¡£
.TP 
.\"O .B \-t, --timeout <seconds>
.B \-t, --timeout <Éÿô>
.\"O (Keyword: timeout)
(¥­¡¼¥ï¡¼¥É: timeout)
.\"O The timeout option allows you to set a server-nonresponse
.\"O timeout in seconds.  If a mailserver does not send a greeting message
.\"O or respond to commands for the given number of seconds,
.\"O \fIfetchmail\fR will hang up on it.  Without such a timeout
.\"O \fIfetchmail\fR might hang up indefinitely trying to fetch mail from a
.\"O down host.  This would be particularly annoying for a \fIfetchmail\fR
.\"O running in background.  There is a default timeout which fetchmail -V
.\"O will report.  If a given connection receives too many timeouts in 
.\"O succession, fetchmail will consider it wedged and stop retrying,
.\"O the calkling user will be notified by email if this happens.
timeout ¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢
¥µ¡¼¥Ð¤¬±þÅú¤·¤Ê¤¤ºÝ¤Î¥¿¥¤¥à¥¢¥¦¥È»þ´Ö¤òÉÃñ°Ì¤ÇÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
»ØÄꤵ¤ì¤¿Éÿô¤Î´Ö¥á¡¼¥ë¥µ¡¼¥Ð¤¬¥°¥ê¡¼¥Æ¥£¥ó¥°¥á¥Ã¥»¡¼¥¸¤òÁ÷¤Ã¤Æ¤³¤Ê¤¤¤«
¥³¥Þ¥ó¥É¤Ë±þÅú¤·¤Ê¤¤¾ì¹ç¡¢
\fIfetchmail\fR ¤Ï¥µ¡¼¥Ð¤È¤ÎÀܳ¤òÀÚ¤ê¤Þ¤¹¡£
¤³¤Î¤è¤¦¤Ê¥¿¥¤¥à¥¢¥¦¥È¤ò»È¤ï¤Ê¤±¤ì¤Ð¡¢
\fIfetchmail\fR ¤ÏÍî¤Á¤Æ¤¤¤ë¥Û¥¹¥È¤«¤é
¤¤¤Ä¤Þ¤Ç¤â¥á¡¼¥ë¤ò¼èÆÀ¤·¤è¤¦¤È¤·¤Æ¥Ï¥ó¥°¥¢¥Ã¥×¤·¤Æ¤·¤Þ¤¦¤«¤â¤·¤ì¤Þ¤»¤ó¡£
¤³¤ì¤Ï \fIfetchmail\fR ¤¬¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤ÇÆ°ºî¤·¤Æ¤¤¤ë»þ¤Ë¤Ï
Æäˤ¦¤Ã¤È¤¦¤·¤¤¤Ç¤·¤ç¤¦¡£
¥Ç¥Õ¥©¥ë¥È¤Î¥¿¥¤¥à¥¢¥¦¥È»þ´Ö¤¬¤¢¤ê¡¢fetchmail -V ¤Çɽ¼¨¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
Í¿¤¨¤é¤ì¤¿Àܳ¤Ç²¿ÅÙ¤âϢ³¤·¤Æ¥¿¥¤¥à¥¢¥¦¥È¤ò¼õ¤±¤¿¾ì¹ç¡¢
fetchmail ¤ÏÀܳ¤¬»ß¤á¤é¤ì¤Æ¤¤¤ë¤â¤Î¤È¹Í¤¨¡¢¥ê¥È¥é¥¤¤ò»ß¤á¤Þ¤¹¡£
¤³¤ì¤¬µ¯¤³¤Ã¤¿¾ì¹ç¡¢Àܳ¤ò»ß¤á¤é¤ì¤¿¥æ¡¼¥¶¤Ï¥á¡¼¥ë¤ÇÄÌÃΤò¼õ¤±¤Þ¤¹¡£
.TP
.\"O .B \--plugin <command>
.B \--plugin <¥³¥Þ¥ó¥É>
.\"O (Keyword: plugin) The plugin option allows you to use an external
.\"O program to establish the TCP connection.  This is useful if you want
.\"O to use socks, SSL, ssh, or need some special firewalling setup.  The
.\"O program will be looked up in $PATH and can optionally be passed the
.\"O hostname and port as arguments using "%h" and "%p" respectively (note
.\"O that the interpolation logic is rather primitive, and these token must
.\"O be bounded by whitespace or beginning of string or end of string).
.\"O Fetchmail will write to the plugin's stdin and read from the plugin's
.\"O stdout.
(¥­¡¼¥ï¡¼¥É: plugin)
plugin ¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢TCP Àܳ¤ò³ÎΩ¤¹¤ë¤¿¤á¤Î
³°Éô¥×¥í¥°¥é¥à¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤ì¤Ï SOCKS, SSL, ssh ¤ò»È¤¦¾ì¹ç¤ä
¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ëÍѤÎÆüì¤ÊÀßÄ꤬ɬÍפʤȤ­¤ËÊØÍø¤Ç¤¹¡£
¥×¥í¥°¥é¥à¤Ï $PATH ´Ä¶­ÊÑ¿ôÆâ¤Ç¸¡º÷¤µ¤ì¤Þ¤¹¡£
¥ª¥×¥·¥ç¥ó¤È¤·¤Æ¡¢"%h" ¤È "%p" ¤ò»È¤Ã¤Æ¡¢
¤½¤ì¤¾¤ì¥Û¥¹¥È̾¤È¥Ý¡¼¥È̾¤ò°ú¤­¿ô¤È¤·¤ÆÅϤ¹¤³¤È¤â¤Ç¤­¤Þ¤¹
(Êä´Ö¥í¥¸¥Ã¥¯¤Ï¾¯¤·¸¶»ÏŪ¤Ç¡¢¼õ¤±¼è¤é¤ì¤ë°ú¤­¿ô¤Ï¶õÇò¤Ç°Ï¤Þ¤ì¤Æ¤¤¤ë¤«¡¢
ʸ»úÎó¤ÎÀèƬ¤Þ¤¿¤ÏËöÈø¤Ë¤Ê¤±¤ì¤Ð¤¤¤±¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ²¼¤µ¤¤)¡£
fetchmail ¤Ï¥×¥é¥°¥¤¥ó¤Îɸ½àÆþÎϤ˽ñ¤­¹þ¤ß¤ò¹Ô¤¤¡¢
¥×¥é¥°¥¤¥ó¤Îɸ½à½ÐÎϤ«¤éÆɤ߹þ¤ß¤ò¹Ô¤¤¤Þ¤¹¡£
.TP
.\"O .B \--plugout <command>
.B \--plugout <¥³¥Þ¥ó¥É>
.\"O (Keyword: plugout)
(¥­¡¼¥ï¡¼¥É: plugout)
.\"O Identical to the plugin option above, but this one is used for the SMTP
.\"O connections (which will probably not need it, so it has been separated
.\"O from plugin).
Á°¤Î¹à¤Î plugin ¥ª¥×¥·¥ç¥ó¤ÈƱ¤¸¤Ç¤¹¤¬¡¢
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï SMTP Àܳ¤ËÂФ·¤Æ¤Î¤ß»È¤ï¤ì¤Þ¤¹
(SMTP Àܳ¤Ç¤Ï¤¿¤Ö¤ó¥×¥é¥°¥¤¥ó¤ÏÉÔÍפʤΤǡ¢
plugin ¥ª¥×¥·¥ç¥ó¤«¤éʬΥ¤µ¤ì¤Æ¤¤¤Þ¤¹)¡£
.TP
.\"O .B \-r <name>, --folder <name>
.B \-r <¥Õ¥©¥ë¥À̾>, --folder <¥Õ¥©¥ë¥À̾>
.\"O (Keyword: folder[s])
(¥­¡¼¥ï¡¼¥É: folder[s])
.\"O Causes a specified non-default mail folder on the mailserver (or
.\"O comma-separated list of folders) to be retrieved.  The syntax of the
.\"O folder name is server-dependent.  This option is not available under
.\"O POP3, ETRN, or ODMR.
¥á¡¼¥ë¥µ¡¼¥Ð¾å¤Ç¡¢¥Ç¥Õ¥©¥ë¥È°Ê³°¤Î»ØÄꤵ¤ì¤¿¥á¡¼¥ë¥Õ¥©¥ë¥À
(¤Þ¤¿¤Ï¥³¥ó¥Þ¤Ç¶èÀڤä¿¥Õ¥©¥ë¥À¤Î¥ê¥¹¥È) ¤«¤é¥á¡¼¥ë¤ò¼èÆÀ¤·¤Þ¤¹¡£
¥Õ¥©¥ë¥À̾¤Îµ­Ë¡¤Ï¥µ¡¼¥Ð¤Ë°Í¸¤·¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï POP3, ETRN, ODMR ¤Ç¤Ï»È¤¨¤Þ¤»¤ó¡£
.TP
.B \--tracepolls
.\"O (Keyword: tracepolls)
(¥­¡¼¥ï¡¼¥É: tracepolls)
.\"O Tell fetchail to poll trace information in the form `polling %s
.\"O account %s' to the Received line it generates, where the %s parts are
.\"O replaced by the user's remote name and the poll label (the Received
.\"O header also normally includes the server's truename).  This can be
.\"O used to facilate mail filtering based on the account it is being
.\"O received from.
fetchmail ¤¬À¸À®¤¹¤ë Received ¹Ô¤Ë¡¢
`polling %s account %s' ¤È¤¤¤¦·Á¼°¤Ç¥È¥ì¡¼¥¹¾ðÊó¤òÆþ¤ì¤ë¤è¤¦¤Ë¤µ¤»¤Þ¤¹¡£
%s ¤ÎÉôʬ¤Ï¥æ¡¼¥¶¤Î¥ê¥â¡¼¥È̾¤È¥Ý¡¼¥ê¥ó¥°¥ì¥Ù¥ë¤ËÃÖ¤­´¹¤¨¤é¤ì¤Þ¤¹
(Ä̾Received ¥Ø¥Ã¥À¤Ë¤Ï¥µ¡¼¥Ð¤ÎËÜÅö¤Î̾Á°¤â´Þ¤Þ¤ì¤Þ¤¹)¡£
¤³¤ì¤Ï¡¢¼õ¿®¤·¤¿¥¢¥«¥¦¥ó¥È¤Ë´ð¤Å¤¤¤¿¥á¡¼¥ë¥Õ¥£¥ë¥¿¥ê¥ó¥°¤ò
Íưפˤ¹¤ë¤¿¤á¤Ë»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.TP
.B \--ssl
.\"O (Keyword: ssl)
(¥­¡¼¥ï¡¼¥É: ssl)
.\"O Causes the connection to the mail server to be encrypted via SSL.  Connect
.\"O to the server using the specified base protocol over a connection secured
.\"O by SSL.  SSL support must be present at the server.  If no port is
.\"O specified, the connection is attempted to the well known port of the SSL
.\"O version of the base protocol.  This is generally a different port than the
.\"O port used by the base protocol.  For IMAP, this is port 143 for the clear
.\"O protocol and port 993 for the SSL secured protocol.
¥á¡¼¥ë¥µ¡¼¥Ð¤Ø¤ÎÀܳ¤ò SSL ¤ò»È¤Ã¤Æ°Å¹æ²½¤·¤Þ¤¹¡£¥µ¡¼¥Ð¤Ø¤ÎÀܳ¤Ï¡¢SSL 
¤Ë¤è¤Ã¤Æ¼é¤é¤ì¤¿Àܳ¾å¤Ç»ØÄꤷ¤¿´ðËÜ¥×¥í¥È¥³¥ë¤ò»È¤Ã¤Æ¹Ô¤ï¤ì¤Þ¤¹¡£
¥Ý¡¼¥È¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ï¡¢
Àܳ¤Ï´ðËÜ¥×¥í¥È¥³¥ë¤Î SSL ÈǤδûÃΤΥݡ¼¥È¤Ç»î¤ß¤é¤ì¤Þ¤¹¡£
¤³¤ì¤Ï°ìÈÌŪ¤Ë¤Ï¡¢´ðËÜ¥×¥í¥È¥³¥ë¤Ç»È¤ï¤ì¤ë¥Ý¡¼¥È¤È¤Ï°Û¤Ê¤ê¤Þ¤¹¡£
IMAP ¤Î¾ì¹ç¡¢´ðËÜ¥×¥í¥È¥³¥ë¤Ï¥Ý¡¼¥È 143 ¤Ç¤¢¤ê¡¢
SSL ¤Ç¼é¤é¤ì¤¿¥×¥í¥È¥³¥ë¤Î¾ì¹ç¤Ï¥Ý¡¼¥È 993 ¤Ç¤¹¡£
.TP
.\"O .B \--sslcert <name>
.B \--sslcert <̾Á°>
.\"O (Keyword: sslcert)
(¥­¡¼¥ï¡¼¥É: sslcert)
.\"O Specifies the file name of the client side public SSL certificate.  Some
.\"O SSL encrypted servers may require client side keys and certificates for
.\"O authentication.  In most cases, this is optional.  This specifies
.\"O the location of the public key certificate to be presented to the server
.\"O at the time the SSL session is established.  It is not required (but may
.\"O be provided) if the server does not require it.  Some servers may
.\"O require it, some servers may request it but not require it, and some
.\"O servers may not request it at all.  It may be the same file
.\"O as the private key (combined key and certificate file) but this is not
.\"O recommended.
¥¯¥é¥¤¥¢¥ó¥È¦¤Î¸ø³« SSL ¾ÚÌÀ½ñ¤Î¥Õ¥¡¥¤¥ë̾¤ò»ØÄꤷ¤Þ¤¹¡£SSL ¤Ë¤è¤ë
°Å¹æ²½¤ò¹Ô¤¦¥µ¡¼¥Ð¤Î°ìÉô¤Ë¤Ï¡¢Ç§¾Ú¤Î¤¿¤á¤Ë¥¯¥é¥¤¥¢¥ó¥È¦¤Î¸°¤È¾ÚÌÀ½ñ¤ò
ɬÍפȤ¹¤ë¤â¤Î¤â¤¢¤ê¤Þ¤¹¡£¤Û¤È¤ó¤É¤Î¾ì¹ç¤Ï¤³¤ì¤Ï¾Êά¤·¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï SSL ¥»¥Ã¥·¥ç¥ó¤ò³ÎΩ¤¹¤ë»þ¤Ë¥µ¡¼¥Ð¤Ë¼¨¤¹¸ø³«¸°¾ÚÌÀ½ñ
¤Î°ÌÃÖ¤ò»ØÄꤷ¤Þ¤¹¡£¥µ¡¼¥Ð¤¬É¬ÍפȤ·¤Ê¤±¤ì¤Ð¡¢¤³¤ì¤ò»ØÄꤹ¤ëɬÍפϤ¢¤ê
¤Þ¤»¤ó (»ØÄꤷ¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó)¡£¤³¤ì¤òɬÍפȤ¹¤ë¥µ¡¼¥Ð¤â¤¢¤ê¤Þ¤¹¤·¡¢
Í׵᤹¤ë¤±¤ì¤ÉɬÍפȤϤ·¤Ê¤¤¥µ¡¼¥Ð¤â¤¢¤ê¤Þ¤¹¤·¡¢Á´¤¯Í׵ᤷ¤Ê¤¤¥µ¡¼¥Ð¤â
¤¢¤ê¤Þ¤¹¡£¤³¤ì¤ÏÈëÌ©¸° (¸°¤È¾ÚÌÀ½ñ¤ò°ì½ï¤Ë¤·¤¿¥Õ¥¡¥¤¥ë) ¤ÈƱ¤¸¥Õ¥¡¥¤¥ë¤Î
¤³¤È¤â¤¢¤ê¤Þ¤¹¤¬¡¢¤³¤ì¤Ï¤ª´«¤á¤Ç¤­¤Þ¤»¤ó¡£
.TP
.\"O .B \--sslkey <name>
.B \--sslkey <¥Õ¥¡¥¤¥ë̾>
.\"O (Keyword: sslkey)
(¥­¡¼¥ï¡¼¥É: sslkey)
.\"O Specifies the file name of the client side private SSL key.  Some SSL
.\"O encrypted servers may require client side keys and certificates for
.\"O authentication.  In most cases, this is optional.  This specifies
.\"O the location of the private key used to sign transactions with the server
.\"O at the time the SSL session is established.  It is not required (but may
.\"O be provided) if the server does not require it.  Some servers may
.\"O require it, some servers may request it but not require it, and some
.\"O servers may not request it at all.  It may be the same file
.\"O as the public key (combined key and certificate file) but this is not
.\"O recommended.  If a password is required to unlock the key, it will be
.\"O prompted for at the time just prior to establishing the session to the
.\"O server.  This can cause some complications in daemon mode.
¥¯¥é¥¤¥¢¥ó¥È¦¤ÎÈëÌ© SSL ¸°¤Î¥Õ¥¡¥¤¥ë̾¤ò»ØÄꤷ¤Þ¤¹¡£SSL ¤Ë¤è¤ë
°Å¹æ²½¤ò¹Ô¤¦¥µ¡¼¥Ð¤Î°ìÉô¤Ë¤Ï¡¢Ç§¾Ú¤Î¤¿¤á¤Ë¥¯¥é¥¤¥¢¥ó¥È¦¤Î¸°¤È¾ÚÌÀ½ñ¤ò
ɬÍפȤ¹¤ë¤â¤Î¤â¤¢¤ê¤Þ¤¹¡£¤Û¤È¤ó¤É¤Î¾ì¹ç¤Ï¤³¤ì¤Ï¾Êά¤·¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï SSL ¥»¥Ã¥·¥ç¥ó¤ò³ÎΩ¤¹¤ë»þ¤Ë¥µ¡¼¥Ð¤È¤Î½ð̾¥È¥é¥ó¥¶¥¯¥·¥ç¥ó
¤ÇÍѤ¤¤ëÈëÌ©¸°¤Î°ÌÃÖ¤ò»ØÄꤷ¤Þ¤¹¡£¥µ¡¼¥Ð¤¬É¬ÍפȤ·¤Ê¤±¤ì¤Ð¡¢¤³¤ì¤ò»ØÄê
¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó (»ØÄꤷ¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó)¡£¤³¤ì¤òɬÍפȤ¹¤ë¥µ¡¼¥Ð¤â
¤¢¤ê¤Þ¤¹¤·¡¢Í׵᤹¤ë¤±¤ì¤ÉɬÍפȤϤ·¤Ê¤¤¥µ¡¼¥Ð¤â¤¢¤ê¤Þ¤¹¤·¡¢Á´¤¯Í׵ᤷ
¤Ê¤¤¥µ¡¼¥Ð¤â¤¢¤ê¤Þ¤¹¡£¤³¤ì¤Ï¸ø³«¸° (¸°¤È¾ÚÌÀ½ñ¤ò°ì½ï¤Ë¤·¤¿¥Õ¥¡¥¤¥ë) ¤ÈƱ
¤¸¥Õ¥¡¥¤¥ë¤Î¤³¤È¤â¤¢¤ê¤Þ¤¹¤¬¡¢¤³¤ì¤Ï¤ª´«¤á¤Ç¤­¤Þ¤»¤ó¡£¸°¤ò³°¤¹¤¿¤á¤Ë
¥Ñ¥¹¥ï¡¼¥É¤¬É¬Íפʾì¹ç¤Ë¤Ï¡¢¥µ¡¼¥Ð¤È¤Î¥»¥Ã¥·¥ç¥ó¤ò³ÎΩ¤¹¤ëľÁ°¤Ë
¥Ñ¥¹¥ï¡¼¥É¤òʹ¤«¤ì¤Þ¤¹¡£¤½¤Î¤¿¤á¡¢¥Ç¡¼¥â¥ó¥â¡¼¥É¤Ç»È¤¦¤Î¤Ïº¤Æñ¤Ç¤¹¡£
.TP
.\"O .B \--sslproto <name>
.\"O (Keyword: sslproto)
.\"O Forces an ssl protocol. Possible values are \&`\fBssl2\fR', `\fBssl3\fR' and
.\"O `\fBtls1\fR'. Try this if the default handshake does not work for your server.
.B \--sslproto <̾Á°>
(¥­¡¼¥ï¡¼¥É: sslproto)
ssl ¥×¥í¥È¥³¥ë¤ò¶¯À©Åª¤Ë»ÈÍѤ·¤Þ¤¹¡£
»ØÄê²Äǽ¤ÊÃÍ¤Ï \&`\fBssl2\fR', `\fBssl3\fR', `\fBtls1\fR' ¤Ç¤¹¡£
¥µ¡¼¥Ð¤È¤Î¥Ç¥Õ¥©¥ë¥È¤ÎÀܳ¤¬¤¦¤Þ¤¯¹Ô¤«¤Ê¤«¤Ã¤¿¾ì¹ç¤Ë»î¤·¤Æ²¼¤µ¤¤¡£
.TP
.B \--sslcertck
.\"O (Keyword: sslcertck)
.\"O Causes fetchmail to strictly check the server certificate against a set of
.\"O local trusted certificates (see the \fBsslcertpath\fR option). If the server
.\"O certificate is not signed by one of the trusted ones (directly or indirectly),
.\"O the SSL connection will fail. This checking should prevent man-in-the-middle
.\"O attacks against the SSL connection. Note that CRLs are seemingly not currently
.\"O supported by OpenSSL in certificate verification! Your system clock should
.\"O be reasonably accurate when using this option!
(¥­¡¼¥ï¡¼¥É: sslcertck)
fetchmail ¤¬¥í¡¼¥«¥ë¤Î¿®ÍѤǤ­¤ë¾ÚÌÀ½ñ¤ËÂФ·¤Æ¥µ¡¼¥Ð¾ÚÌÀ½ñ¤ò
¸·Ì©¤Ë¥Á¥§¥Ã¥¯¤¹¤ë¤è¤¦¤Ë¤·¤Þ¤¹
(\fBsslcertpath\fR ¥ª¥×¥·¥ç¥ó¤ò¸«¤Æ¤¯¤À¤µ¤¤)¡£
¥µ¡¼¥Ð¾ÚÌÀ½ñ¤¬¿®Íê¤Ç¤­¤ë½ð̾¤Ç (ľÀÜŪ¤Þ¤¿¤Ï´ÖÀÜŪ¤Ë)
¥µ¥¤¥ó¤µ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢SSL Àܳ¤Ï¼ºÇÔ¤·¤Þ¤¹¡£
¤³¤Î¥Á¥§¥Ã¥¯¤Ë¤è¤ê¡¢SSL Àܳ¤ËÂФ·¤Æ
·ÐÏ©¤ÎÅÓÃæ¤Ë¤¤¤ë¿Í´Ö¤¬¹Ô¤¦¹¶·â¤òÁ˻ߤǤ­¤Þ¤¹¡£
OpenSSL ¤Ë¤è¤ë¾ÚÌÀ½ñ³Îǧ¤Ç¤Ï¡¢
CRL ¤Ï¸½ºß¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Ê¤¤¤«¤â¤·¤ì¤Ê¤¤ÅÀ¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢¥·¥¹¥Æ¥à¥¯¥í¥Ã¥¯¤¬¤¤¤¯¤é¤«¿Ê¤ß¤Þ¤¹¡£
.TP
.\"O .B \--sslcertpath <directory>
.\"O (Keyword: sslcertpath)
.\"O Sets the directory fetchmail uses to look up local certificates. The default
.\"O is your OpenSSL default one. The directory must be hashed as OpenSSL expects
.\"O it - every time you add or modify a certificate in the directory, you need
.\"O to use the \fBc_rehash\fR tool (which comes with OpenSSL in the tools/
.\"O subdirectory).
.B \--sslcertpath <¥Ç¥£¥ì¥¯¥È¥ê̾>
(¥­¡¼¥ï¡¼¥É: sslcertpath)
fetchmail ¤¬¥í¡¼¥«¥ë¤Î¾ÚÌÀ½ñ¤òõ¤¹¥Ç¥£¥ì¥¯¥È¥ê¤òÀßÄꤷ¤Þ¤¹¡£
¥Ç¥Õ¥©¥ë¥È¤Ï OpenSSL ¤Î¥Ç¥Õ¥©¥ë¥È¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤¹¡£
¥Ç¥£¥ì¥¯¥È¥ê¤Ï OpenSSL ¤¬´üÂÔ¤¹¤ë¤è¤¦¤Ë¥Ï¥Ã¥·¥å¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
¥Ç¥£¥ì¥¯¥È¥êÆâ¤Î¾ÚÌÀ½ñ¤òÄɲᦽ¤Àµ¤·¤¿¾ì¹ç¤Ï¡¢
(OpenSSL ¤Î tools/ ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ËÆþ¤Ã¤Æ¤¤¤ë)
\fBc_rehash\fR ¥Ä¡¼¥ë¤ò»È¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
.TP
.B \--sslfingerprint
.\"O (Keyword: sslfingerprint)
.\"O Specify the fingerprint of the server key (an MD5 hash of the key) in
.\"O hexadecimal notation with colons separating groups of two digits. The letter
.\"O hex digits must be in upper case. This is the default format OpenSSL uses,
.\"O and the one fetchmail uses to report the fingerprint when an SSL connection
.\"O is established. When this is specified, fetchmail will compare the server key
.\"O fingerprint with the given one, and the connection will fail if they do not
.\"O match. This can be used to prevent man-in-the-middle attacks.
(¥­¡¼¥ï¡¼¥É: sslfingerprint)
¥³¥í¥ó¤Ç¶èÀÚ¤é¤ì¤¿ 16 ¿Ê¿ôɽµ­¤Î 2 ÁȤοô»ú¤Ç½ñ¤«¤ì¤¿
¥µ¡¼¥Ð¡¦¥­¡¼¤Î½ð̾ (¥­¡¼¤Î MD5 ¥Ï¥Ã¥·¥å) ¤ò»ØÄꤷ¤Þ¤¹¡£
16 ¿Ê¿ô¤Î¿ô»ú¤ÏÂçʸ»ú¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
¤³¤ì¤Ï OpenSSL ¤¬»È¤¦¥Ç¥Õ¥©¥ë¥È¤Î·Á¼°¤Ç¡¢
SSL Àܳ¤¬³ÎΩ¤µ¤ì¤ë¤È fetchmail ¤Ï¤³¤Î·Á¼°¤Ç½ð̾¤òɽ¼¨¤·¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬»ØÄꤵ¤ì¤ë¤È¡¢
¥µ¡¼¥Ð¡¦¥­¡¼¤Î½ð̾¤òÍ¿¤¨¤é¤ì¤¿½ð̾¤ÈÈæ³Ó¤·¤Þ¤¹¡£
°ìÃפ·¤Ê¤«¤Ã¤¿¾ì¹ç¡¢Àܳ¤Ï¼ºÇÔ¤·¤Þ¤¹¡£
¤³¤ì¤Ï·ÐÏ©¤ÎÅÓÃæ¤Ë¤¤¤ë¿Í´Ö¤¬¹Ô¤¦¹¶·â¤òÁ˻ߤǤ­¤Þ¤¹¡£
.\"O .SS Delivery Control Options
.SS ÇÛÁ÷À©¸æ¥ª¥×¥·¥ç¥ó
.TP
.\"O .B \-S <hosts>, --smtphost <hosts>
.B \-S <hosts>, --smtphost <¥Û¥¹¥È>
.\"O (Keyword: smtp[host])
(¥­¡¼¥ï¡¼¥É: smtp[host])
.\"O Specify a hunt list of hosts to forward mail to (one or more
.\"O hostnames, comma-separated). Hosts are tried in list order; the first
.\"O one that is up becomes the forwarding target for the current run.
.\"O Normally, `localhost' is added to the end of the list as an invisible
.\"O default.  However, when using Kerberos authentication, the FQDN of the
.\"O machine running fetchmail is added to the end of the list as an
.\"O invisible default. Each hostname may have a port number following the
.\"O host name.  The port number is separated from the host name by a
.\"O slash; the default port is 25 (or ``smtp'' under IPv6).  If you
.\"O specify an absolute pathname (beginning with a /), it will be
.\"O interpreted as the name of a UNIX socket accepting LMTP connections
.\"O (such as is supported by the Cyrus IMAP daemon) Example:
¥á¡¼¥ë¤òžÁ÷¤¹¤ë¥Û¥¹¥È¤Î¥ê¥¹¥È (1 ¤Ä°Ê¾å¤Î¥Û¥¹¥È̾¤Ç¡¢¥³¥ó¥Þ¤Ç¶èÀÚ¤ê¤Þ¤¹)
¤ò»ØÄꤷ¤Þ¤¹¡£
¥Û¥¹¥È¤Ï¥ê¥¹¥È¤Î½ç¤ËÀܳ¤¬»î¤ß¤é¤ì¤Þ¤¹¡£
ºÇ½é¤ÎÆ°ºî¤·¤Æ¤¤¤ë¥Û¥¹¥È¤¬¡¢
º£²ó¤ÎÆ°ºî¤Ë¤ª¤±¤ëžÁ÷ÀèÂоݤȤʤê¤Þ¤¹¡£
Ä̾ï¤Ï `localhost' ¤¬¥ê¥¹¥È¤ÎËöÈø¤Ë°ÅÌۤΥǥե©¥ë¥ÈÃͤȤ·¤ÆÄɲ䵤ì¤Æ¤¤¤Þ¤¹¡£
¤·¤«¤·¡¢Kerberos ǧ¾Ú¤ò»È¤¦¾ì¹ç¤Ë¤Ï¡¢
fetchmail ¤ò¼Â¹Ô¤·¤Æ¤¤¤ë¥Þ¥·¥ó¤Î FQDN ¤¬¥ê¥¹¥È¤ÎËöÈø¤Ë
°ÅÌۤΥǥե©¥ë¥ÈÃͤȤ·¤ÆÄɲ䵤ì¤Þ¤¹¡£
¤½¤ì¤¾¤ì¤Î¥Û¥¹¥È̾¤Ë¤Ï¡¢¥Û¥¹¥È¤Î̾Á°¤Î¼¡¤Ë¥Ý¡¼¥ÈÈֹ椬ÉÕ¤¤¤Æ¤¤¤Þ¤¹¡£
¥Ý¡¼¥ÈÈÖ¹æ¤È¥Û¥¹¥È̾¤Ï¥¹¥é¥Ã¥·¥å¤Ç¶èÀÚ¤é¤ì¤Þ¤¹¡£
¥Ç¥Õ¥©¥ë¥È¤Î¥Ý¡¼¥ÈÈÖ¹æ¤Ï 25 (IPv6 ¤Ç¤Ï ``smtp'') ¤Ç¤¹¡£
(/ ¤Ç»Ï¤Þ¤ë) ÀäÂХѥ¹Ì¾¤ò»ØÄꤷ¤¿¾ì¹ç¡¢
LMTP Àܳ¤ò¼õ¤±ÉÕ¤±¤ë UNIX ¥½¥±¥Ã¥È¤Î̾Á°¤È¤·¤Æ²ò¼á¤µ¤ì¤Þ¤¹
(¤³¤ì¤Ï Cyrus IMAP ¥Ç¡¼¥â¥ó¤Ç¥µ¥Ý¡¼¥È¤µ¤ì¤Þ¤¹)¡£
Îã:

        --smtphost server1,server2/2525,server3,/var/imap/socket/lmtp

.\"O This option can be used with ODMR, and will make fetchmail a relay
.\"O between the ODMR server and SMTP or LMTP receiver.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï ODMR ¥â¡¼¥É¤Ç»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¡¢
fetchmail ¤Ë ODMR ¥µ¡¼¥Ð¤È SMTP, LMTP ¥ì¥·¡¼¥Ð¤Î´Ö¤Î
¥ê¥ì¡¼¤ò¤µ¤»¤Þ¤¹¡£
.TP 
.\"O .B --fetchdomains <hosts>
.B --fetchdomains <¥Û¥¹¥È>
.\"O (Keyword: fetchdomains)
(¥­¡¼¥ï¡¼¥É: fetchdomains)
.\"O In ETRN or ODMR mode, this option specifies the list of domains the
.\"O server should ship mail for once the connection is turned around.  The
.\"O default is the FQDN of the machine running fetchmail.
ETRN ¤È ODMR ¥â¡¼¥É¤Ë¤ª¤¤¤Æ¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï
Àܳ¤¬¹Ô¤ï¤ì¤¿¾ì¹ç¤Ë¥µ¡¼¥Ð¤¬¥á¡¼¥ë¤òÇÛÁ÷¤¹¤ë¥É¥á¥¤¥ó¤Î°ìÍ÷¤ò»ØÄꤷ¤Þ¤¹¡£
¥Ç¥Õ¥©¥ë¥È¤Ï fetchmail ¤¬²ÔƯ¤·¤Æ¤¤¤ë¥Þ¥·¥ó¤Î FQDN ¤Ç¤¹¡£
.TP
.\"O .B \-D <domain>, --smtpaddress <domain>
.B \-D <¥É¥á¥¤¥ó>, --smtpaddress <¥É¥á¥¤¥ó>
.\"O (Keyword: smtpaddress) Specify the domain to be appended to addresses
.\"O in RCPT TO lines shipped to SMTP. The name of the SMTP server (as
.\"O specified by --smtphost, or defaulted to "localhost") is used when
.\"O this is not specified.
(¥­¡¼¥ï¡¼¥É: smtpaddress) 
¥¢¥É¥ì¥¹¤ËÄɲ䵤ì¤ë¥É¥á¥¤¥ó¤ò»ØÄꤷ¤Þ¤¹¡£
¤³¤Î¥¢¥É¥ì¥¹¤Ï SMTP ¤ÇÁ÷¤é¤ì¤ë RCPT TO ¹Ô¤ËÆþ¤ê¤Þ¤¹¡£
¤³¤ì¤¬»ØÄꤵ¤ì¤Ê¤«¤Ã¤¿¤È¤­¤Ï¡¢SMTP ¥µ¡¼¥Ð¤Î̾Á°
(--smtphost ¤Ç»ØÄꤹ¤ë¤«¡¢¥Ç¥Õ¥©¥ë¥È¤Î "localhost") ¤¬»È¤ï¤ì¤Þ¤¹¡£
.TP
.\"O .B --smtpname <user@domain>
.B --smtpname <¥æ¡¼¥¶@¥É¥á¥¤¥ó>
.\"O (Keyword: smtpname) 
.\"O Specify the domain and user to be put in RCPT TO lines shipped to SMTP.
.\"O The default user is the current local user.
(¥­¡¼¥ï¡¼¥É: smtpname) 
SMTP ¤ÇÁ÷¤é¤ì¤ë RCPT TO ¹Ô¤ËÆþ¤ì¤é¤ì¤ë¥É¥á¥¤¥ó¤È¥æ¡¼¥¶¤ò»ØÄꤷ¤Þ¤¹¡£
¥Ç¥Õ¥©¥ë¥È¤Î¥æ¡¼¥¶¤Ï¸½ºß¤Î¥æ¡¼¥¶¤Ç¤¹¡£
.TP
.B \-Z <nnn>, --antispam <nnn[, nnn]...>
.\"O (Keyword: antispam) 
(¥­¡¼¥ï¡¼¥É: antispam) 
.\"O Specifies the list of numeric SMTP errors that are to be interpreted
.\"O as a spam-block response from the listener.  A value of -1 disables
.\"O this option.  For the command-line option, the list values should
.\"O be comma-separated.
SMTP ¼õ¿®¥×¥í¥°¥é¥à¤«¤é¤Î¥¹¥Ñ¥àËɻߤαþÅú¤È²ò¼á¤µ¤ì¤ë¡¢
¿ôÃÍ·Á¼°¤Î SMTP¥¨¥é¡¼¤Î¥ê¥¹¥È¤ò»ØÄꤷ¤Þ¤¹¡£
Ãͤ¬ -1 ¤Ç¤¢¤ì¤Ð¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï̵¸ú¤Ë¤µ¤ì¤Þ¤¹¡£
¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤Î¾ì¹ç¡¢
¥ê¥¹¥È¤ÎÃͤϥ³¥ó¥Þ¤Ç¶èÀÚ¤é¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.TP
.\"O .B \-m <command>, \--mda <command>
.B \-m <¥³¥Þ¥ó¥É>, \--mda <¥³¥Þ¥ó¥É>
.\"O (Keyword: mda)
(¥­¡¼¥ï¡¼¥É: mda)
.\"O You can force mail to be passed to an MDA directly (rather than
.\"O forwarded to port 25) with the -mda or -m option.  
-mda ¤¢¤ë¤¤¤Ï -m ¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¡¢(25 È֥ݡ¼¥È¤ËžÁ÷¤¹¤ë¤Î¤Ç¤Ï¤Ê¤¯)
¥á¡¼¥ë¤òľÀÜ MDA ¤ËÅϤ¹¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£
.\"O To avoid losing
.\"O mail, use this option only with MDAs like procmail or sendmail that
.\"O return a nonzero status on disk-full and other resource-exhaustion
.\"O errors; 
¥á¡¼¥ë¤ò¼º¤¦¤Î¤òÈò¤±¤ë¤¿¤á¤Ë¡¢
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢
¥Ç¥£¥¹¥¯¤¬°î¤ì¤Æ¤¤¤ë¾ì¹ç¤ä¥ê¥½¡¼¥¹¾ÃÈñ¥¨¥é¡¼¤Ê¤É¤Î¾ì¹ç¤Ë
0 °Ê³°¤Î¥¹¥Æ¡¼¥¿¥¹¤òÊÖ¤¹ procmail ¤ä sendmail ¤È¤¤¤Ã¤¿
MDA ¤È¤È¤â¤Ë»È¤Ã¤Æ²¼¤µ¤¤¡£
.\"O the nonzero status tells fetchmail that delivery failed and
.\"O prevents the message from being deleted off the server.  
0 °Ê³°¤Î¥¹¥Æ¡¼¥¿¥¹¤Ï fetchmail ¤ËÇÛÁ÷¤¬¼ºÇÔ¤·¤¿¤³¤È¤òÃΤ餻¡¢
¥á¥Ã¥»¡¼¥¸¤¬¥µ¡¼¥Ð¤«¤éºï½ü¤µ¤ì¤ë¤Î¤òËɻߤ·¤Þ¤¹¡£
.\"O If
.\"O \fIfetchmail\fR is running as root, it sets its userid to that of the
.\"O target user while delivering mail through an MDA.  
\fIfetchmail\fR ¤ò root ¤Ç¼Â¹Ô¤¹¤ë¤È¡¢
¥æ¡¼¥¶ ID ¤Ï MDA ·Ðͳ¤Ç¥á¡¼¥ë¤òÇÛÁ÷¤¹¤ë´Ö¤ËÂоݥ桼¥¶¤Î¤â¤Î¤ËÀßÄꤵ¤ì¤Þ¤¹¡£
.\"O Some possible MDAs
.\"O are "/usr/sbin/sendmail -oem -f %F %T", "/usr/bin/deliver" and
.\"O "/usr/bin/procmail -d %T" (but the latter is usually redundant as it's
.\"O what SMTP listeners normally forward to).  
¤³¤ì¤¬ÍøÍѤǤ­¤ë MDA ¤Ë¤Ï
"/usr/sbin/sendmail -oem -f %F %T", "/usr/bin/deliver",
"/usr/bin/procmail -d %T" ¤¬¤¢¤ê¤Þ¤¹ (¤·¤«¤·¡¢Ä̾ï¤Ï¸å¤Î¤â¤Î¤Ï¾éŤǤ¹¡£
¤Ê¤¼¤Ê¤é¤³¤ì¤ÏÄ̾SMTP ¥ê¥¹¥Ê¤¬Å¾Á÷¤ò¹Ô¤¦Àè¤À¤«¤é¤Ç¤¹)¡£
.\"O Local delivery addresses
.\"O will be inserted into the MDA command wherever you place a %T; 
%T ¤òÃÖ¤¤¤¿¾ì½ê¤Ë¤Ï¡¢MDA ¥³¥Þ¥ó¥É¤ËÂФ·¤Æ¥í¡¼¥«¥ëÇÛÁ÷¥¢¥É¥ì¥¹¤¬ÁÞÆþ¤µ¤ì¤Þ¤¹¡£
.\"O the
.\"O mail message's From address will be inserted where you place an %F.
¥á¡¼¥ë¤Î¥á¥Ã¥»¡¼¥¸¤Î From ¥¢¥É¥ì¥¹¤Ï¡¢%F ¤òÃÖ¤¤¤¿¾ì½ê¤ËÁÞÆþ¤µ¤ì¤Þ¤¹¡£
.\"O Do \fInot\fR use an MDA invocation like "sendmail -oem -t" that
.\"O dispatches on the contents of To/Cc/Bcc, it will create mail loops and
.\"O bring the just wrath of many postmasters down upon your head.
"sendmail -oem -t" ¤Î¤è¤¦¤Ê¡¢To/Cc/Bcc ¤ÎÆâÍÆ°¸¤Ë
¥á¡¼¥ë¤òȯÁ÷¤¹¤ë MDA ¤Î¸Æ¤Ó½Ð¤·¤òÍѤ¤¤Æ¤Ï\fI¤¤¤±¤Þ¤»¤ó\fR¡£
¤³¤ì¤ò¤¹¤ë¤È¥á¡¼¥ë¤Î¥ë¡¼¥×¤¬È¯À¸¤·¡¢
¤¢¤Ê¤¿¤¬ÂçÀª¤Î postmaster ¤«¤éÂçÌ̤ܶò¿©¤é¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
.TP 
.B \--lmtp
.\"O (Keyword: lmtp)
(¥­¡¼¥ï¡¼¥É: lmtp)
.\"O Cause delivery via LMTP (Local Mail Transfer Protocol).  A service
.\"O port \fImust\fR be explicitly specified (with a slash suffix) on each
.\"O host in the smtphost hunt list if this option is selected; the
.\"O default port 25 will (in accordance with RFC 2033) not be accepted.
LMTP (Local Mail Transfer Protocol) ·Ðͳ¤ÎÇÛÁ÷¤ò¹Ô¤¤¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤òÁªÂò¤·¤¿¾ì¹ç¤Ë¤Ï¡¢
smtphost ¤ÇÂоݥꥹ¥È¤Ë»ØÄꤷ¤¿³Æ¥Û¥¹¥È¤ËÂФ·¤Æ¡¢
¥µ¡¼¥Ó¥¹¤Î¥Ý¡¼¥È¤ò (¥¹¥é¥Ã¥·¥å¤Î¥µ¥Õ¥£¥Ã¥¯¥¹¤òÍѤ¤¤Æ)
ÌÀ¼¨Åª¤Ë»ØÄꤷ¤Ê¤±¤ì¤Ð\fI¤Ê¤ê¤Þ¤»¤ó\fR¡£
¥Ç¥Õ¥©¥ë¥È¥Ý¡¼¥È¤Î 25 ¤Ï (RFC 2033 ¤Ë¤è¤Ã¤Æ) ǧ¤á¤é¤ì¤Æ¤¤¤Þ¤»¤ó¡£
.TP
.\"O .B \--bsmtp <filename>
.B \--bsmtp <¥Õ¥¡¥¤¥ë̾>
.\"O (keyword: bsmtp)
(¥­¡¼¥ï¡¼¥É: bsmtp)
.\"O Append fetched mail to a BSMTP file.  This simply contains the SMTP
.\"O commands that would normally be generated by fetchmail when passing
.\"O mail to an SMTP listener daemon.  An argument of `-' causes the mail
.\"O to be written to standard output.  Note that fetchmail's
.\"O reconstruction of MAIL FROM and RCPT TO lines is not guaranteed
.\"O correct; the caveats discussed under THE USE AND ABUSE OF MULTIDROP
.\"O MAILBOXES below apply.
¼èÆÀ¤·¤¿¥á¡¼¥ë¤ò BSMTP ¥Õ¥¡¥¤¥ë¤ËÄɲä·¤Þ¤¹¡£
¤³¤ì¤Ïñ¤Ë¡¢¥á¡¼¥ë¤ò SMTP¼õ¿®¥Ç¡¼¥â¥ó¤ËÅϤ¹¤È¤­¤Ë
fetchmail ¤¬Ä̾ïÀ¸À®¤¹¤ë¤Ç¤¢¤í¤¦ SMTP ¥³¥Þ¥ó¥É¤ò´Þ¤ó¤Ç¤¤¤Þ¤¹¡£
°ú¤­¿ô¤Ë `-' ¤ò»ØÄꤹ¤ë¤È¡¢¥á¡¼¥ë¤Ïɸ½à½ÐÎϤ˽ñ¤­¹þ¤Þ¤ì¤Þ¤¹¡£
fetchmail ¤¬ÉÕ¤±Ä¾¤·¤¿ MAIL FROM ¤È RCPT TO ¹Ô¤¬Àµ¤·¤¤¤³¤È¤Î
ÊݾڤϤʤ¤ÅÀ¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
¸å½Ò¤Î¡Ö¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤ÎÍøÍѤÈÉÔÀµ»ÈÍѡפÎ
µÄÏÀ¤Ë¤ª¤±¤ëÃí°Õ»ö¹à¤¬Å¬ÍѤµ¤ì¤Þ¤¹¡£
.\"O .SS Resource Limit Control Options
.SS ¥ê¥½¡¼¥¹¤ÎÀ©¸Â¡¦À©¸æ¤Î¤¿¤á¤Î¥ª¥×¥·¥ç¥ó
.TP
.\"O .B \-l <maxbytes>, --limit <maxbytes>
.B \-l <ºÇÂç¥Ð¥¤¥È¿ô>, --limit <ºÇÂç¥Ð¥¤¥È¿ô>
.\"O (Keyword: limit)
(¥­¡¼¥ï¡¼¥É: limit)
.\"O Takes a maximum octet size argument.  Messages larger than this size
.\"O will not be fetched and will be left on the server (in foreground
.\"O sessions, the progress messages will note that they are "oversized").
.\"O If the fetch protocol permits (in particular, under IMAP or POP3
.\"O without the fetchall option) the message will not be marked seen An
.\"O explicit --limit of 0 overrides any limits set in your run control
.\"O file. This option is intended for those needing to strictly control
.\"O fetch time due to expensive and variable phone rates.  In daemon mode,
.\"O oversize notifications are mailed to the calling user (see the
.\"O --warnings option).  This option does not work with ETRN or ODMR.
¥µ¥¤¥º¤ÎºÇÂçÃͤò 10 ¿Ê¿ô¤Ç°ú¤­¿ô¤Ë¼è¤ê¤Þ¤¹¡£
¤³¤Î¥µ¥¤¥º¤è¤êÂ礭¤¤¥á¥Ã¥»¡¼¥¸¤Ï¼èÆÀ¤µ¤ì¤º¡¢¥µ¡¼¥Ð¾å¤Ë»Ä¤µ¤ì¤Þ¤¹
(¥Õ¥©¥¢¥°¥é¥¦¥ó¥É¤Î¥»¥Ã¥·¥ç¥ó¤Ç¤Ï¡¢
¿Ê¹Ô¾õ¶·¥á¥Ã¥»¡¼¥¸¤Ç "oversized (¥µ¥¤¥ºÄ¶²á)" ¤Ç¤¢¤ë¤ÈÃΤ餵¤ì¤Þ¤¹)¡£
¥á¡¼¥ë¤Î¼èÆÀ¤Ë»È¤ï¤ì¤ë¥×¥í¥È¥³¥ë
(ÆÃ¤Ë fetchall ¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Ê¤¤ IMAP ¤Þ¤¿¤Ï POP3) ¤Ë¤è¤Ã¤Æ
̤Æɤΰõ¤òÉÕ¤±¤ë¤³¤È¤¬¤Ç¤­¤ë¾ì¹ç¡¢
ÌÀ¼¨Åª¤Ë --limit ¤Ë 0 ¤ò»ØÄꤹ¤ë¤È¡¢
¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë¤ÇÀßÄꤷ¤¿¾å¸ÂÃͤòÁ´¤Æ¾å½ñ¤­¤·¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢ÅÅÏÃÎÁ¶â¤¬¹â¤¯¤ÆÊѲ½¤â¤¹¤ë¤È¤¤¤¦Íýͳ¤«¤é¡¢
¥á¡¼¥ë¼èÆÀ¤Î»þ´Ö¤ò¸·¤·¤¯À©¸æ¤¹¤ëɬÍפ¬¤¢¤ë¿Í¤Î¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£
¥Ç¡¼¥â¥ó¥â¡¼¥É¤Ç¤Ï¡¢¥µ¥¤¥ºÄ¶²á¤ÎÄÌÃΤÏ
¸Æ¤Ó½Ð¤·¤ò¹Ô¤Ã¤¿¥æ¡¼¥¶¤ËÂФ·¤Æ¥á¡¼¥ë¤Ç¹Ô¤ï¤ì¤Þ¤¹
(--warning ¥ª¥×¥·¥ç¥ó¤ò»²¾È)¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï ETRN ¤È ODMR ¤Ç¤Ï»È¤¨¤Þ¤»¤ó¡£
.TP
.\"O .B \-w <interval>, --warnings <interval>
.B \-w <´Ö³Ö>, --warnings <´Ö³Ö>
.\"O (Keyword: warnings)
(¥­¡¼¥ï¡¼¥É: warnings)
.\"O Takes an interval in seconds.  When you call
.\"O .I fetchmail
.\"O with a `limit' option in daemon mode, this controls the interval at
.\"O which warnings about oversized messages are mailed to the calling user
.\"O (or the user specified by the `postmaster' option).  One such
.\"O notification is always mailed at the end of the the first poll that
.\"O the oversized message is detected.  Thereafter, renotification is
.\"O suppressed until after the warning interval elapses (it will take
.\"O place at the end of the first following poll).
»þ´Ö´Ö³Ö¤òÉÿô¤Ç°ú¤­¿ô¤Ë¼è¤ê¤Þ¤¹¡£
¥Ç¡¼¥â¥ó¥â¡¼¥É¤Ç `limit' ¥ª¥×¥·¥ç¥ó¤òÉÕ¤±¤Æ
.I fetchmail
¤ò¸Æ¤Ó½Ð¤¹¤È¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¥µ¥¤¥º¤òĶ²á¤·¤Æ¤¤¤ë¥á¥Ã¥»¡¼¥¸¤Ë´Ø¤¹¤ë·Ù¹ð¤¬
¸Æ¤Ó½Ð¤·¤¿¥æ¡¼¥¶ (¤Þ¤¿¤Ï `postmaster' ¥ª¥×¥·¥ç¥ó¤Ç»ØÄꤷ¤¿¥æ¡¼¥¶) ¤Ë
¥á¡¼¥ë¤ÇÁ÷¤é¤ì¤ë»þ´Ö´Ö³Ö¤òÀ©¸æ¤·¤Þ¤¹¡£
¤³¤Î¤è¤¦¤ÊÄÌÃΤϾï¤Ë¡¢¥µ¥¤¥º¤òĶ²á¤·¤Æ¤¤¤ë¥á¥Ã¥»¡¼¥¸¤¬¸«¤Ä¤«¤Ã¤¿
ºÇ½é¤Î¥Ý¡¼¥ê¥ó¥°¤Î½ªÎ»»þ¤Ë¥á¡¼¥ë¤ÇÁ÷¤é¤ì¤Þ¤¹¡£
¤½¤Î¸å¤Ï¡¢·Ù¹ð»þ´Ö´Ö³Ö¤¬·Ð²á¤¹¤ë¤Þ¤ÇºÆÄÌÃΤϻߤá¤é¤ì¤Þ¤¹
(¤³¤ì¤Ï¡¢¸å¤Ë³¤¯ºÇ½é¤Î¥Ý¡¼¥ê¥ó¥°¤Î½ªÎ»»þ¤Ë¹Ô¤ï¤ì¤Þ¤¹)¡£
.TP
.\"O .B -b <count>, --batchlimit <count>
.B -b <ºÇÂç¿ô>, --batchlimit <ºÇÂç¿ô>
.\"O (Keyword: batchlimit)
(¥­¡¼¥ï¡¼¥É: batchlimit)
.\"O Specify the maximum number of messages that will be shipped to an SMTP
.\"O listener before the connection is deliberately torn down and rebuilt
.\"O (defaults to 0, meaning no limit).  An explicit --batchlimit of 0
.\"O overrides any limits set in your run control file.  While
.\"O \fBsendmail\fR(8) normally initiates delivery of a message immediately
.\"O after receiving the message terminator, some SMTP listeners are not so
.\"O prompt.  MTAs like \fIqmail\fR(8) and \fIsmail\fR(8) may wait till the
.\"O delivery socket is shut down to deliver.  This may produce annoying
.\"O delays when \fIfetchmail\fR is processing very large batches.  Setting
.\"O the batch limit to some nonzero size will prevent these delays.  This
.\"O option does not work with ETRN or ODMR.
Àܳ¤ò¤ï¤¶¤È»ß¤á¤Æ¤«¤éºÆÀܳ¤¹¤ë¤Þ¤Ç¤Ë
SMTP ¼õ¿®¥×¥í¥°¥é¥à¤ËÁ÷¿®¤¹¤ë¥á¥Ã¥»¡¼¥¸¤ÎºÇÂç¿ô¤ò»ØÄꤷ¤Þ¤¹
(¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 0 ¤Ç¡¢¤³¤ì¤Ï̵À©¸Â¤òɽ¤·¤Þ¤¹)¡£
ÌÀ¼¨Åª¤Ë --batchlimit ¤Ë 0 ¤ò»ØÄꤹ¤ë¤È¡¢
¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë¤ÇÀßÄꤵ¤ì¤Æ¤¤¤ë¾å¸ÂÃͤÏÁ´¤Æ¾å½ñ¤­¤µ¤ì¤Þ¤¹¡£
\fBsendmail\fR(8) ¤ÏÄ̾
¥á¥Ã¥»¡¼¥¸½ªÃ¼»Ò¤ò¼õ¿®¤·¤¿Ä¾¸å¤Ë¥á¥Ã¥»¡¼¥¸¤ÎÇÛÁ÷¤ò»Ï¤á¤Þ¤¹¤¬¡¢
¤½¤ó¤Ê¤ËÁÇÁ᤯±þÅú¤·¤Ê¤¤ SMTP ¼õ¿®¥×¥í¥°¥é¥à¤â¤¢¤ê¤Þ¤¹¡£
\fIqmail\fR(8) ¤ä \fIsmail\fR(8) Åù¤Î MTA ¤Ï¡¢
ÇÛÁ÷¥½¥±¥Ã¥È¤¬ÊĤ¸¤é¤ì¤ë¤Þ¤ÇÇÛÁ÷¤òÂԤĤ³¤È¤¬¤¢¤ê¤Þ¤¹¡£
\fIfetchmail\fR ¤¬µðÂç¤Ê¥Ð¥Ã¥Á½èÍý¤ò¹Ô¤Ã¤Æ¤¤¤ë»þ¤Ë¤Ï¡¢
¤³¤ì¤Ï¤¦¤Ã¤È¤¦¤·¤¤ÃÙ¤ì¤ò°ú¤­µ¯¤³¤¹¤«¤â¤·¤ì¤Þ¤»¤ó¡£
¥Ð¥Ã¥Á¤Î¾å¸ÂÃͤ˥¼¥í¤Ç¤Ê¤¤Ãͤò²¿¤«ÀßÄꤷ¤Æ¤ª¤¯¤È¡¢
¤³¤Î¤è¤¦¤ÊÃÙ¤ì¤òËɤ°¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï ETRN ¤È ODMR ¤Ç¤ÏÆ°ºî¤·¤Þ¤»¤ó¡£
.TP
.\"O .B -B <number>, --fetchlimit <number>
.B -B <¾å¸ÂÃÍ>, --fetchlimit <¾å¸ÂÃÍ>
.\"O (Keyword: fetchlimit)
(¥­¡¼¥ï¡¼¥É: fetchlimit)
.\"O Limit the number of messages accepted from a given server in a single
.\"O poll.  By default there is no limit. An explicit --fetchlimit of 0
.\"O overrides any limits set in your run control file.
.\"O This option does not work with ETRN or ODMR.
»ØÄꤵ¤ì¤¿¥µ¡¼¥Ð 1 ¤Ä¤«¤é¤Î 1 Å٤Υݡ¼¥ê¥ó¥°¤Ç¼èÆÀ¤Ç¤­¤ë
¥á¥Ã¥»¡¼¥¸¿ô¤òÀ©¸Â¤·¤Þ¤¹¡£
¥Ç¥Õ¥©¥ë¥È¤Ç¤ÏÀ©¸Â¤Ï¤¢¤ê¤Þ¤»¤ó¡£
ÌÀ¼¨Åª¤Ë --fetchlimit ¤Ë 0 ¤òÀßÄꤹ¤ë¤È¡¢
¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë¤ÇÀßÄꤷ¤¿¾å¸ÂÃͤòÁ´¤Æ¾å½ñ¤­¤·¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï ETRN ¤È ODMR ¤Ç¤ÏÆ°ºî¤·¤Þ¤»¤ó¡£
.TP
.\"O .B -e <count>, --expunge <count>
.B -e <¥á¥Ã¥»¡¼¥¸¿ô>, --expunge <¥á¥Ã¥»¡¼¥¸¿ô>
.\"O (keyword: expunge)
(¥­¡¼¥ï¡¼¥É: expunge)
.\"O Arrange for deletions to be made final after a given number of
.\"O messages.  Under POP2 or POP3, fetchmail cannot make deletions final
.\"O without sending QUIT and ending the session -- with this option on,
.\"O fetchmail will break a long mail retrieval session into multiple
.\"O subsessions, sending QUIT after each sub-session. This is a good
.\"O defense against line drops on POP3 servers that do not do the
.\"O equivalent of a QUIT on hangup.  Under IMAP,
.\"O .I fetchmail
.\"O normally issues an EXPUNGE command after each deletion in order to
.\"O force the deletion to be done immediately.  This is safest when your
.\"O connection to the server is flaky and expensive, as it avoids
.\"O resending duplicate mail after a line hit.  However, on large
.\"O mailboxes the overhead of re-indexing after every message can slam the
.\"O server pretty hard, so if your connection is reliable it is good to do
.\"O expunges less frequently.  If you specify this option to an integer N,
.\"O it tells
.\"O .I fetchmail
.\"O to only issue expunges on every Nth delete.  An argument of zero
.\"O suppresses expunges entirely (so no expunges at all will be done until
.\"O the end of run).  This option does not work with ETRN or ODMR.
»ØÄꤵ¤ì¤¿¿ô¤Î¥á¥Ã¥»¡¼¥¸¤Î¸å¤Ëºï½ü¤¬¹Ô¤ï¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
POP2 ¤ä POP3 ¤Î¾ì¹ç¤Ë¤Ï¡¢fetchmail ¤Ï QUIT ¤òÁ÷¤Ã¤Æ
¥»¥Ã¥·¥ç¥ó¤ò½ª¤ï¤é¤Ê¤±¤ì¤Ðºï½ü¤ò¹Ô¤¦¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£
¤·¤¿¤¬¤Ã¤Æ¤³¤Î¥ª¥×¥·¥ç¥ó¤ò on ¤Ë¤¹¤ë¤È¡¢
fetchmail ¤ÏŤ¤¥á¡¼¥ë¼èÆÀ¥»¥Ã¥·¥ç¥ó¤òÊ£¿ô¤Î¥µ¥Ö¥»¥Ã¥·¥ç¥ó¤Ëʬ³ä¤·¡¢
³Æ¥µ¥Ö¥»¥Ã¥·¥ç¥ó¤Î¸å¤Ë QUIT ¤òÁ÷¤ê¤Þ¤¹¡£
¤³¤ì¤Ï¡¢²óÀþ¤¬Àڤ줿»þ¤Ë QUIT ¤ÈƱÅù¤Î½èÍý¤ò¹Ô¤ï¤Ê¤¤
POP3 ¥µ¡¼¥Ð¤Çµ¯¤³¤ë¹ÔÍî¤Á¤ËÂФ¹¤ëÎɤ¤Âкö¤Ë¤Ê¤ê¤Þ¤¹¡£
IMAP ¤Î¾ì¹ç¤Ë¤Ï¡¢
.I fetchmail
¤Ïºï½ü¤ò¨ºÂ¤Ë¹Ô¤ï¤»¤ë¤¿¤á¤Ë¡¢
ºï½ü¤ò¹Ô¤¦¤¿¤Ó¤Ë EXPUNGE ¥³¥Þ¥ó¥É¤òȯ¹Ô¤¹¤ë¤Î¤¬ÉáÄ̤Ǥ¹¡£
¤³¤ì¤Ï¥µ¡¼¥Ð¤È¤ÎÄÌ¿®¤¬ÉÔ°ÂÄê¤Ê»þ¤ä¹â²Á¤Ê»þ¤Ë¤ÏÈó¾ï¤Ë°ÂÁ´¤ÊÊýË¡¤Ç¤¹¡£
¤È¤¤¤¦¤Î¤â¡¢Àܳ¤¬ÀÚ¤ì¤Æ¤·¤Þ¤Ã¤¿¸å¤Ë
Ʊ¤¸¥á¡¼¥ë¤òºÆ¤Ó¼õ¤±¼è¤é¤Ê¤¯¤ÆºÑ¤à¤«¤é¤Ç¤¹¡£
¤·¤«¤·¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤¬Â礭¤¤¾ì¹ç¤Ë¤Ï¡¢
¥á¥Ã¥»¡¼¥¸¤ò¾Ã¤¹¤¿¤Ó¤´¤È¤Ë¥¤¥ó¥Ç¥Ã¥¯¥¹¤òÉÕ¤±Ä¾¤¹»þ¤Î¥ª¡¼¥Ð¡¼¥Ø¥Ã¥É¤Ç¡¢
¥µ¡¼¥Ð¤¬¤«¤Ê¤êÂçÊѤÊÌܤËÁø¤¦¤«¤â¤·¤ì¤Þ¤»¤ó¡£
¤Ç¤¹¤«¤é¡¢Àܳ¤Î¿®ÍêÀ­¤¬¹â¤¤¾ì¹ç¤Ë¤Ï¡¢
ºï½ü¤ò¹Ô¤¦´Ö³Ö¤ÏŤ¯¤·¤¿¤Û¤¦¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤ËÀ°¿ô N ¤ò»ØÄꤹ¤ë¤È¡¢
.I fetchmail
¤Ï N ²óÌܤκï½ü¤Î»þ¤À¤±¼ÂºÝ¤Îºï½ü¤ò¹Ô¤¤¤Þ¤¹¡£
°ú¤­¿ô¤Ë 0 ¤ò»ØÄꤹ¤ë¤È¡¢ºï½ü¤ÏÁ´¤¯¹Ô¤ï¤ì¤Ê¤¯¤Ê¤ê¤Þ¤¹
(¤·¤¿¤¬¤Ã¤Æ¡¢¼Â¹Ô½ªÎ»»þ¤Þ¤Çºï½ü¤ÏÁ´¤¯¹Ô¤ï¤ì¤Þ¤»¤ó)¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï ETRN ¤È ODMR ¤Ç¤ÏÆ°ºî¤·¤Þ¤»¤ó¡£
.\"O .SS Authentication Options
.SS ǧ¾Ú¤Ë´Ø¤¹¤ë¥ª¥×¥·¥ç¥ó
.TP
.\"O .B \-u <name>, --username <name>
.B \-u <¥æ¡¼¥¶Ì¾>, --username <¥æ¡¼¥¶Ì¾>
.\"O (Keyword: user[name])
(¥­¡¼¥ï¡¼¥É: user[name])
.\"O Specifies the user identification to be used when logging in to the mailserver.
.\"O The appropriate user identification is both server and user-dependent.  
.\"O The default is your login name on the client machine that is running 
.\"O .I fetchmail.
.\"O See USER AUTHENTICATION below for a complete description.
¥á¡¼¥ë¥µ¡¼¥Ð¤Ë¥í¥°¥¤¥ó¤¹¤ë¤È¤­¤Ë»È¤¦¥æ¡¼¥¶¼±Ê̾ðÊó¤ò»ØÄꤷ¤Þ¤¹¡£
ŬÀڤʥ桼¥¶¼±Ê̾ðÊó¤Ï¥á¡¼¥ë¥µ¡¼¥Ð¤È¥æ¡¼¥¶¤ÎξÊý¤Ë°Í¸¤·¤Þ¤¹¡£
¥Ç¥Õ¥©¥ë¥ÈÃͤÏ
.I fetchmail
¤ò¼Â¹Ô¤·¤¿¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¾å¤Ç¤Î¥í¥°¥¤¥ó̾¤Ç¤¹¡£
.TP
.\"O .B \-I <specification>, --interface <specification>
.B \-I <¥¤¥ó¥¿¥Õ¥§¡¼¥¹»ØÄê>, --interface <¥¤¥ó¥¿¥Õ¥§¡¼¥¹»ØÄê>
.\"O (Keyword: interface)
(¥­¡¼¥ï¡¼¥É: interface)
.\"O Require that a specific interface device be up and have a specific local
.\"O or remote IP address (or range) before polling.  Frequently
.\"O .I fetchmail
.\"O is used over a transient point-to-point TCP/IP link established directly
.\"O to a mailserver via SLIP or PPP.  That is a relatively secure channel.
¥Ý¡¼¥ê¥ó¥°¤ò¹Ô¤¦Á°¤Ë¡¢ÆÃÄê¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹¥Ç¥Ð¥¤¥¹¤¬Æ°ºî¤·¤Æ¤¤¤ë¤³¤È¤È¡¢
ÆÃÄê¤Î¥í¡¼¥«¥ë¤Þ¤¿¤Ï¥ê¥â¡¼¥È¤Î IP ¥¢¥É¥ì¥¹
(¤Þ¤¿¤Ï¥¢¥É¥ì¥¹ÈÏ°Ï) ¤ò»ý¤Ä¤³¤È¤òÍ׵ᤷ¤Þ¤¹¡£
.I fetchmail
¤Ï
SLIP ¤ä PPP ·Ðͳ¤Ç¥á¡¼¥ë¥µ¡¼¥Ð¤ËÂФ·¤ÆľÀܳÎΩ¤µ¤ì¤¿ point-to-point ¤Î
TCP/IP ¥ê¥ó¥¯¾å¤Ç»È¤ï¤ì¤ë¤³¤È¤¬¤è¤¯¤¢¤ê¤Þ¤¹¡£
¤³¤ì¤ÏÈæ³ÓŪ°ÂÁ´¤Ê¥Á¥ã¥Í¥ë¤Ç¤¹¡£
.\"O But when other TCP/IP routes to the mailserver exist (e.g. when the link
.\"O is connected to an alternate ISP), your username and password may be
.\"O vulnerable to snooping (especially when daemon mode automatically polls
.\"O for mail, shipping a clear password over the net at predictable
.\"O intervals).  The --interface option may be used to prevent this.  When
.\"O the specified link is not up or is not connected to a matching IP
.\"O address, polling will be skipped.  The format is:
¤·¤«¤·¡¢¥á¡¼¥ë¥µ¡¼¥Ð¤Ø¤Î¾¤Î TCP/IP ·ÐÏ©¤¬Â¸ºß¤¹¤ë¤È¤­
(Îã: ¥ê¥ó¥¯¤¬Ê̤ΠISP ¤ËÀܳ¤µ¤ì¤Æ¤¤¤ë¤È¤­)¡¢
¤¢¤Ê¤¿¤Î¥æ¡¼¥¶Ì¾¤È¥Ñ¥¹¥ï¡¼¥É¤ÏÅðÄ°¤ËÂФ·¤ÆÀȼå¤Ç¤¹
(Æä˥ǡ¼¥â¥ó¥â¡¼¥É¤¬¼«Æ°Åª¤Ë¥á¡¼¥ë¤ò¥Ý¡¼¥ê¥ó¥°¤·¡¢
ʿʸ¤Î¥Ñ¥¹¥ï¡¼¥É¤òͽ¬²Äǽ¤Ê´Ö³Ö¤Ç¥Í¥Ã¥È¥ï¡¼¥¯¾å¤Ëή¤·¤Æ¤¤¤ë¾ì¹ç)¡£
--interface ¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢¤³¤ì¤òËɤ°¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
»ØÄꤵ¤ì¤¿¥ê¥ó¥¯¤¬¾å¤¬¤Ã¤Æ¤¤¤Ê¤¤¤È¤­¤ä¡¢
¥Þ¥Ã¥Á¤¹¤ë IP ¥¢¥É¥ì¥¹¤ËÀܳ¤µ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Ë¤Ï¡¢
¥Ý¡¼¥ê¥ó¥°¤ÏÈô¤Ð¤µ¤ì¤Þ¤¹¡£
¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï°Ê²¼¤Ç¤¹:
.sp
        interface/iii.iii.iii.iii/mmm.mmm.mmm.mmm
.sp
.\"O The field before the first slash is the interface name (i.e. sl0, ppp0
.\"O etc.).  The field before the second slash is the acceptable IP address.
.\"O The field after the second slash is a mask which specifies a range of
.\"O IP addresses to accept.  If no mask is present 255.255.255.255 is
.\"O assumed (i.e. an exact match).  This option is currently only supported
.\"O under Linux and FreeBSD. Please see the 
.\"O .B monitor 
.\"O section for below for FreeBSD specific information.
ºÇ½é¤Î¥¹¥é¥Ã¥·¥å¤ÎÁ°¤Î¥Õ¥£¡¼¥ë¥É¤Ï¥¤¥ó¥¿¥Õ¥§¡¼¥¹Ì¾¤Ç¤¹
(¤Ä¤Þ¤ê¡¢sl0, ppp0 Åù)¡£
2 ÈÖÌܤΥ¹¥é¥Ã¥·¥å¤ÎÁ°¤Î¥Õ¥£¡¼¥ë¥É¤Ïµö²Ä¤µ¤ì¤ë IP ¥¢¥É¥ì¥¹¤Ç¤¹¡£
2 ÈÖÌܤΥ¹¥é¥Ã¥·¥å¤Î¸å¤Î¥Õ¥£¡¼¥ë¥É¤Ï¡¢µö²Ä¤¹¤ë IP ¥¢¥É¥ì¥¹¤ÎÈϰϤò
»ØÄꤹ¤ë¥Þ¥¹¥¯ÃͤǤ¹¡£
¥Þ¥¹¥¯¤¬¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢255.255.255.255 (¤Ä¤Þ¤ê¡¢´°Á´¤Ê¥Þ¥Ã¥Á) 
¤¬»ØÄꤵ¤ì¤¿¤â¤Î¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò¸½ºß¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤Î¤Ï Linux ¤È FreeBSD ¤À¤±¤Ç¤¹¡£
FreeBSD ¸ÇÍ­¤Î¾ðÊó¤Ë¤Ä¤¤¤Æ¤Ï¡¢¸å½Ò¤Î
.B monitor 
¥»¥¯¥·¥ç¥ó¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
.TP
.\"O .B \-M <interface>, --monitor <interface>
.B \-M <¥¤¥ó¥¿¥Õ¥§¡¼¥¹>, --monitor <¥¤¥ó¥¿¥Õ¥§¡¼¥¹>
.\"O (Keyword: monitor)
(¥­¡¼¥ï¡¼¥É: monitor)
.\"O Daemon mode can cause transient links which are automatically taken down
.\"O after a period of inactivity (e.g. PPP links) to remain up
.\"O indefinitely.  This option identifies a system TCP/IP interface to be
.\"O monitored for activity.  After each poll interval, if the link is up but
.\"O no other activity has occurred on the link, then the poll will be
.\"O skipped.  However, when fetchmail is woken up by a signal, the
.\"O monitor check is skipped and the poll goes through unconditionally.
.\"O This option is currently only supported under Linux and FreeBSD.
¥Ç¡¼¥â¥ó¥â¡¼¥É¤Ç¤Ï¡¢¥¢¥¯¥Æ¥£¥Ö¤Ç¤Ê¤¤¾õÂÖ¤¬°ìÄê»þ´Ö³¤¯¤È¡¢
¼«Æ°Åª¤ËÀÚÃǤµ¤ì¤ë°ì»þŪ¤Ê¥ê¥ó¥¯ (Îã: PPP Àܳ) ¤¬
¤¤¤Ä¤Þ¤Ç¤âÀܳ¤·¤¿¤Þ¤Þ¤Ë¤Ê¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¥¢¥¯¥Æ¥£¥Ö¾õÂÖ¤ò´Æ»ë¤¹¤ë
¥·¥¹¥Æ¥à¤Î TCP/IP ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ò»ØÄꤷ¤Þ¤¹¡£
Ëè²ó¤Î¥Ý¡¼¥ê¥ó¥°´Ö³Ö¤Î¸å¡¢¥ê¥ó¥¯¤¬³ÎΩ¤·¤Æ¤¤¤ë¤±¤ì¤É
¤½¤Î¥ê¥ó¥¯¾å¤Ç¾¤ÎÄÌ¿®¤¬¤µ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢¥Ý¡¼¥ê¥ó¥°¤ÏÈô¤Ð¤µ¤ì¤Þ¤¹¡£
¤·¤«¤·¡¢fetchmail ¤¬¥·¥°¥Ê¥ë¤Çµ¯Æ°¤µ¤ì¤¿¾ì¹ç¤Ï¡¢
´Æ»ë¤Î¥Á¥§¥Ã¥¯¤ÏÈô¤Ð¤µ¤ì¡¢Ìµ¾ò·ï¤Ë¥Ý¡¼¥ê¥ó¥°¤¬¹Ô¤ï¤ì¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¸½ºß Linux ¤È FreeBSD ¤Ç¤Î¤ß¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
.\"O For the 
.\"O .B monitor 
.\"O and 
.\"O .B interface
.\"O options to work for non root users under FreeBSD, the fetchmail binary
.\"O must be installed SGID kmem. This would be a security hole, but
.\"O fetchmail runs with the effective GID set to that of the kmem group
.\"O .I only
.\"O when interface data is being collected.
FreeBSD ¤Î¾ì¹ç¡¢
.B monitor 
¥ª¥×¥·¥ç¥ó¤È
.B interface
¥ª¥×¥·¥ç¥ó¤ò root °Ê³°¤Î¥æ¡¼¥¶¤ÇÆ°ºî¤µ¤»¤ë¤Ë¤Ï¡¢SGID kmem ¤·¤Æ
fetchmail ¤Î¥Ð¥¤¥Ê¥ê¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
¤³¤ì¤Ï¥»¥­¥å¥ê¥Æ¥£¥Û¡¼¥ë¤Ë¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤¬¡¢
fetchmail ¤Ï¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Î¥Ç¡¼¥¿¤ò½¸¤á¤ë¤È¤­
.I ¤À¤±
¼Â¸ú GID ¤ò kmem ¥°¥ë¡¼¥×¤ËÀßÄꤷ¤ÆÆ°ºî¤·¤Þ¤¹¡£
.TP
.\"O .B --auth <type>
.B --auth <¥¿¥¤¥×>
.\"O (Keyword: auth[enticate])
(¥­¡¼¥ï¡¼¥É: auth[enticate])
.\"O This option permits you to specify an authentication type (see USER
.\"O AUTHENTICATION below for details).  
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤Èǧ¾Ú¤Î¥¿¥¤¥×¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹
(¾Ü¤·¤¯¤Ï¡Ö¥æ¡¼¥¶Ç§¾Ú¡×¤Î¹à¤ò¤´Í÷¤¯¤À¤µ¤¤)¡£
.\"O The possible values are \fBany\fR,
.\"O \&`\fBpassword\fR', `\fBkerberos_v5\fR' and `\fBkerberos\fR' (or, for
.\"O excruciating exactness, `\fBkerberos_v4\fR'), \fRgssapi\fR,
.\"O \fIcram-md5\fR, \fIotp\fR, \fIntlm\fR, and \fBssh\fR.  
»ØÄê²Äǽ¤ÊÃͤϡ¢\fBany\fR, \&`\fBpassword\fR', `\fBkerberos_v5\fR', 
`\fBkerberos\fR' (Èó¾ï¤ËÀµ³Î¤Ë¸À¤¦¤È `\fBkerberos_v4\fR'), \fRgssapi\fR, 
\fIcram-md5\fR, \fIotp\fR, \fIntlm\fR, \fBssh\fR ¤Ç¤¹¡£
.\"O When \fBany\fR (the
.\"O default) is specified, fetchmail tries first methods that don't
.\"O require a password (GSSAPI, KERBEROS_IV); then it looks for methods
.\"O that mask your password (CRAM-MD5, X-OTP, NTLM); and only if the server
.\"O doesn't support any of those will it ship your password en clair.
(¥Ç¥Õ¥©¥ë¥È¤Î) \fBany\fR ¤ò»ØÄꤹ¤ë¤È¡¢
fetchmail ¤Ï¡¢¤Þ¤ººÇ½é¤Ë¥Ñ¥¹¥ï¡¼¥É¤òɬÍפȤ·¤Ê¤¤ÊýË¡
(GSSAPI, KERBEROS_IV) ¤ò»î¤·¤Þ¤¹¡£
¼¡¤Ë¥Ñ¥¹¥ï¡¼¥É¤ò±£¤¹ÊýË¡ (CRAM-MD5, X-OTP, NTLM) ¤òõ¤·¤Þ¤¹¡£
¤½¤·¤Æ¡¢¥µ¡¼¥Ð¤¬¤³¤ì¤é¤ÎÊýË¡¤Î¤É¤ì¤â¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ë¤Î¤ß¡¢
¥Ñ¥¹¥ï¡¼¥É¤òʿʸ¤ÇÅϤ·¤Þ¤¹¡£
.\"O Other values may be used to force various authentication methods
.\"O (\fBssh\fR suppresses authentication).  
¤½¤ì°Ê³°¤ÎÃͤϡ¢¤¤¤í¤¤¤í¤Êǧ¾ÚÊýË¡¤ò¶¯À©¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹
(\fBssh\fR ¤Ïǧ¾Ú¤ò¤µ¤»¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹)¡£
.\"O Any value other than
.\"O \fIpassword\fR, \fIcram-md5\fR, \fIntlm\fR or \fIotp\fR suppresses fetchmail's
.\"O normal inquiry for a password.  
\fIpassword\fR, \fIcram-md5\fR, \fIntlm\fR, \fIotp\fR °Ê³°¤ÎÃͤǤϡ¢
fetchmail ¤Ë¤è¤ëÄ̾ï¤Î¥Ñ¥¹¥ï¡¼¥ÉÌ䤤¹ç¤ï¤»¤ò¤µ¤»¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£
.\"O Specify \fIssh\fR when you are using
.\"O an end-to-end secure connection such as an ssh tunnel; 
ssh ¥È¥ó¥Í¥ë¤Î¤è¤¦¤Ê end-to-end ¤Î°ÂÁ´¤ÊÀܳ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¡¢
\fIssh\fR ¤ò»ØÄꤷ¤Æ²¼¤µ¤¤¡£
.\"O specify
.\"O \fRgssapi\fR or \fBkerberos_v4\fR if you are using a protocol variant
.\"O that employs GSSAPI or K4.  
GSSAPI ¤Þ¤¿¤Ï K4 ¤ò»È¤Ã¤¿¥×¥í¥È¥³¥ë¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
\fRgssapi\fR ¤Þ¤¿¤Ï \fBkerberos_v4\fR ¤ò»ØÄꤷ¤Æ²¼¤µ¤¤¡£
.\"O Choosing KPOP protocol automatically
.\"O selects Kerberos authentication.  
KPOP ¥×¥í¥È¥³¥ë¤òÁªÂò¤¹¤ë¤È¼«Æ°Åª¤Ë Kerberos ǧ¾Ú¤¬ÁªÂò¤µ¤ì¤Þ¤¹¡£
.\"O This option does not work with ETRN.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï ETRN ¤Ç¤ÏÆ°ºî¤·¤Þ¤»¤ó¡£
.\"O .SS Miscellaneous Options
.SS ¤½¤Î¾¤Î¥ª¥×¥·¥ç¥ó
.TP
.\"O .B \-f <pathname>, --fetchmailrc <pathname>
.B \-f <¥Ñ¥¹Ì¾>, --fetchmailrc <¥Ñ¥¹Ì¾>
.\"O Specify a non-default name for the 
.\"O .I ~/.fetchmailrc
.\"O run control file.  The pathname argument must be either "-" (a single
.\"O dash, meaning to read the configuration from standard input) or a
.\"O filename.  Unless the --version option is also on, a named file
.\"O argument must have permissions no more open than 0600 (u=rw,g=,o=) or
.\"O else be /dev/null.
.I ~/.fetchmailrc
¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë¤È¤·¤Æ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ê¤¤Ì¾Á°¤ò»ØÄꤷ¤Þ¤¹¡£
<¥Ñ¥¹Ì¾> °ú¤­¿ô¤Ï "-"
(¥À¥Ã¥·¥å 1 ¤Ä¡¢É¸½àÆþÎϤ«¤éÀßÄê¤òÆɤ߹þ¤à¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹)
¤Þ¤¿¤Ï¥Õ¥¡¥¤¥ë̾¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
Ʊ»þ¤Ë --version ¥ª¥×¥·¥ç¥ó¤âÍ­¸ú¤Ë¤·¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢
»ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë°ú¤­¿ô¤Ï
0600 (u=rw,g=,o=) °Ê³°¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤ò»ý¤Ã¤Æ¤¤¤ë¤«¡¢
¤½¤¦¤Ç¤Ê¤±¤ì¤Ð /dev/null ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.TP
.\"O .B \-i <pathname>, --idfile <pathname>
.B \-i <¥Ñ¥¹Ì¾>, --idfile <¥Ñ¥¹Ì¾>
.\"O (Keyword: idfile)
(¥­¡¼¥ï¡¼¥É: idfile)
.\"O Specify an alternate name for the .fetchids file used to save POP3
.\"O UIDs. 
POP3 ¤Î UID ¤òÊݸ¤¹¤ë¤¿¤á¤Ë»È¤¦ .fetchids ¥Õ¥¡¥¤¥ë¤ËÊ̤Î̾Á°¤ò»ØÄꤷ¤Þ¤¹¡£
.TP
.B \-n, --norewrite
.\"O (Keyword: no rewrite)
(¥­¡¼¥ï¡¼¥É: no rewrite)
.\"O Normally,
.\"O .I fetchmail
.\"O edits RFC-822 address headers (To, From, Cc, Bcc, and Reply-To) in
.\"O fetched mail so that any mail IDs local to the server are expanded to
.\"O full addresses (@ and the mailserver hostname are appended).  This enables 
.\"O replies on the client to get addressed correctly (otherwise your
.\"O mailer might think they should be addressed to local users on the
.\"O client machine!).  This option disables the rewrite.  (This option is
.\"O provided to pacify people who are paranoid about having an MTA edit
.\"O mail headers and want to know they can prevent it, but it is generally
.\"O not a good idea to actually turn off rewrite.)
.\"O When using ETRN or ODMR, the rewrite option is ineffective.
Ä̾
.I fetchmail
¤Ï¼èÆÀ¤·¤¿¥á¡¼¥ëÃæ¤Î RFC-822 ¤Î¥¢¥É¥ì¥¹¥Ø¥Ã¥À
(To, From, Cc, Bcc, Reply-To) ¤òÊÔ½¸¤·¡¢
¥µ¡¼¥Ð¤ËÂФ·¤Æ¥í¡¼¥«¥ë¤Ê¥á¡¼¥ë¤Î ID ¤¬´°Á´¤Ê¥¢¥É¥ì¥¹¤ËŸ³«¤µ¤ì¤Þ¤¹
(@ ¤È¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥Û¥¹¥È̾¤¬Äɲ䵤ì¤Þ¤¹)¡£
¤³¤ì¤Ë¤è¤ê¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ë¤ª¤±¤ë¥ê¥×¥é¥¤¤Ç
°¸Àè¤òÀµ¤·¤¯¤¹¤ë¤³¤È¤¬²Äǽ¤Ë¤Ê¤ê¤Þ¤¹
(¤³¤Î¤è¤¦¤Ë¤·¤Ê¤¤¾ì¹ç¡¢¥á¡¼¥é¤Ï¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¤Î
¥í¡¼¥«¥ë¥æ¡¼¥¶¤ËÁ÷¤ë¤Ù¤­¤À¤È¹Í¤¨¤ë¤«¤â¤·¤ì¤Þ¤»¤ó!)¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¤³¤Î½ñ¤­´¹¤¨¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£
(¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢MTA ¤¬¥á¡¼¥ë¤Î¥Ø¥Ã¥À¤òÊÔ½¸¤¹¤ë¤³¤È¤ËÂФ·¤Æ¿À·Ð¼Á¤Ç¡¢
¤³¤ì¤ò»ß¤á¤é¤ì¤ë¤³¤È¤òÃΤꤿ¤¤¿Í¡¹¤ò¤Ê¤À¤á¤ë¤¿¤á¤ËÍÑ°Õ¤·¤Æ¤¤¤Þ¤¹¡£
¤·¤«¤·°ìÈÌŪ¤Ë¤Ï¡¢¼ÂºÝ¤Ë½ñ¤­´¹¤¨¤ò»ß¤á¤ë¤Î¤ÏÎɤ¤¹Í¤¨¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£)
ETRN ¤ä ODMR ¤ò»È¤¦¤È¤­¤Ë¤Ï¡¢½ñ¤­´¹¤¨¥ª¥×¥·¥ç¥ó¤Ï̵¸ú¤Ç¤¹¡£
.TP
.\"O .B -E <line>, --envelope <line>
.B -E <envelope ¹Ô>, --envelope <envelope ¹Ô>
.\"O (Keyword: envelope)
(¥­¡¼¥ï¡¼¥É: envelope)
.\"O This option changes the header 
.\"O .I fetchmail
.\"O assumes will carry a copy of the mail's envelope address.  Normally
.\"O this is `X-Envelope-To' but as this header is not standard, practice
.\"O varies. See the discussion of multidrop address handling below.  As a
.\"O special case, `envelope "Received"' enables parsing of sendmail-style
.\"O Received lines.  This is the default, and it should not be necessary
.\"O unless you have globally disabled Received parsing with `no envelope'
.\"O in the \fI.fetchmailrc\fR file.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢
.I fetchmail
¤¬¥á¡¼¥ë¤Î envelope ¥¢¥É¥ì¥¹¤Î¥³¥Ô¡¼¤ò±¿¤Ö¤ÈÁÛÄꤹ¤ë¥Ø¥Ã¥À¤òÊѹ¹¤·¤Þ¤¹¡£
Ä̾盧¤ì¤Ï `X-Envelope-To' ¤Ç¤¹¤¬¡¢¤³¤ì¤Ïɸ½à¥Ø¥Ã¥À¤Ç¤Ï¤Ê¤¤¤Î¤Ç¡¢
¼ÂºÝ¤Ë¤ÏÊ̤Τâ¤Î¤Ë¤Ê¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
¸å½Ò¤Î¥Þ¥ë¥Á¥É¥í¥Ã¥×¥¢¥É¥ì¥¹½èÍý¤Ë´Ø¤¹¤ëµÄÏÀ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
Æüì¤Ê¾ì¹ç¤È¤·¤Æ¡¢`envelope "Received"' ¤òÀßÄꤹ¤ë¤È
sendmail ·Á¼°¤Î Received ¹Ô¤ò½èÍý¤¹¤ë¤³¤È¤¬²Äǽ¤Ë¤Ê¤ê¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¤¹¤¬¡¢\fI.fetchmailrc\fR ¥Õ¥¡¥¤¥ë¤Ç
`no envelope' ¤ò»È¤Ã¤Æ Received ¤Î½èÍý¤òÆ°ºîÁ´ÂΤÇ̵¸ú¤Ë¤·¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢
ɬ¤º¤·¤âɬÍפϤʤ¤¤Ï¤º¤Ç¤¹¡£
.TP
.\"O .B -Q <prefix>, --qvirtual <prefix>
.B -Q <¥×¥ì¥Õ¥£¥Ã¥¯¥¹>, --qvirtual <¥×¥ì¥Õ¥£¥Ã¥¯¥¹>
.\"O (Keyword: qvirtual)
(¥­¡¼¥ï¡¼¥É: qvirtual)
.\"O The string prefix assigned to this option will be removed from the user
.\"O name found in the header specified with the \fIenvelope\fR option
.\"O (\fIbefore\fR doing multidrop name mapping or localdomain checking,
.\"O if either is applicable). This option is useful if you are using  
.\"O .I fetchmail
.\"O to collect the mail for an entire domain and your ISP (or your mail
.\"O redirection provider) is using qmail.
.\"O One of the basic features of qmail is the
.\"O .sp
.\"O \&`Delivered-To:'
.\"O .sp
.\"O message header.  Whenever qmail delivers a message to a local mailbox
.\"O it puts the username and hostname of the envelope recipient on this
.\"O line.  The major reason for this is to prevent mail loops.  To set up
.\"O qmail to batch mail for a disconnected site the ISP-mailhost will have
.\"O normally put that site in its `Virtualhosts' control file so it will
.\"O add a prefix to all mail addresses for this site. This results in mail
.\"O .\" The \&@\& tries to stop HTML converters from making a mailto URL here.
.\"O sent to 'username\&@\&userhost.userdom.dom.com' having a
.\"O \&`Delivered-To:' line of the form:
.\"O .sp
.\"O Delivered-To: mbox-userstr-username\&@\&userhost.userdom.dom.com
.\"O .sp
.\"O The ISP can make the 'mbox-userstr-' prefix anything they choose
.\"O but a string matching the user host name is likely.
.\"O By using the option `envelope Delivered-To:' you can make fetchmail reliably
.\"O identify the original envelope recipient, but you have to strip the
.\"O `mbox-userstr-' prefix to deliver to the correct user.
.\"O This is what this option is for.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ë³ä¤êÅö¤Æ¤é¤ì¤¿Ê¸»úÎó¥×¥ì¥Õ¥£¥Ã¥¯¥¹¤Ï¡¢
\fIenvelope\fR ¥ª¥×¥·¥ç¥ó¤Ç»ØÄꤵ¤ì¤¿¥Ø¥Ã¥ÀÆâ¤Ç¸«¤Ä¤«¤Ã¤¿
¥æ¡¼¥¶Ì¾¤«¤éºï½ü¤µ¤ì¤Þ¤¹
(¥Þ¥ë¥Á¥É¥í¥Ã¥×¤Î̾Á°¥Þ¥Ã¥Á¥ó¥°¤«
¥í¡¼¥«¥ë¥É¥á¥¤¥ó¤Î¥Á¥§¥Ã¥¯¤Î¤É¤Á¤é¤«¤¬ÍøÍѤǤ­¤ë¾ì¹ç¡¢
¤³¤ì¤é¤ò¹Ô¤¦\fIÁ°\fR¤Ëºï½ü¤¬¹Ô¤ï¤ì¤Þ¤¹)¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï
.I fetchmail
¤ò»È¤Ã¤Æ¥É¥á¥¤¥óÁ´ÂΤΥ᡼¥ë¤ò½¸¤á¤Æ¤¤¤ë¾ì¹ç¤È¡¢
¤ª»È¤¤¤Î ISP (¤Þ¤¿¤Ï¥á¡¼¥ëžÁ÷¥×¥í¥Ð¥¤¥À) ¤¬
qmail ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤ËÊØÍø¤Ç¤¹¡£
qmail ¤Î´ðËܵ¡Ç½¤Î 1 ¤Ä¤Ë
.sp
\&`Delivered-To:'
.sp
¤¬¤¢¤ê¤Þ¤¹¡£
qmail ¤Ï¥í¡¼¥«¥ë¤Î¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤Ë¥á¥Ã¥»¡¼¥¸¤òÇÛ㤹¤ë¤È¤­¤Ë¤Ïɬ¤º¡¢
¥æ¡¼¥¶Ì¾¤È envelope recipient ¤Î¥Û¥¹¥È̾¤ò¤³¤Î¹Ô¤Ë½ñ¤­¤Þ¤¹¡£
¤³¤ì¤Ï¼ç¤Ë¥á¡¼¥ë¤Î¥ë¡¼¥×¤òËɤ°¤¿¤á¤Ë¹Ô¤¤¤Þ¤¹¡£
Àܳ¤µ¤ì¤Æ¤¤¤Ê¤¤¥µ¥¤¥È¤Ë°ì³ç¤Ç¥á¡¼¥ë¤òÁ÷¤ë qmail ¤ÎÀßÄê¤ò¹Ô¤¦¤¿¤á¡¢
ISP ¤Î¥á¡¼¥ë¥Û¥¹¥È¤Ï¤½¤Î¥µ¥¤¥È¤ò
`Virtualhosts' À©¸æ¥Õ¥¡¥¤¥ë¤Ë½ñ¤¤¤Æ¤ª¤¯¤Î¤¬ÉáÄ̤Ǥ¢¤ê¡¢
¤³¤ì¤Ë¤è¤ê¤½¤Î¥µ¥¤¥È°¸¤Î¥á¡¼¥ë¥¢¥É¥ì¥¹Á´¤Æ¤Ë¥×¥ì¥Õ¥£¥Ã¥¯¥¹¤¬Äɲ䵤ì¤Þ¤¹¡£
.\" \&@\& ¤Ï HTML ¥³¥ó¥Ð¡¼¥¿¤¬ mailto URL ¤ò¤³¤³¤Ëºî¤é¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£
¤½¤Î·ë²Ì¡¢'username\&@\&userhost.userdom.dom.com' °¸¤ËÁ÷¤é¤ì¤¿¥á¡¼¥ë¤Î
\&`Delivered-To:' ¹Ô¤Ï°Ê²¼¤Î¤è¤¦¤Ê·Á¤Ë¤Ê¤ê¤Þ¤¹:
.sp
Delivered-To: mbox-userstr-username\&@\&userhost.userdom.dom.com
.sp
ISP ¤Ï 'mbox-userstr-' ¥×¥ì¥Õ¥£¥Ã¥¯¥¹¤ò¼«Í³¤Ë·è¤á¤é¤ì¤Þ¤¹¤¬¡¢
¤è¤¯Áª¤Ð¤ì¤ë¤Î¤Ï¥æ¡¼¥¶¤Î¥Û¥¹¥È̾¤Ë¥Þ¥Ã¥Á¤¹¤ëʸ»úÎó¤Ç¤¹¡£
¥ª¥×¥·¥ç¥ó `envelope Delivered-To:' ¤ò»È¤¦¤³¤È¤Ë¤è¤ê¡¢
fetchmail ¤Ë¸µ¤Î envelope recipient ¤ò¼±Ê̤µ¤»¤ë¤³¤È¤¬°ÂÁ´¤Ë¹Ô¤¨¤Þ¤¹¤¬¡¢
Àµ¤·¤¤¥æ¡¼¥¶¤Ë¥á¡¼¥ë¤òÇÛ㤹¤ë¤Ë¤Ï `mbox-userstr-' ¥×¥ì¥Õ¥£¥Ã¥¯¥¹¤ò
¼è¤ê½ü¤«¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
¤³¤ì¤¬¤³¤Î¥ª¥×¥·¥ç¥ó¤ÎÌÜŪ¤Ç¤¹¡£
.TP
.B --configdump
.\"O Parse the 
.\"O .I ~/.fetchmailrc
.\"O file, interpret any command-line options specified, and dump a
.\"O configuration report to standard output.  The configuration report is
.\"O a data structure assignment in the language Python.  This option
.\"O is meant to be used with an interactive 
.\"O .I ~/.fetchmailrc
.\"O editor like 
.\"O .IR fetchmailconf ,
.\"O written in Python.
.I ~/.fetchmailrc
¤ò½èÍý¤·¡¢»ØÄꤵ¤ì¤¿¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤òÁ´¤Æ²ò¼á¤·¡¢
ɸ½à½ÐÎϤËÀßÄê¾ðÊó¤ò½ÐÎϤ·¤Þ¤¹¡£
ÀßÄê¾ðÊó¤Ï Python ¸À¸ì¤Î¥Ç¡¼¥¿¹½Â¤ÇÛÃ֤ˤʤäƤ¤¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï
.I fetchmailconf
¤Î¤è¤¦¤Ê Python ¤Ç½ñ¤«¤ì¤¿ÂÐÏÃŪ¤Ê
.I ~/.fetchmailrc
¥¨¥Ç¥£¥¿¤È°ì½ï¤Ë»È¤¦¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£

.\"O .SH USER AUTHENTICATION AND ENCRYPTION
.SH ¥æ¡¼¥¶Ç§¾Ú¤È°Å¹æ²½
.\"O All modes except ETRN require authentication of the client.
.\"O Normal user authentication in 
.\"O .I fetchmail
.\"O is very much like the authentication mechanism of 
.\"O .IR ftp (1).
.\"O The correct user-id and password depend upon the underlying security
.\"O system at the mailserver.  
ETRN ¤ò½ü¤¯Á´¤Æ¤Î¥â¡¼¥É¤Ç¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Îǧ¾Ú¤¬É¬ÍפǤ¹¡£
.I fetchmail
¤Ë¤ª¤±¤ëÄ̾ï¤Î¥æ¡¼¥¶Ç§¾Ú¤Ï¡¢
.IR ftp (1)
¤Îǧ¾Úµ¡¹½¤Ë¤è¤¯»÷¤Æ¤¤¤Þ¤¹¡£
Àµ¤·¤¤¥æ¡¼¥¶ ID ¤È¥Ñ¥¹¥ï¡¼¥É¤Ï¡¢
¥á¡¼¥ë¥µ¡¼¥Ð¤ÎÆâÉôŪ¤Ê¥»¥­¥å¥ê¥Æ¥£¥·¥¹¥Æ¥à¤Ë°Í¸¤·¤Þ¤¹¡£
.PP
.\"O If the mailserver is a Unix machine on which you have an ordinary user 
.\"O account, your regular login name and password are used with 
.\"O .I fetchmail.
¥á¡¼¥ë¥µ¡¼¥Ð¤¬¡¢¤¢¤Ê¤¿¤¬Ä̾ï¤Î¥æ¡¼¥¶¥¢¥«¥¦¥ó¥È¤ò»ý¤Ã¤Æ¤¤¤ë Unix ¥Þ¥·¥ó¤Ê¤é¤Ð¡¢
¤¢¤Ê¤¿¤¬¤¤¤Ä¤â»È¤Ã¤Æ¤¤¤ë¥í¥°¥¤¥ó̾¤È¥Ñ¥¹¥ï¡¼¥É¤ò
.I fetchmail
¤Ç¤â»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
.\"O If you use the same login name on both the server and the client machines,
.\"O you needn't worry about specifying a user-id with the 
.\"O .B \-u
.\"O option \-\- 
.\"O the default behavior is to use your login name on the client machine as the 
.\"O user-id on the server machine.  If you use a different login name
.\"O on the server machine, specify that login name with the
.\"O .B \-u
.\"O option.  e.g. if your login name is 'jsmith' on a machine named 'mailgrunt',
.\"O you would start 
.\"O .I fetchmail 
.\"O as follows:
¥µ¡¼¥Ð¤È¥¯¥é¥¤¥¢¥ó¥È¤ÎξÊý¤ÇƱ¤¸¥í¥°¥¤¥ó̾¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¡¢
.B \-u
¥ª¥×¥·¥ç¥ó¤Ç¤ï¤¶¤ï¤¶¥æ¡¼¥¶ ID ¤ò»ØÄꤹ¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£
¤È¤¤¤¦¤Î¤â¡¢¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤Ç¤Ï¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¾å¤Ç¤Î
¥í¥°¥¤¥ó̾¤ò¥µ¡¼¥Ð¥Þ¥·¥ó¤Î¥æ¡¼¥¶ ID ¤È¤·¤Æ»È¤¦¤«¤é¤Ç¤¹¡£
¥µ¡¼¥Ð¥Þ¥·¥ó¤Ç¤ÏÊÌ¤Î¥í¥°¥¤¥ó̾¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
.B \-u
¥ª¥×¥·¥ç¥ó¤Ç¥í¥°¥¤¥ó̾¤ò»ØÄꤷ¤Æ¤¯¤À¤µ¤¤¡£
Î㤨¤Ð¡¢'mailgrunt' ¤È¤¤¤¦Ì¾Á°¤Î¥Þ¥·¥ó¤Ç¤Î¥í¥°¥¤¥ó̾¤¬ 'jsmith' ¤Ç¤¢¤ë¾ì¹ç¡¢
°Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ
.I fetchmail 
¤òµ¯Æ°¤¹¤ë¤³¤È¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦:
.IP
fetchmail -u jsmith mailgrunt
.PP
.\"O The default behavior of 
.\"O .I fetchmail
.\"O is to prompt you for your mailserver password before the connection is
.\"O established.  This is the safest way to use 
.\"O .I fetchmail
.\"O and ensures that your password will not be compromised.  You may also specify
.\"O your password in your
.\"O .I ~/.fetchmailrc
.\"O file.  This is convenient when using 
.\"O .I fetchmail
.\"O in daemon mode or with scripts.
.I fetchmail
¤Î¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤Ç¤Ï¡¢Àܳ¤¬³ÎΩ¤µ¤ì¤ëÁ°¤Ë
¥æ¡¼¥¶¤Ë¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥Ñ¥¹¥ï¡¼¥É¤òÌ䤤¹ç¤ï¤»¤Þ¤¹¡£
¤³¤ì¤ÏºÇ¤â°ÂÁ´¤Ë
.I fetchmail
¤ò»È¤¦ÊýË¡¤Ç¤¢¤ê¡¢¥Ñ¥¹¥ï¡¼¥É¤âÅð¤Þ¤ì¤Ë¤¯¤Ê¤ê¤Þ¤¹¡£
¥Ñ¥¹¥ï¡¼¥É¤Ï
.I ~/.fetchmailrc
¥Õ¥¡¥¤¥ë¤Ç»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
¤³¤ì¤Ï¥Ç¡¼¥â¥ó¥â¡¼¥É¤ä¥¹¥¯¥ê¥×¥È¤Ç
.I fetchmail
¤ò»È¤¦¾ì¹ç¤ËÊØÍø¤Ç¤¹¡£
.PP
.\"O If you do not specify a password, and
.\"O .I fetchmail
.\"O cannot extract one from your
.\"O .I ~/.fetchmailrc
.\"O file, it will look for a 
.\"O .I ~/.netrc
.\"O file in your home directory before requesting one interactively; if an
.\"O entry matching the mailserver is found in that file, the password will
.\"O be used.  Fetchmail first looks for a match on poll name; if it finds none,
.\"O it checks for a match on via name.  See the
.\"O .IR ftp (1)
.\"O man page for details of the syntax of the
.\"O .I ~/.netrc
.\"O file.  (This feature may allow you to avoid duplicating password
.\"O information in more than one file.)
¥Ñ¥¹¥ï¡¼¥É¤ò»ØÄꤵ¤ì¤Æ¤ª¤é¤º¡¢
.I fetchmail
¤¬
.I ~/.fetchmailrc
¥Õ¥¡¥¤¥ë¤«¤é¥Ñ¥¹¥ï¡¼¥É¤òŸ³«¤Ç¤­¤Ê¤«¤Ã¤¿¾ì¹ç¡¢
.I fetchmail
¤ÏÂÐÏÃŪ¤Ë¥Ñ¥¹¥ï¡¼¥É¤òʹ¤¯Á°¤Ë¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Î
.I ~/.netrc
¥Õ¥¡¥¤¥ë¤òõ¤·¤Þ¤¹¡£
¤³¤Î¥Õ¥¡¥¤¥ëÃæ¤Ë¡¢¥æ¡¼¥¶¤Î¥á¡¼¥ë¥µ¡¼¥Ð¤Ë¥Þ¥Ã¥Á¤¹¤ë¥¨¥ó¥È¥ê¤¬¤¢¤Ã¤¿¾ì¹ç¡¢
¤½¤Î¥Ñ¥¹¥ï¡¼¥É¤¬»È¤ï¤ì¤Þ¤¹¡£
fetchmail ¤Ï poll ̾¤Ë¥Þ¥Ã¥Á¤¹¤ë¤â¤Î¤òºÇ½é¤Ëõ¤·¤Þ¤¹¡£
¤³¤ì¤¬¸«¤Ä¤«¤é¤Ê¤±¤ì¤Ð¡¢via ̾¤Ë¥Þ¥Ã¥Á¤¹¤ë¤â¤Î¤ò¥Á¥§¥Ã¥¯¤·¤Þ¤¹¡£
.\"O ¤³¤ÎÉôʬ¤Ï¤á¤Á¤ã¤á¤Á¤ã¤¢¤ä¤·¤¤¤Ã¤¹(^_^;
.I ~/.netrc
¥Õ¥¡¥¤¥ë¤Î¾Ü¤·¤¤Ê¸Ë¡¤Ë¤Ä¤¤¤Æ¤Ï¡¢¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Î
.IR ftp (1)
¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
(¤³¤Îµ¡Ç½¤ò»È¤¦¤È¡¢Ê£¿ô¤Î¥Õ¥¡¥¤¥ë¤Ë¥Ñ¥¹¥ï¡¼¥É¾ðÊó¤¬
ʬ¤«¤ì¤ë¤³¤È¤òÈò¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£)
.PP
.\"O On mailservers that do not provide ordinary user accounts, your user-id and 
.\"O password are usually assigned by the server administrator when you apply for 
.\"O a mailbox on the server.  Contact your server administrator if you don't know 
.\"O the correct user-id and password for your mailbox account.
Ä̾ï¤Î¥æ¡¼¥¶¥¢¥«¥¦¥ó¥È¤òÍ¿¤¨¤Ê¤¤¥á¡¼¥ë¥µ¡¼¥Ð¤Ç¤ÏÉáÄÌ¡¢
¥æ¡¼¥¶ ID ¤È¥Ñ¥¹¥ï¡¼¥É¤Ï¥µ¡¼¥Ð¤Ë¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤òÍ¿¤¨¤ë¤È¤­¤Ë
¥µ¡¼¥Ð¤Î´ÉÍý¼Ô¤¬³ä¤êÅö¤Æ¤Þ¤¹¡£
¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤Î¥¢¥«¥¦¥ó¥ÈÍѤÎÀµ¤·¤¤¥æ¡¼¥¶ ID ¤È¥Ñ¥¹¥ï¡¼¥É¤¬Ê¬¤«¤é¤Ê¤±¤ì¤Ð¡¢
¥µ¡¼¥Ð¤Î´ÉÍý¼Ô¤ËÏ¢Íí¤·¤Þ¤·¤ç¤¦¡£
.PP
.\"O Early versions of POP3 (RFC1081, RFC1225) supported a crude form of
.\"O independent authentication using the
.\"O .I rhosts
.\"O file on the mailserver side.  Under this RPOP variant, a fixed
.\"O per-user ID equivalent to a password was sent in clear over a link to
.\"O a reserved port, with the command RPOP rather than PASS to alert the
.\"O server that it should do special checking.  RPOP is supported
.\"O by
.\"O .I fetchmail
.\"O (you can specify `protocol RPOP' to have the program send `RPOP'
.\"O rather than `PASS') but its use is strongly discouraged.  This
.\"O facility was vulnerable to spoofing and was withdrawn in RFC1460.
¸Å¤¤¥Ð¡¼¥¸¥ç¥ó¤Î POP3 (RFC1081, RFC1225) ¤Ï
¥á¡¼¥ë¥µ¡¼¥Ð¦¤Ç
.I rhosts
¤òÍѤ¤¤ëÂ绨ÇĤʷÁ¼°¤ÎÆȼ«¤Îǧ¾Ú¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤·¤¿¡£
¤³¤Î RPOP ¤ÎÊѼï¤Ç¤Ï¡¢¥Ñ¥¹¥ï¡¼¥É¤ÈƱÅù¤Ç¤¢¤ë¥æ¡¼¥¶¤´¤È¤Î¸ÇÄê ID ¤Ï¡¢
ͽÌó¥Ý¡¼¥È¤È¤ÎÀܳ¾å¤Çʿʸ¤Î¤Þ¤ÞÁ÷¿®¤µ¤ì¤Æ¤¤¤Þ¤·¤¿¡£
¤³¤Î¤È¤­¡¢PASS ¥³¥Þ¥ó¥É¤Ç¤Ê¤¯ RPOP¥³¥Þ¥ó¥É¤ò»È¤Ã¤Æ¡¢
Æüì¤Ê¥Á¥§¥Ã¥¯¤¬É¬Íפʤ³¤È¤ò¥µ¡¼¥Ð¤ËÃΤ餻¤Æ¤¤¤Þ¤·¤¿¡£
.I fetchmail
¤Ï RPOP ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹
(`protocol RPOP' ¤ò»ØÄꤹ¤ë¤È¡¢
fetchmail ¤Ë `PASS' ¤Ç¤Ï¤Ê¤¯ `RPOP' ¤òÁ÷¤é¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹) ¤¬¡¢
¤³¤ì¤Ï»È¤ï¤Ê¤¤¤³¤È¤ò¶¯¤¯¤ª´«¤á¤·¤Þ¤¹¡£
¤³¤Îµ¡Ç½¤ÏÅðÄ°¤Ë¼å¤¤¤¿¤á¡¢RFC1460 ¤Ë¤ª¤¤¤Æºï½ü¤µ¤ì¤Þ¤·¤¿¡£
.PP
.\"O RFC1460 introduced APOP authentication.  In this variant of POP3,
.\"O you register an APOP password on your server host (the program
.\"O to do this with on the server is probably called \fIpopauth\fR(8)).  You
.\"O put the same password in your 
.\"O .I ~/.fetchmailrc
.\"O file.  Each time 
.\"O .I fetchmail
.\"O logs in, it sends a cryptographically secure hash of your password and
.\"O the server greeting time to the server, which can verify it by
.\"O checking its authorization database. 
RFC1460 ¤Ç APOP ǧ¾Ú¤¬Æ³Æþ¤µ¤ì¤Þ¤·¤¿¡£
¤³¤Î POP3 ¤ÎÊѼï¤Ç¤Ï¡¢APOP ¥Ñ¥¹¥ï¡¼¥É¤ò¥µ¡¼¥Ð¥Û¥¹¥È¤ËÅÐÏ¿¤·¤Þ¤¹
(¥µ¡¼¥Ð¾å¤Ç¤³¤ì¤ò¹Ô¤¦¥×¥í¥°¥é¥à¤Ï¡¢
¤¿¤Ö¤ó \fIpopauth\fR(8) ¤È¸Æ¤Ð¤ì¤ë¤â¤Î¤Ç¤¹)¡£
.I ~/.fetchmailrc
¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢¤³¤ì¤ÈƱ¤¸¥Ñ¥¹¥ï¡¼¥É¤ò½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£
.I fetchmail
¤¬¥í¥°¥¤¥ó¤¹¤ë¤¿¤Ó¤Ë¡¢¥Ñ¥¹¥ï¡¼¥É¤È¥µ¡¼¥Ð¤Ë¤ª¤±¤ë¥°¥ê¡¼¥Æ¥£¥ó¥°»þ¹ï¤Î
°Å¹æ³ØŪ¤Ë°ÂÁ´¤Ê¥Ï¥Ã¥·¥åÃͤ¬¥µ¡¼¥Ð¤ËÁ÷¤é¤ì¤Þ¤¹¡£
¤³¤ì¤Ï¡¢Ç§¾Ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥Á¥§¥Ã¥¯¤Ë¤è¤Ã¤Æ¸¡ºº¤Ç¤­¤Þ¤¹¡£
.PP
.\"O If your \fIfetchmail\fR was built with Kerberos support and you specify 
.\"O Kerberos authentication (either with --auth or the \fI.fetchmailrc\fR
.\"O option \fBauthenticate kerberos_v4\fR) it will try to get a Kerberos
.\"O ticket from the mailserver at the start of each query.  Note: if
.\"O either the pollnane or via name is `hesiod', fetchmail will try to use
.\"O Hesiod to look up the mailserver.
¤ª»È¤¤¤Î \fIfetchmail\fR ¤¬ Kerberos ¤Î¥µ¥Ý¡¼¥ÈÉÕ¤­¤Ç¹½ÃÛ¤µ¤ì¤Æ¤ª¤ê¡¢
¤«¤Ä Kerberos ǧ¾Ú¤ò»ØÄê (--auth ¤« \fI.fetchmailrc\fR ¤Ç¤Î
\fBauthenticate kerberos_v4\fR ¥ª¥×¥·¥ç¥ó¤òÍѤ¤¤Þ¤¹) ¤·¤¿¾ì¹ç¡¢
\fIfetchmail\fR ¤ÏÌ䤤¹ç¤ï¤»³«»Ï»þ¤Ë
Ëè²ó Kerberos ¥Á¥±¥Ã¥È¤ò¼èÆÀ¤·¤è¤¦¤È¤·¤Þ¤¹¡£
Ãí°Õ: poll ̾¤« via ̾¤Î¤É¤Á¤é¤«¤¬ `hesiod' ¤Ê¤é¤Ð¡¢
fetchmail ¤Ï¥á¡¼¥ë¥µ¡¼¥Ð¤Î¸¡º÷¤Ë Hesiod ¤ò»È¤ª¤¦¤È¤·¤Þ¤¹¡£
.PP
.\"O If you use POP3 or IMAP with GSSAPI authentication, \fIfetchmail\fR will
.\"O expect the server to have RFC1731- or RFC1734-conformant GSSAPI
.\"O capability, and will use it.  Currently this has only been tested over
.\"O Kerberos V, so you're expected to already have a ticket-granting
.\"O ticket. You may pass a username different from your principal name
.\"O using the standard \fB--user\fR command or by the \fI.fetchmailrc\fR
.\"O option \fBuser\fR.
GSSAPI ǧ¾Ú¤Ë¤è¤ë POP3 ¤ä IMAP ¤ò»È¤¦¾ì¹ç¡¢
\fIfetchmail\fR ¤Ï¥µ¡¼¥Ð¤¬ RFC1731 ¤Þ¤¿¤Ï RFC1734 ¤Ë½àµò¤¹¤ë
GSSAPI µ¡Ç½¤òÈ÷¤¨¤Æ¤¤¤ë¤È²¾Äꤷ¤Æ»ÈÍѤ·¤Þ¤¹¡£
¸½ºß¡¢¤³¤Îµ¡Ç½¤Ï Kerberos V ¾å¤Ç¤·¤«¥Æ¥¹¥È¤µ¤ì¤Æ¤¤¤Ê¤¤¤Î¤Ç¡¢
´û¤Ë tiket-granting ¥Á¥±¥Ã¥È¤ò»ý¤Ã¤Æ¤¤¤ë¤³¤È¤ò²¾Äꤷ¤Þ¤¹¡£
ɸ½à¤Î \fB--user\fR ¥³¥Þ¥ó¥É¤ä \fI.fetchmailrc\fR ¤Î \fBuser\fR ¥ª¥×¥·¥ç¥ó¤ò
»È¤Ã¤Æ¡¢¼ç¤Ë»È¤Ã¤Æ¤¤¤ë̾Á°¤È¤ÏÊ̤Υ桼¥¶Ì¾¤òÅϤ¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.\"O Kerberos ÍѸì¤ÏÁ´ÌǾõÂÖ¡Ä(^_^;
.PP
.\"O If your IMAP daemon returns the PREAUTH response in its greeting line, 
.\"O fetchmail will notice this and skip the normal authentication step.
.\"O This can be useful, e.g. if you start imapd explicitly using ssh.
.\"O In this case you can declare the authentication value `ssh' on that
.\"O site entry to stop \fI.fetchmail\fR from asking you for a password
.\"O when it starts up.
¤ª»È¤¤¤Î IMAP ¥Ç¡¼¥â¥ó¤¬¥°¥ê¡¼¥Æ¥£¥ó¥°¹Ô¤Ç
PREAUTH ¥ì¥¹¥Ý¥ó¥¹¤òÊÖ¤·¤¿¾ì¹ç¤Ë¤Ï¡¢
fetchmail ¤Ï¤³¤ì¤òÄÌÃΤ·¤Æ¡¢Ä̾ï¤Îǧ¾Ú¼ê½ç¤òÈô¤Ð¤·¤Þ¤¹¡£
¤³¤ì¤ÏÎ㤨¤Ð ssh ¤òÌÀ¼¨Åª¤ËÍѤ¤¤Æ imapd ¤òµ¯Æ°¤·¤Æ¤¤¤ë¾ì¹ç¤Ê¤É¤ËÊØÍø¤Ç¤¹¡£
¤³¤Î¾ì¹ç¡¢\fIfetchmail\fR ¤¬µ¯Æ°¤·¤¿¤È¤­¤Ë
¥Ñ¥¹¥ï¡¼¥É¤òÌ䤤¹ç¤ï¤»¤ë¤Î¤ò»ß¤á¤µ¤»¤ë¤¿¤á¤Ë¡¢
¤½¤Î¥µ¥¤¥È¤Ç¤Îǧ¾Ú¤ÎÃÍ `ssh' ¤òÀë¸À¤Ç¤­¤Þ¤¹¡£
.PP
.\"O If you are using POP3, and the server issues a one-time-password
.\"O challenge conforming to RFC1938, \fIfetchmail\fR will use your
.\"O password as a pass phrase to generate the required response. This
.\"O avoids sending secrets over the net unencrypted.
POP3 ¤ò»È¤¦¾ì¹ç¤Ë¤Ï¡¢¥µ¡¼¥Ð¤Ï RFC1938 ½àµò¤Î
»È¤¤¼Î¤Æ¥Ñ¥¹¥ï¡¼¥É¤Î¥Á¥ã¥ì¥ó¥¸Ê¸»úÎó¤òȯ¹Ô¤·¡¢
\fIfetchmail\fR ¤Ï¥æ¡¼¥¶¤Î¥Ñ¥¹¥ï¡¼¥É¤ò¥Ñ¥¹¥Õ¥ì¡¼¥º¤È¤·¤Æ»È¤Ã¤Æ¡¢
ɬÍפȤµ¤ì¤ë¥ì¥¹¥Ý¥ó¥¹Ê¸»úÎó¤òÀ¸À®¤·¤Þ¤¹¡£
¤³¤ì¤Ë¤è¤ê¡¢¥Í¥Ã¥È¥ï¡¼¥¯¾å¤Ë
°Å¹æ²½¤µ¤ì¤Æ¤¤¤Ê¤¤µ¡Ì©¾ðÊó¤òή¤¹¤³¤È¤òÈò¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.PP
.\"O Compuserve's RPA authentication (similar to APOP) is supported. If you
.\"O compile in the support, \fIfetchmail\fR will try to perform an RPA pass-phrase
.\"O authentication instead of sending over the password en clair if it
.\"O detects "@compuserve.com" in the hostname.
Compuserve ¤Î RPA ǧ¾Ú (APOP ¤Ë»÷¤Æ¤¤¤Þ¤¹) ¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
¤³¤Î¥µ¥Ý¡¼¥È¤òÁȤ߹þ¤ó¤Ç¤¤¤ë¾ì¹ç¡¢
¥Û¥¹¥È̾¤ÎÃæ¤Ë "@compuserve.com" ¤¬¸«¤Ä¤«¤ë¤È¡¢
\fIfetchmail\fR ¤Ï¥Ñ¥¹¥ï¡¼¥É¤òʿʸ¤ÇÁ÷¤é¤º¡¢
RPA ¥Ñ¥¹¥Õ¥ì¡¼¥º¤òÍѤ¤¤¿Ç§¾Ú¤ò¼Â¹Ô¤·¤è¤¦¤È¤·¤Þ¤¹¡£
.PP
.\"O If you are using IMAP, Microsoft's NTLM authentication (used by Microsoft
.\"O Exchange) is supported. If you compile in the support, \fIfetchmail\fR
.\"O will try to perform an NTLM authentication (instead of sending over the
.\"O password en clair) whenever the server returns AUTH=NTLM in its
.\"O capability response. Specify a user option value that looks like
.\"O `user@domain': the part to the left of the @ will be passed as the
.\"O username and the part to the right as the NTLM domain.
IMAP ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¡¢
(Microsoft Exchange ¤¬»È¤¦) Microsoft ¤Î NTLM ǧ¾Ú ¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Þ¤¹¡£
¤³¤Î¥µ¥Ý¡¼¥È¤òÁȤ߹þ¤ó¤Ç¤¤¤ë¾ì¹ç¡¢¥µ¡¼¥Ð¤¬µ¡Ç½¤ò¼¨¤¹±þÅú¤Ç
¡ÖAUTH=NTLM¡×¤òÊÖ¤¹¤È¡¢\fIfetchmail\fR ¤Ï (¥Ñ¥¹¥ï¡¼¥É¤òʿʸ¤ÇÁ÷¤é¤Ê¤¤¤Ç)
NTLM ǧ¾Ú¤ò¼Â¹Ô¤·¤è¤¦¤È¤·¤Þ¤¹¡£
¡Ö¥æ¡¼¥¶Ì¾@¥É¥á¥¤¥ó̾¡×¤Î·Á¤Ç user ¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Æ¤¯¤À¤µ¤¤:
¡Ö@¡×¤Îº¸¤ÎÉôʬ¤Ï¥æ¡¼¥¶Ì¾¤È¤·¤ÆÅϤµ¤ì¡¢
¡Ö@¡×¤Î±¦¤ÎÉôʬ¤Ï NTLM ¥É¥á¥¤¥ó¤È¤·¤ÆÅϤµ¤ì¤Þ¤¹¡£
.PP
.\"O If you are using IPsec, the -T (--netsec) option can be used to pass
.\"O an IP security request to be used when outgoing IP connections are
.\"O initialized.  You can also do this using the `netsec' server option
.\"O in the .fetchmailrc file.  In either case, the option value is a
.\"O string in the format accepted by the net_security_strtorequest() 
.\"O function of the inet6_apps library.
IPsec ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢-T (--netsec) ¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢
³°¸þ¤­¤Î IP Àܳ¤¬½é´ü²½¤µ¤ì¤ë¤È¤­¤Ë»È¤ï¤ì¤ë
IP ¥»¥­¥å¥ê¥Æ¥£¥ê¥¯¥¨¥¹¥È¤òÅϤ¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤ì¤Ï .fetchmailrc ¥Õ¥¡¥¤¥ë¤Ç `netsec' ¥µ¡¼¥Ð¥ª¥×¥·¥ç¥ó¤ò
»È¤Ã¤Æ¹Ô¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
¤É¤Á¤é¤Î¾ì¹ç¤Ç¤â¡¢¥ª¥×¥·¥ç¥ó¤ÎÃͤÏ
inet6_apps ¥é¥¤¥Ö¥é¥ê¤Î net_security_strtorequest() ´Ø¿ô¤¬¼õ¤±ÉÕ¤±¤ë
¥Õ¥©¡¼¥Þ¥Ã¥È¤Îʸ»úÎó¤Ç¤¹¡£
.PP
.\"O You can access SSL encrypted services by specifying the --ssl option.
--ssl ¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È SSL ¤Ç°Å¹æ²½¤µ¤ì¤¿¥µ¡¼¥Ó¥¹¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤Þ¤¹¡£
.\"O You can also do this using the "ssl" server option in the .fetchmailrc
.\"O file.  With SSL encryption enabled, queries are initiated over a connection
.\"O after negotiating an SSL session.  Some services, such as POP3 and IMAP,
.\"O have different well known ports defined for the SSL encrypted services.
¤³¤ì¤Ï .fetchmailrc ¥Õ¥¡¥¤¥ë¤Ç "ssl" ¥µ¡¼¥Ð¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¤â¹Ô¤¨¤Þ¤¹¡£
SSL ¤Ë¤è¤ë°Å¹æ²½¤òÍ­¸ú¤Ë¤¹¤ë¤È¡¢
SSL ¥»¥Ã¥·¥ç¥ó¤ÎÄ´Ää¤Î¸å¤Ë SSL Àܳ¾å¤ÇÌ䤤¹ç¤ï¤»¤¬¹Ô¤ï¤ì¤Þ¤¹¡£
POP3 ¤ä IMAP ¤È¤¤¤Ã¤¿°ìÉô¤Î¥µ¡¼¥Ó¥¹¤Ç¤Ï¡¢
SSL ¤Ë¤è¤ë°Å¹æ²½¥µ¡¼¥Ó¥¹¤Î¤¿¤á¤Ëɸ½à¥×¥í¥È¥³¥ë¤È¤ÏÊ̤Ë
´ûÃΤΥݡ¼¥È¤¬ÄêµÁ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
.\"O The encrypted ports will be selected automatically when SSL is enabled and
.\"O no explicit port is specified.
SSL ¤¬Í­¸ú¤Ë¤µ¤ì¤Æ¤ª¤ê¡¢¤«¤ÄÌÀ¼¨Åª¤Ë¥Ý¡¼¥È¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢
°Å¹æ²½ÄÌ¿®¤Î¥Ý¡¼¥È¤Ï¼«Æ°Åª¤ËÁªÂò¤µ¤ì¤Þ¤¹¡£
.PP
.\"O When connecting to an SSL encrypted server, the server presents a certificate
.\"O to the client for validation.  The certificate is checked to verify that
.\"O the common name in the certificate matches the name of the server being
.\"O contacted and that the effective and expiration dates in the certificate
.\"O indicate that it is currently valid.  If any of these checks fail, a warning
.\"O message is printed, but the connection continues.  The server certificate
.\"O does not need to be signed by any specific Certifying Authority and may
.\"O be a "self-signed" certificate.
SSL ¤Ë¤è¤ë°Å¹æ²½¤ò¹Ô¤¦¥µ¡¼¥Ð¤ËÀܳ¤¹¤ë¤È¤­¡¢
¥µ¡¼¥Ð¤Ï¿È¸µ³Îǧ¤Î¤¿¤á¤Ë¥¯¥é¥¤¥¢¥ó¥È¤Ë¾ÚÌÀ½ñ¤ò¼¨¤·¤Þ¤¹¡£
¾ÚÌÀ½ñ¤Ï¥Á¥§¥Ã¥¯¤µ¤ì¡¢Àܳ¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¥µ¡¼¥Ð¤Î̾Á°¤¬
¾ÚÌÀ½ñ¤ÎÃæ¤Îɸ½à̾¤È°ìÃפ¹¤ë¤³¤È¤È¡¢
¾ÚÌÀ½ñ¤Ë½ñ¤«¤ì¤Æ¤¤¤ëÍ­¸ú´ü¸Â¤Ë¤è¤ë¤È
¸½ºß¾ÚÌÀ½ñ¤¬Í­¸ú¤Ç¤¢¤ë¤³¤È¤¬³Î¤«¤á¤é¤ì¤Þ¤¹¡£
¤É¤Á¤é¤«¤Î¥Á¥§¥Ã¥¯¤¬¼ºÇÔ¤¹¤ë¤È·Ù¹ð¥á¥Ã¥»¡¼¥¸¤¬É½¼¨¤µ¤ì¤Þ¤¹¤¬¡¢
Àܳ¤Ï·Ñ³¤µ¤ì¤Þ¤¹¡£
¥µ¡¼¥Ð¤Î¾ÚÌÀ½ñ¤ÏÆÃÄê¤Îǧ¾Úµ¡´Ø (CA, Certification Authority) ¤Ë¤è¤Ã¤Æ
½ð̾¤µ¤ì¤Æ¤¤¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¤·¡¢
¡Ö¼«Ê¬¤Ç½ð̾¤·¤¿¡×¾ÚÌÀ½ñ¤Ç¤¢¤Ã¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó¡£
.PP
.\"O Some SSL encrypted servers may request a client side certificate.  A client
.\"O side public SSL certificate and private SSL key may be specified.  If
.\"O requested by the server, the client certificate is sent to the server for
.\"O validation.  Some servers may require a valid client certificate and may
.\"O refuse connections if a certificate is not provided or if the certificate
.\"O is not valid.  Some servers may require client side certificates be signed
.\"O by a recognized Certifying Authority.  The format for the key files and
.\"O the certificate files is that required by the underlying SSL libraries
.\"O (OpenSSL in the general case).
SSL ¤Ë¤è¤ë°Å¹æ²½¤ò¹Ô¤¦¥µ¡¼¥Ð¤Ë¤è¤Ã¤Æ¤Ï¡¢
¥¯¥é¥¤¥¢¥ó¥È¦¤Î¾ÚÌÀ½ñ¤òÍ׵᤹¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
¥¯¥é¥¤¥¢¥ó¥È¦¤Î¸ø³« SSL ¾ÚÌÀ½ñ¤ÈÈëÌ© SSL ¸°¤ò»ØÄê¤Ç¤­¤Þ¤¹¡£
¥µ¡¼¥Ð¤¬¾ÚÌÀ½ñ¤òÍ׵ᤷ¤¿¤é¡¢¥¯¥é¥¤¥¢¥ó¥È¤Î¾ÚÌÀ½ñ¤Ï
¿È¸µ³Îǧ¤Î¤¿¤á¤Ë¥µ¡¼¥Ð¤ËÁ÷¤é¤ì¤Þ¤¹¡£
¥µ¡¼¥Ð¤Ë¤è¤Ã¤Æ¤ÏÀµÅö¤Ê¥¯¥é¥¤¥¢¥ó¥È¤Î¾ÚÌÀ½ñ¤òÍ׵ᤷ¡¢
¾ÚÌÀ½ñ¤¬Á÷¤é¤ì¤Ê¤¤¤«ÀµÅö¤Ç¤Ê¤±¤ì¤ÐÀܳ¤òµñÈݤ¹¤ë¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
¥µ¡¼¥Ð¤Ë¤è¤Ã¤Æ¤Ï¡¢Ç§¤á¤é¤ì¤Æ¤¤¤ëǧ¾Úµ¡´Ø¤è¤ë½ð̾¤¬
¥¯¥é¥¤¥¢¥ó¥È¦¤Î¾ÚÌÀ½ñ¤Ë¤Ê¤µ¤ì¤Æ¤¤¤ë¤³¤È¤¬É¬Íפʤâ¤Î¤â¤¢¤ê¤Þ¤¹¡£
¸°¥Õ¥¡¥¤¥ë¤È¾ÚÌÀ½ñ¥Õ¥¡¥¤¥ë¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï¡¢
ÆâÉôŪ¤ËÆ°ºî¤·¤Æ¤¤¤ë SSL ¥é¥¤¥Ö¥é¥ê¤¬É¬ÍפȤ¹¤ë·Á¼°
(°ìÈÌŪ¤Ë¤Ï OpenSSL) ¤Ç¤¹¡£
.PP
.\"O Finally, a word of care about the use of SSL: While above mentioned
.\"O setup with self-signed server certificates retrieved over the wires
.\"O can protect you from a passive eavesdropper it doesn't help against an
.\"O active attacker. It's clearly an improvement over sending the
.\"O passwords in clear but you should be aware that a man-in-the-middle
.\"O attack is trivially possible (in particular with tools such as dsniff,
.\"O http://www.monkey.org/~dugsong/dsniff/).  Use of an ssh tunnel (see
.\"O below for some examples) is preferable if you care seriously about the
.\"O security of your mailbox.
ºÇ¸å¤Ë¡¢SSL ¤Î»ÈÍѤˤĤ¤¤ÆÃí°Õ½ñ¤­¤ò¤·¤Þ¤¹ :
¥Í¥Ã¥È¥ï¡¼¥¯±Û¤·¤Ë¼«Ê¬¤Ç½ð̾¤·¤¿¥µ¡¼¥Ð¤Î¾ÚÌÀ½ñ¤ò¼èÆÀ¤¹¤ë¤È¤¤¤¦
¾å¤Ç½Ò¤Ù¤¿¤è¤¦¤ÊÀßÄê¤Ç¤Ï¡¢
¾Ã¶ËŪ¤ÊÅð¤ßʹ¤­¤ò¤¹¤ëÁê¼ê¤«¤é¤Ï¼é¤ì¤Þ¤¹¤¬¡¢
ÀѶËŪ¤Ë¹¶·â¤·¤Æ¤¯¤ëÁê¼ê¤«¤é¼é¤ë¤¿¤á¤Î½õ¤±¤Ë¤Ï¤Ê¤ê¤Þ¤»¤ó¡£
¥Ñ¥¹¥ï¡¼¥É¤òʿʸ¤ÇÁ÷¤ë¤Î¤ËÈæ¤Ù¤ì¤Ð¡¢¤«¤Ê¤ê²þÁ±¤µ¤ì¤Þ¤¹¤¬¡¢
Ãæ·ÑÅÀ¤Ë¤¤¤ëÁê¼ê¤«¤é¤Î¹¶·â¤Ï
(http://www.monkey.org/~dugsong/dsniff/ ¤Ë¤¢¤ë
dsniff ¤Î¤è¤¦¤Ê¥Ä¡¼¥ë¤ò»È¤¦¤ÈÆäË)
´Êñ¤Ë²Äǽ¤Ç¤¢¤ë¤³¤È¤òÃΤäƤª¤«¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
¼«Ê¬¤Î¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤Î¥»¥­¥å¥ê¥Æ¥£¤ò¿¿·õ¤Ë¹Í¤¨¤ë¤Ê¤é¡¢
ssh ¥È¥ó¥Í¥ë (²¼µ­¤ÎÎã¤ò»²¾È) ¤ò¤ª´«¤á¤·¤Þ¤¹¡£

.\"O .SH DAEMON MODE
.SH ¥Ç¡¼¥â¥ó¥â¡¼¥É
.\"O The 
.\"O .B --daemon <interval>
.\"O or
.\"O .B -d <interval>
.\"O option runs 
.\"O .I fetchmail
.\"O in daemon mode.  You must specify a numeric argument which is a
.\"O polling interval in seconds.
.B --daemon <´Ö³Ö>
¤Þ¤¿¤Ï
.B -d <´Ö³Ö>
¤ò»È¤¦¤È
.I fetchmail
¤ò¥Ç¡¼¥â¥ó¥â¡¼¥É¤Ç¼Â¹Ô¤Ç¤­¤Þ¤¹¡£
°ú¤­¿ô¤È¤·¤Æ¡¢¥Ý¡¼¥ê¥ó¥°¤Î»þ´Ö´Ö³Ö¤òÉÿô¤Ç»ØÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.PP
.\"O In daemon mode, 
.\"O .I fetchmail
.\"O puts itself in background and runs forever, querying each specified
.\"O host and then sleeping for the given polling interval.
¥Ç¡¼¥â¥ó¥â¡¼¥É¤Ç¤Ï¡¢
.I fetchmail
¤Ï¼«Ê¬¼«¿È¤ò¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤Ç¤º¤Ã¤ÈÆ°ºî¤µ¤»¤Þ¤¹¡£
¤Ä¤Þ¤ê¡¢»ØÄꤵ¤ì¤¿³Æ¥Û¥¹¥È¤Ø¤ÎÌ䤤¹ç¤ï¤»¤È¡¢
»ØÄꤵ¤ì¤¿»þ´Ö¤Î¥¹¥ê¡¼¥×¤ò·«¤êÊÖ¤·¤Þ¤¹¡£
.PP
.\"O Simply invoking
.\"O .IP
.\"O fetchmail -d 900
.\"O .PP
.\"O will, therefore, poll all the hosts described in your 
.\"O .I ~/.fetchmailrc
.\"O file (except those explicitly excluded with the `skip' verb) once
.\"O every fifteen minutes.
¤·¤¿¤¬¤Ã¤Æ¡¢Ã±¤Ë
.IP
fetchmail -d 900
.PP
¤ò¼Â¹Ô¤¹¤ë¤È¡¢
.I ~/.fetchmailrc
¤Ëµ­½Ò¤µ¤ì¤¿Á´¤Æ¤Î¥Û¥¹¥È
(¥­¡¼¥ï¡¼¥É `skip' ¤ÇÌÀ¼¨Åª¤Ë½ü³°¤µ¤ì¤¿¥Û¥¹¥È¤Ï½ü¤­¤Þ¤¹) ¤ËÂФ·¤Æ
15 ʬ¤´¤È¤Ë 1 ²ó¥Ý¡¼¥ê¥ó¥°¤ò¹Ô¤¤¤Þ¤¹¡£
.PP
.\"O It is possible to set a polling interval 
.\"O in your
.\"O .I ~/.fetchmailrc
.\"O file by saying `set daemon <interval>', where <interval> is an
.\"O integer number of seconds.  If you do this, fetchmail will always
.\"O start in daemon mode unless you override it with the command-line
.\"O option --daemon 0 or -d0.
`set daemon <interval>' ¤ò
.I ~/.fetchmailrc
¥Õ¥¡¥¤¥ë¤Ë½ñ¤¯¤³¤È¤Ç¥Ý¡¼¥ê¥ó¥°´Ö³Ö¤òÀßÄꤹ¤ë¤³¤È¤¬²Äǽ¤Ç¤¹¡£
¤³¤³¤Ç¡¢<interval> ¤ÏÉÿô¤òɽ¤¹À°¿ôÃͤǤ¹¡£
¤³¤ì¤ò¹Ô¤¦¤È¡¢¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤Î
--daemon 0 ¤Þ¤¿¤Ï -d0 ¤Ç¾å½ñ¤­¤·¤Ê¤¤¸Â¤ê¡¢
fetchmail ¤Ïɬ¤º¥Ç¡¼¥â¥ó¥â¡¼¥É¤Çµ¯Æ°¤·¤Þ¤¹¡£
.PP
.\"O Only one daemon process is permitted per user; in daemon mode,
.\"O .I fetchmail
.\"O makes a per-user lockfile to guarantee this.
¥æ¡¼¥¶¤¢¤¿¤ê 1 ¤Ä¤Î¥Ç¡¼¥â¥ó¥×¥í¥»¥¹¤·¤«µö¤µ¤ì¤Þ¤»¤ó¡£
¥Ç¡¼¥â¥ó¥â¡¼¥É¤Ç¤Ï¡¢
.I fetchmail
¤Ï¥æ¡¼¥¶Ã±°Ì¤Î¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¤Æ¤³¤ì¤òÊݾڤ·¤Þ¤¹¡£
.PP
.\"O Normally, calling fetchmail with a daemon in the background sends a
.\"O wakeup signal to the daemon, forcing it to poll mailservers
.\"O immediately.  (The wakeup signal is SIGHUP if fetchmail is running as
.\"O root, SIGUSR1 otherwise.)  The wakeup action also clears any `wedged'
.\"O flags indicating that connections have wedged due to failed 
.\"O authentication or multiple timeouts.
Ä̾ï¤Ï¡¢¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤Ç¥Ç¡¼¥â¥ó¤òÆ°ºî¤·¤Æ¤¤¤ë»þ¤Ë fetchmail ¤ò¸Æ¤Ó½Ð¤¹¤È¡¢
¥Ç¡¼¥â¥ó¤ËÂФ·¤Æµ¯Æ°¤Î¥·¥°¥Ê¥ë¤òÁ÷¿®¤·¡¢
¨ºÂ¤Ë¥á¡¼¥ë¥µ¡¼¥Ð¤Ë¥Ý¡¼¥ê¥ó¥°¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
(fatchmali ¤ò root ¤Ç¼Â¹Ô¤·¤Æ¤¤¤ì¤Ðµ¯Æ°¥·¥°¥Ê¥ë¤Ï SIGHUP ¤Ç¡¢
¤½¤ì°Ê³°¤Î¥æ¡¼¥¶¤Ç¤¢¤ì¤Ð SIGUSR1 ¤Ç¤¹¡£)
µ¯Æ°¤ÎÆ°ºî¤Ç¤Ï¡¢Ç§¾Ú¤Î¼ºÇÔ¤äÊ£¿ô²ó¤Î¥¿¥¤¥à¥¢¥¦¥È¤Ë¤è¤Ã¤Æ
Àܳ¤¬¡Ö»É¤µ¤Ã¤Æ¤¤¤ë¡×¤³¤È¤ò¼¨¤¹¥Õ¥é¥°¤¬Á´¤Æ¥¯¥ê¥¢¤µ¤ì¤Þ¤¹¡£
.PP
.\"O The option
.\"O .B --quit
.\"O will kill a running daemon process instead of waking it up (if there
.\"O is no such process,
.\"O .I fetchmail
.\"O notifies you).  If the --quit option is the only command-line option,
.\"O that's all there is to it.
¥ª¥×¥·¥ç¥ó
.B --quit
¤Ï¡¢¥Ç¡¼¥â¥ó¤òµ¯Æ°¤µ¤»¤ë¤Î¤Ç¤Ï¤Ê¤¯¡¢Æ°ºî¤·¤Æ¤¤¤ë¥Ç¡¼¥â¥ó¤ò»¦¤·¤Þ¤¹
(¤½¤Î¤è¤¦¤Ê¥×¥í¥»¥¹¤¬Ìµ¤±¤ì¤Ð
.I fetchmail
¤¬ÃΤ餻¤Æ¤¯¤ì¤Þ¤¹)¡£
--quit ¥ª¥×¥·¥ç¥ó¤¬Í£°ì¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤Ê¤é¤Ð¡¢
¤³¤ÎÆ°ºî¤À¤±¤ò¹Ô¤¤¤Þ¤¹¡£
.PP
.\"O The quit option may also be mixed with other command-line options; its
.\"O effect is to kill any running daemon before doing what the other
.\"O options specify in combination with the rc file.
quit ¥ª¥×¥·¥ç¥ó¤Ï¾¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤È°ì½ï¤Ë»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
¤³¤Î¾ì¹ç¤ÎÆ°ºî¤È¤·¤Æ¤Ï¡¢Â¾¤Î¥ª¥×¥·¥ç¥ó¤È¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë¤òÁȤ߹ç¤ï¤»¤Æ
»ØÄꤵ¤ì¤Æ¤¤¤ë¤³¤È¤ò¹Ô¤¦Á°¤Ë¡¢Æ°ºî¤·¤Æ¤¤¤ë¥Ç¡¼¥â¥ó¤òÁ´¤Æ»¦¤·¤Þ¤¹¡£
.PP
.\"O The
.\"O .B -L <filename>
.\"O or
.\"O .B --logfile <filename>
.\"O option (keyword: set logfile) allows you to redirect status messages
.\"O emitted while detached into a specified logfile (follow the
.\"O option with the logfile name).  The logfile is opened for append, so
.\"O previous messages aren't deleted.  This is primarily useful for
.\"O debugging configurations.
.B -L <¥Õ¥¡¥¤¥ë̾>
¤Þ¤¿¤Ï
.B --logfile <¥Õ¥¡¥¤¥ë̾>
¥ª¥×¥·¥ç¥ó (¥­¡¼¥ï¡¼¥É: set logfile) ¤ò»È¤¦¤È¡¢
üËö¤ÈÀÚ¤êÎ¥¤µ¤ì¤Æ¤¤¤ë´Ö¤ËȯÀ¸¤·¤¿¾õÂÖ¥á¥Ã¥»¡¼¥¸¤ò¡¢
»ØÄꤵ¤ì¤¿¥í¥°¥Õ¥¡¥¤¥ë (¥ª¥×¥·¥ç¥ó¤Î¸å¤Ë¥í¥°¥Õ¥¡¥¤¥ë̾¤ò³¤±¤Æ¤¯¤À¤µ¤¤) ¤Ë
¥ê¥À¥¤¥ì¥¯¥È¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¥í¥°¥Õ¥¡¥¤¥ë¤ÏÄɲå⡼¥É¤Ç¥ª¡¼¥×¥ó¤µ¤ì¤ë¤Î¤Ç¡¢
°ÊÁ°¤Î¥á¥Ã¥»¡¼¥¸¤Ïºï½ü¤µ¤ì¤Þ¤»¤ó¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¼ç¤Ë¥Ç¥Ð¥Ã¥°ÍѤÎÀßÄê¤Î¾ì¹ç¤ËÌò¤ËΩ¤Á¤Þ¤¹¡£
.PP
.\"O The
.\"O .B --syslog
.\"O option (keyword: set syslog) allows you to redirect status and error
.\"O messages emitted to the
.\"O .IR syslog (3)
.\"O system daemon if available.
.B --syslog
¥ª¥×¥·¥ç¥ó (¥­¡¼¥ï¡¼¥É: set syslog) ¤ò»È¤¦¤È¡¢
²Äǽ¤Ç¤¢¤ì¤Ð¡¢È¯À¸¤·¤¿¾õÂÖ¥á¥Ã¥»¡¼¥¸¤È¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤ò
.IR syslog (3)
¥·¥¹¥Æ¥à¥Ç¡¼¥â¥ó¤ËÁ÷¤ê¤Þ¤¹¡£
.\"O Messages are logged with an id of \fBfetchmail\fR, the facility \fBLOG_MAIL\fR,
.\"O and priorities \fBLOG_ERR\fR, \fBLOG_ALERT\fR or \fBLOG_INFO\fR.
.\"O This option is intended for logging status and error messages which
.\"O indicate the status of the daemon and the results while fetching mail
.\"O from the server(s).
¥á¥Ã¥»¡¼¥¸¤Ï \fBfetchmail\fR ¤Î ID, \fBLOG_MAIL\fR ¤Îµ¡Ç½¡¢
\fBLOG_ERR\fR, \fBLOG_ALERT\fR, \fBLOG_INFO\fR
¤¤¤º¤ì¤«¤ÎÍ¥ÀèÅ٤Ȱì½ï¤Ëµ­Ï¿¤µ¤ì¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢¥µ¡¼¥Ð¤«¤é¥á¡¼¥ë¤ò¼èÆÀ¤·¤Æ¤¤¤ë´Ö¤Î¥Ç¡¼¥â¥ó¤Î¾õÂÖ¤È
·ë²Ì¤ò¼¨¤¹¾õÂÖ¥á¥Ã¥»¡¼¥¸¤È¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤òµ­Ï¿¤¹¤ë¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£
.\"O Error messages for command line options and parsing the \fI.fetchmailrc\fR
.\"O file are still written to stderr, or to the specified log file.
¤³¤Î¾ì¹ç¤Ç¤â¡¢¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤È \fI.fetchmailrc\fR ¤Î½èÍý¤ËÂФ¹¤ë
¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Ïɸ½à¥¨¥é¡¼½ÐÎϤ«»ØÄꤵ¤ì¤¿¥í¥°¥Õ¥¡¥¤¥ë¤Ë½ñ¤«¤ì¤Þ¤¹¡£
.\"O The
.\"O .B --nosyslog
.\"O option turns off use of 
.\"O .IR syslog (3),
.\"O assuming it's turned on in the 
.\"O .I ~/.fetchmailrc  
.\"O file, or that the
.\"O .B -L
.\"O or
.\"O .B --logfile <file>
.\"O option was used.
.B --nosyslog
¥ª¥×¥·¥ç¥ó¤Ï¡¢¤³¤ì¤¬
.I ~/.fetchmailrc 
Æâ¤ÇÍ­¸ú¤Ë¤µ¤ì¤Æ¤¤¤ë¤«¡¢
.B -L <¥Õ¥¡¥¤¥ë̾>
¤Þ¤¿¤Ï
.B --logfile <¥Õ¥¡¥¤¥ë̾>
¥ª¥×¥·¥ç¥ó¤¬»È¤ï¤ì¤Æ¤¤¤ë¤â¤Î¤È¤·¤Æ
.IR syslog (3)
¤Î»ÈÍѤò̵¸ú¤Ë¤·¤Þ¤¹¡£
.PP
.\"O The 
.\"O .B \-N
.\"O or --nodetach option suppresses backgrounding and detachment of the
.\"O daemon process from its control terminal.  This is primarily useful
.\"O for debugging.  Note that this also causes the logfile option to be
.\"O ignored (though perhaps it shouldn't).
.B \-N
¤Þ¤¿¤Ï
--nodetach
¥ª¥×¥·¥ç¥ó¤Ï¡¢¥Ç¡¼¥â¥ó¥×¥í¥»¥¹¤ÎÀ©¸æüËö¤«¤é¤Î
¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É²½¤äÀÚ¤êÎ¥¤·¤ò»ß¤á¤Þ¤¹¡£
¤³¤ì¤Ï¼ç¤Ë¥Ç¥Ð¥Ã¥°»þ¤ËÍ­¸ú¤Ç¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï logfile ¥ª¥×¥·¥ç¥ó¤â̵¸ú¤Ë¤·¤Æ¤·¤Þ¤¦ÅÀ¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤
(¤¿¤Ö¤ó¤³¤ì¤Ç¤Ï¤¤¤±¤Ê¤¤¤Î¤Ç¤¹¤¬)¡£
.PP
.\"O Note that while running in daemon mode polling a POP2 or IMAP2bis server,
.\"O transient errors (such as DNS failures or sendmail delivery refusals)
.\"O may force the fetchall option on for the duration of the next polling
.\"O cycle.  This is a robustness feature.  It means that if a message is
.\"O fetched (and thus marked seen by the mailserver) but not delivered
.\"O locally due to some transient error, it will be re-fetched during the
.\"O next poll cycle.  (The IMAP logic doesn't delete messages until
.\"O they're delivered, so this problem does not arise.)
¥Ç¡¼¥â¥ó¥â¡¼¥É¤ÇÆ°ºî¤·¤Æ POP2 ¤ä IMAP2bis ¥µ¡¼¥Ð¤ËÂФ·¤Æ
¥Ý¡¼¥ê¥ó¥°¤·¤Æ¤¤¤ë»þ¤Ë¤Ï¡¢
°ì»þŪ¥¨¥é¡¼ (DNS »²¾È¼ºÇÔ¤ä sendmail ¤ÎÇÛÁ÷µñÈݤʤÉ) ¤¬µ¯¤³¤ë¤È
¼¡¤Î¥Ý¡¼¥ê¥ó¥°¼þ´ü¤Î´Ö¤Ë¤Ï fetchall ¥ª¥×¥·¥ç¥ó¤¬Í­¸ú¤È¤Ê¤ê¤Þ¤¹¡£
¤³¤ì¤Ï´è·ò¤µ¤ò¼Â¸½¤¹¤ëµ¡Ç½¤Ç¤¹¡£
¤Ä¤Þ¤ê¡¢¥á¥Ã¥»¡¼¥¸¤ò¼èÆÀ¤Ç¤­¤¿
(¤½¤·¤Æ¥á¡¼¥ë¥µ¡¼¥Ð¤Ç¤Ï´ûÆɤΰõ¤¬ÉÕ¤±¤é¤ì¤¿) ¤±¤ì¤É¡¢
°ì»þŪ¥¨¥é¡¼¤Î¤¿¤á¤Ë¥í¡¼¥«¥ë¤Ç¤ÏÇÛÁ÷¤µ¤ì¤Ê¤«¤Ã¤¿¾ì¹ç¡¢
¤½¤Î¥á¡¼¥ë¤Ï¼¡¤Î¥Ý¡¼¥ê¥ó¥°¼þ´ü¤Î¤È¤­¤ËºÆ¤Ó¼èÆÀ¤µ¤ì¤Þ¤¹¡£
(IMAP ¤Î»ÅÁȤߤǤϥá¥Ã¥»¡¼¥¸¤ÏÇÛ㤵¤ì¤ë¤Þ¤Ç¾Ãµî¤µ¤ì¤Þ¤»¤ó¡£
¤·¤¿¤¬¤Ã¤Æ¡¢¤³¤Î¤è¤¦¤ÊÌäÂê¤Ïµ¯¤³¤ê¤Þ¤»¤ó¡£)
.PP
.\"O If you touch or change the 
.\"O .I ~/.fetchmailrc 
.\"O file while fetchmail is running in daemon mode, this will be detected 
.\"O at the beginning of the next poll cycle.  When a changed
.\"O .I ~/.fetchmailrc  
.\"O is detected, fetchmail rereads it and restarts from scratch (using
.\"O exec(2); no state information is retained in the new instance).  Note also
.\"O that if you break the
.\"O .I ~/.fetchmailrc  
.\"O file's syntax, the new instance will softly and silently vanish away
.\"O on startup.
fetchmail ¤¬¥Ç¡¼¥â¥ó¥â¡¼¥É¤ÇÆ°ºî¤·¤Æ¤¤¤ë»þ¤Ë
.I ~/.fetchmailrc 
¥Õ¥¡¥¤¥ë¤ò touch ¤·¤¿¤êÊѹ¹¤¹¤ë¤È¡¢¤³¤ì¤Ï¼¡²ó¤Î¥Ý¡¼¥ê¥ó¥°¤¬»Ï¤Þ¤ë»þ¤Ë
¸¡½Ð¤µ¤ì¤Þ¤¹¡£
.I ~/.fetchmailrc 
¤ÎÊѹ¹¤¬¸¡½Ð¤µ¤ì¤ë¤È¡¢fetchmail ¤Ï¤³¤Î¥Õ¥¡¥¤¥ë¤òÆɤ߹þ¤ßľ¤·¡¢
¼«Ê¬¼«¿È¤òºÇ½é¤«¤éµ¯Æ°¤·Ä¾¤·¤Þ¤¹
(exec(2) ¤ò»È¤¤¤Þ¤¹¡£
¿·¤·¤¯Æ°ºî¤¹¤ë fetchmail ¤Ë¤Ï¡¢¾õÂ֤˴ؤ¹¤ë¤½¤ì¤Þ¤Ç¤Î¾ðÊó¤Ï°ìÀڻĤê¤Þ¤»¤ó)¡£
.I ~/.fetchmailrc 
¥Õ¥¡¥¤¥ë¤Îʸˡ¤Ë°ãÈ¿¤·¤Æ¤¤¤ë¤È¡¢
¿·¤·¤¤ fetchmail ¤Ïµ¯Æ°»þ¤ËÌۤäÆÀŤ«¤Ë¾Ã¤¨¤Æ¤·¤Þ¤¦¤Ç¤·¤ç¤¦¡£

.\"O .SH ADMINISTRATIVE OPTIONS
.SH ´ÉÍýÍÑ¥ª¥×¥·¥ç¥ó
.PP
.\"O The 
.\"O .B --postmaster <name>
.\"O option (keyword: set postmaster) specifies the last-resort username to
.\"O which multidrop mail is to be forwarded if no matching local recipient
.\"O can be found.  Normally this is just the user who invoked fetchmail.
.\"O If the invoking user is root, then the default of this option is
.\"O the user `postmaster'.  Setting postmaster to the empty string causes
.\"O such mail to be discarded.
.B --postmaster <¥æ¡¼¥¶Ì¾>
¥ª¥×¥·¥ç¥ó (¥­¡¼¥ï¡¼¥É: set postmaster) ¤Ï¡¢
¥í¡¼¥«¥ë¤Ç¥á¡¼¥ë¤ò¼õ¤±¼è¤ëŬÀڤʥ桼¥¶¤¬¸«¤Ä¤«¤é¤Ê¤«¤Ã¤¿¾ì¹ç¤Ë¡¢
¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¤¬Å¾Á÷¤µ¤ì¤ëºÇ½ªÃÏÅÀ¤Ë¤Ê¤ë¥æ¡¼¥¶Ì¾¤ò»ØÄꤷ¤Þ¤¹¡£
Ä̾¤³¤ì¤Ïñ¤Ë fetchmail ¤òµ¯Æ°¤·¤¿¥æ¡¼¥¶¤Ç¤¹¡£
µ¯Æ°¤·¤¿¥æ¡¼¥¶¤¬ root ¤Ç¤¢¤ì¤Ð¡¢
¤³¤Î¥ª¥×¥·¥ç¥ó¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤϥ桼¥¶ `postmaster' ¤Ë¤Ê¤ê¤Þ¤¹¡£
postmaster ¤Î¥æ¡¼¥¶Ì¾¤ò¶õ¤Îʸ»úÎó¤ËÀßÄꤹ¤ë¤È¡¢¤³¤Î¤è¤¦¤Ê¥á¡¼¥ë¤ÏÇË´þ¤µ¤ì¤Þ¤¹¡£
.PP
.\"O The
.\"O .B --nobounce
.\"O option suppresses the normal action of bouncing errors back to the 
.\"O sender in an RFC1894-conformant error message.  If nobounce is on, the
.\"O message will go to the postmaster instead.
.B --nobounce
¥ª¥×¥·¥ç¥ó¤Ï¡¢RFC1894 ½àµò¤Î¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Î¤¦¤Á¡¢
Á÷¿®¼Ô¤ËÌᤵ¤ì¤ëº¹Ìᤷ¥¨¥é¡¼ (bouncing error) ¤ÎÄ̾ï¤ÎÆ°ºî¤ò»ß¤á¤Þ¤¹¡£
nobounce ¤¬Í­¸ú¤Ê¾ì¹ç¡¢¥á¥Ã¥»¡¼¥¸¤ÏÁ÷¿®¼Ô¤Ç¤Ï¤Ê¤¯ postmaster ¤ËÁ÷¤é¤ì¤Þ¤¹¡£
.PP
.\"O The 
.\"O .B --invisible
.\"O option (keyword: set invisible) tries to make fetchmail invisible.
.\"O Normally, fetchmail behaves like any other MTA would -- it generates a
.\"O Received header into each message describing its place in the chain of
.\"O transmission, and tells the MTA it forwards to that the mail came from
.\"O the machine fetchmail itself is running on.  If the invisible option
.\"O is on, the Received header is suppressed and fetchmail tries to spoof
.\"O the MTA it forwards to into thinking it came directly from the
.\"O mailserver host.
.B --invisible
¥ª¥×¥·¥ç¥ó (¥­¡¼¥ï¡¼¥É: set invisible) ¤Ï fetchmail ¤ò¸«¤¨¤Ê¤¯¤·¤è¤¦¤È¤·¤Þ¤¹¡£
Ä̾fetchmail ¤Ï¾¤Î MTA ¤ÈƱ¤¸¤è¤¦¤Ë¿¶Éñ¤¤¤Þ¤¹¡£
¤Ä¤Þ¤ê¡¢Á÷¿®¤Î·ÐÏ©¤¬µ­½Ò¤µ¤ì¤Æ¤¤¤ë Received ¥Ø¥Ã¥À¤ò¥á¥Ã¥»¡¼¥¸Á´¤Æ¤Ë½ñ¤­¹þ¤ß¡¢
žÁ÷Àè¤Î MTA ¤Ë¡¢fetchmail ¤½¤Î¤â¤Î¤¬¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë¥Þ¥·¥ó¤«¤é
¥á¡¼¥ë¤¬Í褿¤³¤È¤òÃΤ餻¤Þ¤¹¡£
invisible ¥ª¥×¥·¥ç¥ó¤¬Í­¸ú¤Ç¤¢¤ë¾ì¹ç¤Ï¡¢
Received ¥Ø¥Ã¥À¤ÏÉÕ¤±¤é¤ì¤º¡¢fetchmail ¤ÏžÁ÷Àè¤Î MTA ¤ò¤À¤Þ¤·¤Æ¡¢
¥á¡¼¥ë¤¬¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥Û¥¹¥È¤«¤éľÀÜÆϤ¤¤¿¤È»×¤ï¤»¤è¤¦¤È¤·¤Þ¤¹¡£
.PP
.\"O The 
.\"O .B --showdots
.\"O option (keyword: set showdots) forces fetchmail to show progress dots
.\"O even if the current tty is not stdout (for example logfiles).
.\"O Starting with fetchmail version 5.3.0, 
.\"O progress dots are only shown on stdout by default.
.B --showdots
¥ª¥×¥·¥ç¥ó (¥­¡¼¥ï¡¼¥É: set showdots) ¤Ï¡¢
¤¿¤È¤¨¸½ºß¤ÎüËö (tty) ¤¬É¸½à½ÐÎϤǤʤ¤¾ì¹ç
(Î㤨¤Ð¥í¥°¥Õ¥¡¥¤¥ë¤Î¾ì¹ç) ¤Ç¤â¡¢¿ÊĽ¾õ¶·¤òɽ¤¹¥É¥Ã¥È¤òɽ¼¨¤¹¤ë¡£
fetchmail ¥Ð¡¼¥¸¥ç¥ó 5.3.0 ¤òµ¯Æ°¤·¤¿¾ì¹ç¡¢
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¿ÊĽ¾õ¶·¤òɽ¤¹¥É¥Ã¥È¤Ïɸ½à½ÐÎϤˤ·¤«É½¼¨¤µ¤ì¤Þ¤»¤ó¡£
.PP
.\"O By specifying the
.\"O .B --tracepolls
.\"O option, you can ask fetchmail to add information to the Received
.\"O header on the form "polling {label} account {user}", where {label} is
.\"O the account label (from the specified rcfile, normally ~/.fetchmailrc)
.\"O and {user} is the username which is used to log on to the mail
.\"O server. This header can be used to make filtering email where no
.\"O useful header information is available and you want mail from
.\"O different accounts sorted into different mailboxes (this could, for
.\"O example, occur if you have an account on the same server running a
.\"O mailing list, and are subscribed to the list using that account). The
.\"O default is not adding any such header.  In
.\"O .IR .fetchmailrc , 
.\"O this is called `tracepolls'.
.B --tracepolls
¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤³¤È¤Ë¤è¤ê¡¢fetchmail ¤ËÂФ·¤Æ
"polling {label} account {user}" ¤È¤¤¤¦·Á¼°¤Î¾ðÊó¤ò
Received ¥Ø¥Ã¥À¤Ë²Ã¤¨¤ë¤è¤¦¤Ë»Ø¼¨¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤³¤Ç¡¢{label} ¤Ï (»ØÄꤵ¤ì¤¿ÀßÄê¥Õ¥¡¥¤¥ë¡¢
Ä̾ï¤Ï ~/.fetchmailrc ¤Ç¤Î) ¥¢¥«¥¦¥ó¥È¥é¥Ù¥ë¤Ç¤¹¡£
¤Þ¤¿¡¢{user} ¤Ï¥á¡¼¥ë¥µ¡¼¥Ð¤Ë¥í¥°¥ª¥ó¤¹¤ë¤¿¤á¤Î¥æ¡¼¥¶Ì¾¤Ç¤¹¡£
¤³¤Î¥Ø¥Ã¥À¤Ï¡¢ÌòΩ¤Ä¥Ø¥Ã¥À¾ðÊó¤Î¤Ê¤¤ E ¥á¡¼¥ë¤ò¥Õ¥£¥ë¥¿¥ê¥ó¥°¤·¤¿¤ê¡¢
¥¢¥«¥¦¥ó¥ÈËè¤Î¥á¡¼¥ë¤òÊÌ¡¹¤Î¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤Ë
¥½¡¼¥È¤·¤ÆÆþ¤ì¤ë¤Î¤Ë»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹
(Î㤨¤Ð¡¢¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤¬±¿±Ä¤µ¤ì¤Æ¤¤¤ë¥µ¡¼¥Ð¤Ë¥¢¥«¥¦¥ó¥È¤¬¤¢¤ê¡¢
¤½¤Î¥¢¥«¥¦¥ó¥È¤ò»È¤Ã¤Æ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤ò¹ØÆɤ·¤Æ¤¤¤ë¾ì¹ç¤Ë
»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹)¡£
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¤³¤Î¤è¤¦¤Ê¥Ø¥Ã¥À¤ÏÄɲ䵤ì¤Þ¤»¤ó¡£
¤³¤ì¤Ï
.I .fetchmailrc
¤Ç¤Ï `tracepolls' ¤È¤¤¤¦¥­¡¼¥ï¡¼¥É¤Ë¤Ê¤ê¤Þ¤¹¡£

.\"O .SH RETRIEVAL FAILURE MODES
.SH ¼èÆÀ¼ºÇԥ⡼¥É
.\"O The protocols \fIfetchmail\fR uses to talk to mailservers are next to
.\"O bulletproof.  In normal operation forwarding to port 25, no message is
.\"O ever deleted (or even marked for deletion) on the host until the SMTP
.\"O listener on the client side has acknowledged to \fIfetchmail\fR that
.\"O the message has been either accepted for delivery or rejected due to a
.\"O spam block.
\fIfetchmail\fR ¤¬¥á¡¼¥ë¥µ¡¼¥Ð¤ÈÂÐÏ乤ëºÝ¤Ë»È¤¦¥×¥í¥È¥³¥ë¤Ï¡¢¤«¤Ê¤ê°ÂÁ´¤Ç¤¹¡£
25 È֥ݡ¼¥È¤Ø¤ÎžÁ÷¤ò¹Ô¤¦Ä̾ï¤ÎÁàºî¤Ç¤Ï¡¢
¥¯¥é¥¤¥¢¥ó¥È¾å¤Î SMTP ¼õ¿®¥×¥í¥°¥é¥à¤¬ \fIfetchmail\fR ¤ËÂФ·¤Æ
ÇÛÁ÷¤¹¤ë¥á¥Ã¥»¡¼¥¸¤ò¼õ¤±¼è¤Ã¤¿¤³¤È¤òÃΤ餻¤¿¤ê¡¢
¥¹¥Ñ¥àËɸæ¤Î¤¿¤á¤ËµñÈݤ·¤¿¤ê¤¹¤ë¤Þ¤Ç¤Ï¡¢
(ºï½ü¤Î°õ¤¬ÉÕ¤¤¤Æ¤¤¤¿¤È¤·¤Æ¤â) ¥Û¥¹¥È¾å¤Î¤¤¤«¤Ê¤ë¥á¥Ã¥»¡¼¥¸¤â¾Ã¤µ¤ì¤Þ¤»¤ó¡£
.PP
.\"O When forwarding to an MDA, however, there is more possibility
.\"O of error.  Some MDAs are `safe' and reliably return a nonzero status
.\"O on any delivery error, even one due to temporary resource limits.
¤·¤«¤·¡¢MDA ¤ËžÁ÷¤¹¤ë»þ¤Ë¤Ï¡¢¥¨¥é¡¼¤Î²ÄǽÀ­¤Ï¤º¤Ã¤È¹â¤¯¤Ê¤ê¤Þ¤¹
MDA ¤Î¤Ê¤«¤Ë¤Ï¡Ö°ÂÁ´¡×¤Ê¤â¤Î¤â¤¢¤ê¡¢
ÇÛÁ÷¥¨¥é¡¼¤Î¾ì¹ç¤ä°ì»þŪ¤Ê¥ê¥½¡¼¥¹»ñ¸»¤ò»È¤¤²Ì¤¿¤·¤¿¾ì¹ç¤Ë¤â¡¢
0 °Ê³°¤Î¥¹¥Æ¡¼¥¿¥¹¤òɬ¤ºÊÖ¤·¤Æ¤¯¤ì¤Þ¤¹¡£
.\"O The well-known
.\"O .IR procmail (1)
.\"O program is like this; so are most programs designed as mail transport
.\"O agents, such as 
.\"O .IR sendmail (1),
.\"O and
.\"O .IR exim (1).
ͭ̾¤Ê
.IR procmail (1)
¥×¥í¥°¥é¥à¤Ï¡¢¤³¤Î¤è¤¦¤ÊÆ°ºî¤ò¤·¤Þ¤¹¡£
.IR sendmail (1)
¤ä
.IR exim (1)
¤Î¤è¤¦¤Ê¥á¡¼¥ëžÁ÷¥¨¡¼¥¸¥§¥ó¥È¤È¤·¤Æ¥Ç¥¶¥¤¥ó¤µ¤ì¤¿ÂçÉôʬ¤Î¥×¥í¥°¥é¥à¤â¡¢
¤³¤Î¤è¤¦¤ÊÆ°ºî¤ò¤·¤Þ¤¹¡£
.\"O These programs give back a reliable positive acknowledgement and
.\"O can be used with the mda option with no risk of mail loss.  Unsafe
.\"O MDAs, though, may return 0 even on delivery failure.  If this
.\"O happens, you will lose mail.
¤³¤ì¤é¤Î¥×¥í¥°¥é¥à¤Ï¿®Íê¤Ç¤­¤ëÀѶËŪ¤ÊÊÖÅú¤òÊÖ¤·¤Æ¤¯¤ì¤ë¤Î¤Ç¡¢
¥á¡¼¥ë¤ò¼º¤¦¥ê¥¹¥¯¤òÉ餦¤³¤È¤Ê¤¯¡¢
mda ¥ª¥×¥·¥ç¥ó¤ò¤Ä¤±¤Æ»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤·¤«¤·°ÂÁ´¤Ç¤Ê¤¤ MDA ¤Ç¤Ï¡¢ÇÛÁ÷¤¬¼ºÇÔ¤·¤¿¾ì¹ç¤Ç¤â 0 ¤òÊÖ¤·¤Þ¤¹¡£
¤³¤Î¤è¤¦¤Ê»ö¤¬µ¯¤³¤ì¤Ð¡¢¥á¡¼¥ë¤¬¤Ê¤¯¤Ê¤ë¤Ç¤·¤ç¤¦¡£
.PP
.\"O The normal mode of \fIfetchmail\fR is to try to download only `new'
.\"O messages, leaving untouched (and undeleted) messages you have already
.\"O read directly on the server (or fetched with a previous \fIfetchmail
.\"O --keep\fR).  But you may find that messages you've already read on the
.\"O server are being fetched (and deleted) even when you don't specify
.\"O --all.  There are several reasons this can happen.
\fIfetchmail\fR ¤ÎÄ̾ï¥â¡¼¥É¤Ï¡¢
¡Ö¿·¤·¤¤¡×¥á¥Ã¥»¡¼¥¸¤À¤±¤ò¥À¥¦¥ó¥í¡¼¥É¤·¤è¤¦¤È¤·¡¢
¥µ¡¼¥Ð¤«¤é´û¤ËľÀÜÆɤ߽Ф·¤¿
(¤¢¤ë¤¤¤Ï¡¢°ÊÁ°¤Ë \fIfetchmail --keep\fR ¤ò»È¤Ã¤Æ¼õ¤±¼è¤Ã¤¿)
¥á¡¼¥ë¤Ë¤Ï´ØÍ¿¤·¤Þ¤»¤ó (ºï½ü¤â¤·¤Þ¤»¤ó)¡£
¤·¤«¤·¡¢--all ¤ò»ØÄꤷ¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ç¤µ¤¨¡¢¥µ¡¼¥Ð¾å¤Ë¤¢¤ë
´ûÆɤΥ᡼¥ë¤¬¼èÆÀ¤µ¤ì¤ë (¤½¤·¤Æºï½ü¤µ¤ì¤ë) ¤³¤È¤¬¤¢¤ë¤³¤È¤Ë
¤ªµ¤¤Å¤­¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
¤³¤Î¤è¤¦¤Ê¤³¤È¤¬µ¯¤³¤ëÍýͳ¤Ï¤¤¤¯¤Ä¤«¤¢¤ê¤Þ¤¹¡£
.PP
.\"O One could be that you're using POP2.  The POP2 protocol includes no
.\"O representation of `new' or `old' state in messages, so \fIfetchmail\fR
.\"O must treat all messages as new all the time.  But POP2 is obsolete, so
.\"O this is unlikely.
¤Þ¤º POP2 ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤¬¹Í¤¨¤é¤ì¤Þ¤¹¡£
POP2 ¥×¥í¥È¥³¥ë¤Ë¤Ï¡¢¥á¥Ã¥»¡¼¥¸¤Î¡Ö¿·µ¬¡×¤ä¡Ö´ûÆɡפξõÂÖ¤ò
ɽ¸½¤¹¤ëÊýË¡¤¬¤¢¤ê¤Þ¤»¤ó¡£
¤·¤¿¤¬¤Ã¤Æ¡¢\fIfetchmail\fR ¤Ïɬ¤ºÁ´¤Æ¤Î¥á¥Ã¥»¡¼¥¸¤ò
¿·¤·¤¤¤â¤Î¤È¤·¤Æ°·¤ï¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
¤·¤«¤·¡¢POP2 ¤Ï¸Å¤¯¤Æ»È¤ï¤ì¤Ê¤¯¤Ê¤Ã¤Æ¤¤¤ë¤Î¤Ç¡¢
¤³¤ì¤¬¸¶°ø¤Î¤³¤È¤Ï¤¢¤Þ¤ê¤Ê¤¤¤Ç¤·¤ç¤¦¡£
.PP
.\"O Under POP3, blame RFC1725.  That version of the POP3 protocol
.\"O specification removed the LAST command, and some POP servers follow it
.\"O (you can verify this by invoking \fIfetchmail -v\fR to the mailserver
.\"O and watching the response to LAST early in the query).  The
.\"O \fIfetchmail\fR code tries to compensate by using POP3's UID feature,
.\"O storing the identifiers of messages seen in each session until the
.\"O next session, in the \fI.fetchids\fR file.  But this doesn't track
.\"O messages seen with other clients, or read directly with a mailer on
.\"O the host but not deleted afterward.  A better solution would be to
.\"O switch to IMAP.
POP3 ¤Î¾ì¹ç¤Ë¤Ï¡¢RFC1725 ¤òº¨¤ó¤Ç¤¯¤À¤µ¤¤¡£
¤³¤Î¥Ð¡¼¥¸¥ç¥ó¤Î POP3 ¥×¥í¥È¥³¥ë¤Î»ÅÍͤǤÏ
LAST ¥³¥Þ¥ó¥É¤¬Ìµ¤¯¤Ê¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢
°ìÉô¤Î POP ¥µ¡¼¥Ð¤¬¤³¤ì¤Ë½àµò¤·¤Æ¤¤¤ë¤Î¤Ç¤¹
(¤³¤ì¤òÄ´¤Ù¤ë¤Ë¤Ï¡¢¥á¡¼¥ë¥µ¡¼¥Ð¤ËÂФ·¤Æ \fIfetchmail -v\fR ¤ò¼Â¹Ô¤·¤Æ¡¢
Ì䤤¹ç¤ï¤»¤ÎºÇ½é¤ÎÊý¤Ç¹Ô¤ï¤ì¤ë LAST ¥³¥Þ¥ó¥É¤Ø¤Î±þÅú¤ò¸«¤Æ¤¯¤À¤µ¤¤)¡£
\fIfetchmail\fR ¤Î¥³¡¼¥É¤Ç¤Ï
POP3 ¤Î UID µ¡Ç½¤ò»È¤Ã¤ÆËä¤á¹ç¤ï¤»¤ò¤·¤è¤¦¤È¤·¤Æ¤¤¤Þ¤¹¡£
¤³¤ì¤Ï¡¢¤½¤ì¤¾¤ì¤Î¥»¥Ã¥·¥ç¥ó¤Ç¸«¤¿¥á¥Ã¥»¡¼¥¸¤Î¼±Ê̻Ҥò¡¢
¼¡¤Î¥»¥Ã¥·¥ç¥ó¤Þ¤Ç \fI.fetchids\fR ¤ËÊݸ¤·¤Æ¤ª¤¯¤È¤¤¤¦ÊýË¡¤Ç¤¹¡£
¤·¤«¤·¤³¤ÎÊýË¡¤Ç¤Ï¡¢Â¾¤Î¥¯¥é¥¤¥¢¥ó¥È¤Ç¸«¤¿¥á¥Ã¥»¡¼¥¸¤ä¡¢
¥Û¥¹¥È¾å¤Î¥á¡¼¥é¤ÇľÀÜÆɤޤ줿¤±¤ì¤É
¤½¤Î¸å¤Ç¾Ã¤µ¤ì¤Æ¤¤¤Ê¤¤¥á¥Ã¥»¡¼¥¸¤Þ¤Ç¤ÏÄɤ¤¤«¤±¤é¤ì¤Þ¤»¤ó¡£
IMAP ¤Ë¾è¤ê´¹¤¨¤ëÊý¤¬¤¤¤¤¤Ç¤·¤ç¤¦¡£
.PP
.\"O Another potential POP3 problem might be servers that insert messages
.\"O in the middle of mailboxes (some VMS implementations of mail are
.\"O rumored to do this).  The \fIfetchmail\fR code assumes that new
.\"O messages are appended to the end of the mailbox; when this is not true
.\"O it may treat some old messages as new and vice versa.  The only 
.\"O real fix for this problem is to  switch to IMAP.
¾¤Ëµ¯¤³¤ë²ÄǽÀ­¤¬¤¢¤ë POP3 ¤ÎÌäÂê¤È¤·¤Æ¡¢
¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤ÎÅÓÃæ¤Ë¥á¥Ã¥»¡¼¥¸¤òÁÞÆþ¤¹¤ë¥µ¡¼¥Ð¤¬¹Í¤¨¤é¤ì¤Þ¤¹
(VMS ¤Î¥á¡¼¥ë¤Î¼ÂÁõ¤Î°ìÉô¤Ë¡¢¤³¤Î¤è¤¦¤Ê¤â¤Î¤¬¤¢¤ë¤È¸À¤ï¤ì¤Æ¤¤¤Þ¤¹)¡£
\fIfetchmail\fR ¤Î¥³¡¼¥É¤Ç¤Ï¡¢
¿·¤·¤¤¥á¡¼¥ë¤Ï¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤ÎºÇ¸å¤ËÄɲ䵤ì¤ë¤³¤È¤òÁÛÄꤷ¤Æ¤¤¤Þ¤¹¡£
¤³¤ì¤¬À®¤êΩ¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢
¸Å¤¤¥á¥Ã¥»¡¼¥¸¤Î°ìÉô¤¬¿·¤·¤¤¤â¤Î¤È¤·¤Æ°·¤ï¤ì¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¤·¡¢
¤½¤ÎµÕ¤âµ¯¤³¤ê¤Þ¤¹¡£
¤³¤ÎÌäÂê¤ò¿¿¤ÃÅö¤Ë²ò·è¤¹¤ëÍ£°ì¤ÎÊýË¡¤Ï¡¢IMAP ¤Ë¾è¤ê´¹¤¨¤ë¤³¤È¤Ç¤¹¡£
.PP
.\"O Yet another POP3 problem is that if they can't make tempfiles in the
.\"O user's home directory, some POP3 servers will hand back an
.\"O undocumented response that causes fetchmail to spuriously report "No
.\"O mail".
POP3 ¤ÎÊ̤ÎÌäÂê¤È¤·¤Æ¡¢
¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Ë°ì»þ¥Õ¥¡¥¤¥ë¤¬ºîÀ®¤Ç¤­¤Ê¤¤¾ì¹ç¤Ë¡¢
°ìÉô¤Î POP3 ¥µ¡¼¥Ð¤Ïʸ½ñ²½¤µ¤ì¤Æ¤¤¤Ê¤¤±þÅú¤òÊÖ¤¹¤¿¤á¡¢
fetchmail ¤¬´Ö°ã¤Ã¤Æ¡ÖNo mail¡×¤ÈÊó¹ð¤·¤Æ¤·¤Þ¤¦¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
.PP
.\"O The IMAP code uses the presence or absence of the server flag \eSeen
.\"O to decide whether or not a message is new.  Under Unix, it counts on
.\"O your IMAP server to notice the BSD-style Status flags set by mail user
.\"O agents and set the \eSeen flag from them when appropriate.  All Unix
.\"O IMAP servers we know of do this, though it's not specified by the IMAP
.\"O RFCs.  If you ever trip over a server that doesn't, the symptom will
.\"O be that messages you have already read on your host will look new to
.\"O the server.  In this (unlikely) case, only messages you fetched with
.\"O \fIfetchmail --keep\fR will be both undeleted and marked old.
IMAP ¤Î¥³¡¼¥É¤Ç¤Ï¡¢¥µ¡¼¥Ð¾å¤Î \eSeen ¤Î̵ͭ¤ò»È¤Ã¤Æ
¥á¥Ã¥»¡¼¥¸¤¬¿·¤·¤¤¤«¤É¤¦¤«¤ò·è¤á¤Æ¤¤¤Þ¤¹¡£
Unix ¤Î¾ì¹ç¡¢fetchmail ¤Ï IMAP ¥µ¡¼¥Ð¤¬¥á¡¼¥ë¥æ¡¼¥¶¥¨¡¼¥¸¥§¥ó¥È¤¬ÀßÄꤷ¤¿
BSD ·Á¼°¤Î Status ¥Õ¥é¥°¤ËÃíÌܤ·¡¢
ŬÅö¤Ê»þ¤Ë¤³¤ì¤é¤ò»È¤Ã¤Æ \eSeen ¥Õ¥é¥°¤òÀßÄꤹ¤ë¤³¤È¤ò´üÂÔ¤·¤Þ¤¹¡£
¤³¤ì¤Ï IMAP ¤Î RFC ¤Î»ÅÍͤˤϤ¢¤ê¤Þ¤»¤ó¤¬¡¢
²æ¡¹¤¬ÃΤë¸Â¤ê¤Î Unix ÍÑ IMAP ¥µ¡¼¥Ð¤ÏÁ´¤Æ¤³¤ì¤ò¹Ô¤¤¤Þ¤¹¡£
¤³¤ì¤ò¹Ô¤ï¤Ê¤¤¥µ¡¼¥Ð¤Ç¤Ä¤Þ¤º¤¤¤¿¤È¤­¤Ë¤Ï¡¢
¥Û¥¹¥È¾å¤Î´ûÆɤΥá¥Ã¥»¡¼¥¸¤¬
¥µ¡¼¥Ð¤Ë¤Ï¿·¤·¤¯¸«¤¨¤ë¤È¸À¤Ã¤¿¾É¾õ¤¬¸½¤ï¤ì¤ë¤Ç¤·¤ç¤¦¡£
¤³¤Î¾ì¹ç (¤¢¤Þ¤êµ¯¤³¤ê¤Þ¤»¤ó¤¬) ¤Ë¤Ï¡¢\fIfetchmail --keep\fR ¤Ç
¼èÆÀ¤·¤¿¥á¥Ã¥»¡¼¥¸¤À¤±¤¬¾Ã¤µ¤ì¤º¡¢¤«¤Ä´ûÆɤΰõ¤¬ÉÕ¤±¤é¤ì¤Þ¤¹¡£
.PP
.\"O In ETRN and ODMR modes, \fIfetchmail\fR does not actually retrieve messages;
.\"O instead, it asks the server's SMTP listener to start a queue flush
.\"O to the client via SMTP.  Therefore it sends only undelivered messages.
ETRN ¤È ODMR ¥â¡¼¥É¤Ç¤Ï¡¢\fIfetchmail\fR ¤Ï¼ÂºÝ¤Ë¤Ï¥á¡¼¥ë¤ò¼èÆÀ¤·¤Þ¤»¤ó¡£
¤½¤ÎÂå¤ï¤ê¤Ë¡¢¥µ¡¼¥Ð¤Î SMTP ¥ê¥¹¥Ê¤ËÂФ·¤Æ¡¢
¥¯¥é¥¤¥¢¥ó¥È¤Ë SMTP ·Ðͳ¤Î¥­¥å¡¼¤Î¥Õ¥é¥Ã¥·¥å¤ò³«»Ï¤¹¤ë¤è¤¦¤Ë»Ø¼¨¤·¤Þ¤¹¡£
¤·¤¿¤¬¤Ã¤Æ¡¢Ì¤ÇÛÁ÷¤Î¥á¥Ã¥»¡¼¥¸¤·¤«Á÷¤ê¤Þ¤»¤ó¡£

.\"O .SH SPAM FILTERING
.SH ¥¹¥Ñ¥à¥Õ¥£¥ë¥¿¥ê¥ó¥°
.\"O Many SMTP listeners allow administrators to set up `spam filters' that
.\"O block unsolicited email from specified domains.  A MAIL FROM or DATA line that
.\"O triggers this feature will elicit an SMTP response which
.\"O (unfortunately) varies according to the listener.
SMTP ¥ê¥¹¥Ê¤Î¿¤¯¤Ç¤Ï¡¢»ØÄꤷ¤¿¥É¥á¥¤¥ó¤«¤éÁ÷¤é¤ì¤Æ¤¯¤ëÉÔÍפʥ᡼¥ë¤ò
¥Ö¥í¥Ã¥¯¤¹¤ë¡Ö¥¹¥Ñ¥à¥Õ¥£¥ë¥¿ (spam filter)¡×¤ò´ÉÍý¼Ô¤¬ÀßÄê¤Ç¤­¤Þ¤¹¡£
¤³¤Îµ¡Ç½¤ò¸Æ¤Ó½Ð¤¹ MAIL FROM ¤¢¤ë¤¤¤Ï DATA ¹Ô¤Ï¡¢
(»ÄÇ°¤Ê¤³¤È¤Ë) ¥ê¥¹¥Ê¤Ë¤è¤Ã¤Æ°Û¤Ê¤ë SMTP ¤Î±þÅú¤ò°ú¤­½Ð¤·¤Þ¤¹¡£
.PP
.\"O Newer versions of 
.\"O .I sendmail
.\"O return an error code of 571.  This return value
.\"O is blessed by RFC1893 as "Delivery not authorized, message refused".
ºÇ¶á¤Î¥Ð¡¼¥¸¥ç¥ó¤Î
.I sendmail
¤Ï¥¨¥é¡¼¥³¡¼¥É 571 ¤òÊÖ¤·¤Þ¤¹¡£
¤³¤ÎÊÖ¤·ÃÍ¤Ï RFC1893 ¤Ë¤è¤Ã¤Æ "Delivery not authorized, message refused"
¤È¤·¤ÆÍ¿¤¨¤é¤ì¤Æ¤¤¤Þ¤¹¡£
.PP
.\"O According to current drafts of the replacement for RFC821, the correct
.\"O thing to return in this situation is 550 "Requested action not taken:
.\"O mailbox unavailable" (the draft adds "[E.g., mailbox not found, no
.\"O access, or command rejected for policy reasons].").
RFC821 ¤«¤éÃÖ¤­´¹¤¨¤é¤ì¤¿¸½ºß¤Î¥É¥é¥Õ¥È¤Ë¤è¤ë¤È¡¢
¤³¤Î¤è¤¦¤Ê¾õ¶·¤ÇÊÖ¤¹¤Ù¤­Àµ¤·¤¤Ãͤϡ¢
550 "Requested action not taken: mailbox unavailable" 
¤È¤µ¤ì¤Æ¤¤¤Þ¤¹
(¤³¤Î¥É¥é¥Õ¥È¤Ç¤Ï "[E.g., mailbox not found, no access, or
command rejected for policy reasons]." ¤òÄɲ䷤Ƥ¤¤Þ¤¹)¡£
.PP
.\"O The
.\"O .I exim
.\"O MTA returns 501 "Syntax error in parameters or arguments", but will
.\"O move to 550 soon.
.I exim
¤È¤¤¤¦ MTA ¤Ï 501 "Syntax error in parameters or arguments" ¤òÊÖ¤·¤Þ¤¹¤¬¡¢
¤³¤ì¤Ï¤â¤¦¤¹¤° 550 ¤ËÊѹ¹¤µ¤ì¤Þ¤¹¡£
.PP
.\"O The
.\"O .I postfix
.\"O MTA runs 554 as an antispam response.
.I postfix
¤È¤¤¤¦ MTA ¤Ï¥¹¥Ñ¥àµñÈݤαþÅú¤È¤·¤Æ 554 ¤òÊÖ¤·¤Þ¤¹¡£
.PP
.\"O The
.\"O .I fetchmail
.\"O code recognizes and discards the message on any of a list of responses
.\"O that defaults to [571, 550, 501, 554] but can be set with the `antispam'
.\"O option.  This is one of the
.\"O .I only
.\"O three circumstance under which fetchmail ever discards mail (the others
.\"O are the 552 and 553 errors described below, and the suppression of
.\"O multidropped messages with a message-ID already seen).
fetchmail ¤Î¥³¡¼¥É¤Ï±þÅú¤Î¥ê¥¹¥È¤Î¤¤¤º¤ì¤«¤Ë³ºÅö¤¹¤ë¥á¥Ã¥»¡¼¥¸¤ò
ǧ¼±¡¦ÇË´þ¤·¤Þ¤¹¡£
¤³¤Î¥ê¥¹¥È¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï [571, 550, 501, 554] ¤Ç¤¹¤¬¡¢
`antispam' ¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤ÆÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
fetchmail ¤¬¥á¡¼¥ë¤òÇË´þ¤·¤Æ¤·¤Þ¤¦¾õ¶·¤Ï
.I 3 ¤Ä¤·¤«
¤¢¤ê¤Þ¤»¤ó¤¬¡¢¤³¤ì¤Ï¤½¤Î¤¦¤Á¤Î 1 ¤Ä¤Ç¤¹
(»Ä¤ê¤Ï¸å½Ò¤Î 552, 553 ¥¨¥é¡¼¤Î¾ì¹ç¤È¡¢
¥Þ¥ë¥Á¥É¥í¥Ã¥×¤µ¤ì¤¿¥á¥Ã¥»¡¼¥¸¤Ç
´û¤Ë½èÍý¤µ¤ì¤Æ¤¤¤ë¥á¥Ã¥»¡¼¥¸ ID ¤ò»ý¤Ä¤â¤Î¤òÇË´þ¤¹¤ë¾ì¹ç¤Ç¤¹)¡£
.PP
.\"O If
.\"O .I fetchmail
.\"O is fetching from an IMAP server, the antispam response will be detected and
.\"O the message rejected immediately after the headers have been fetched,
.\"O without reading the message body.  Thus, you won't pay for downloading 
.\"O spam message bodies.
.I fetchmail
¤¬ IMAP ¥µ¡¼¥Ð¤«¤é¥á¡¼¥ë¤ò¼èÆÀ¤¹¤ë¾ì¹ç¤Ë antispam ¤Î±þÅú¤¬¸¡½Ð¤µ¤ì¤ë¤È¡¢
antispam ¥Ø¥Ã¥À¤ò¼èÆÀ¤·¤¿¸å¡¢¥á¥Ã¥»¡¼¥¸ËÜÂΤòÆɤळ¤È¤Ê¤¯
¨ºÂ¤Ë¥á¥Ã¥»¡¼¥¸¤òµñÈݤ·¤Þ¤¹¡£
¤·¤¿¤¬¤Ã¤Æ¡¢spam ¥á¥Ã¥»¡¼¥¸¤ÎËÜÂΤò¥À¥¦¥ó¥í¡¼¥É¤¹¤ëʬ¤Î
²Ý¶â¤ò»Ùʧ¤¦¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
.PP
.\"O If the \fIspambounce\fR option is on, mail that is spam-blocked
.\"O triggers an RFC1892 bounce message informing the originator that we do
.\"O not accept mail from it.
\fIspambounce\fR ¥ª¥×¥·¥ç¥ó¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¡¢
¥á¡¼¥ë¤¬¥¹¥Ñ¥àËɸæ¤ò¼õ¤±¤ë¤È¡¢º¹½Ð¿Í¤Ë¥á¡¼¥ë¤ò¼õ¤±¼è¤é¤Ê¤«¤Ã¤¿¤³¤È¤òÃΤ餻¤ë
RFC1892 ¤Îº¹Ìᤷ¥á¥Ã¥»¡¼¥¸¤¬Á÷¤é¤ì¤Þ¤¹¡£

.\"O .SH SMTP/ESMTP ERROR HANDLING
.SH SMTP/ESMTP ¤Î¥¨¥é¡¼½èÍý
.\"O Besides the spam-blocking described above, fetchmail takes special
.\"O actions on the following SMTP/ESMTP error responses
ÀèÄøÀâÌÀ¤·¤¿¥¹¥Ñ¥àËɸæ°Ê³°¤Ë¤â¡¢
fetchmail ¤Ï°Ê²¼¤Î SMTP/ESMTP ¤Î¥¨¥é¡¼±þÅú¤ËÂФ·¤ÆÆüì¤ÊÆ°ºî¤ò¹Ô¤¤¤Þ¤¹:
.TP 5
.\"O 452 (insufficient system storage)
.\"O Leave the message in the server mailbox for later retrieval.
452 (¥·¥¹¥Æ¥à¤Î¥Ç¥£¥¹¥¯¤¬ÉÔ½½Ê¬¤Ç¤¹)
¸å¤Ç¼èÆÀ¤Ç¤­¤ë¤è¤¦¤Ë¥µ¡¼¥Ð¤Î¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤Ë¥á¥Ã¥»¡¼¥¸¤ò»Ä¤·¤Þ¤¹¡£
.TP 5
.\"O 552 (message exceeds fixed maximum message size)
.\"O Delete the message from the server.  Send bounce-mail to the
.\"O originator.
552 (¥á¥Ã¥»¡¼¥¸¤¬¸ÇÄê¤ÎºÇÂç¥á¥Ã¥»¡¼¥¸¥µ¥¤¥º¤ò±Û¤¨¤Þ¤·¤¿)
¥µ¡¼¥Ð¤«¤é¥á¥Ã¥»¡¼¥¸¤òºï½ü¤·¤Þ¤¹¡£º¹½Ð¿Í¤Ëº¹Ìᤷ¥á¡¼¥ë¤òÁ÷¤ê¤Þ¤¹¡£
.TP 5
.\"O 553 (invalid sending domain)
.\"O Delete the message from the server.  Send bounce-mail to the originator.
553 (Á÷¿®¥É¥á¥¤¥ó¤¬ÉÔÀµ¤Ç¤¹)
¥µ¡¼¥Ð¤«¤é¥á¥Ã¥»¡¼¥¸¤òºï½ü¤·¤Þ¤¹¡£º¹½Ð¿Í¤Ëº¹Ìᤷ¥á¡¼¥ë¤òÁ÷¤ê¤Þ¤¹¡£
.PP
.\"O Other errors trigger bounce mail back to the originator.
¾¤Î¥¨¥é¡¼¤Ç¤Ï¡¢º¹½Ð¿Í¤Ëº¹Ìᤷ¥á¡¼¥ë¤¬Á÷¤é¤ì¤Þ¤¹¡£

.\"O .SH THE RUN CONTROL FILE
.SH ¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë
.\"O The preferred way to set up fetchmail is to write a
.\"O \&\fI.fetchmailrc\fR file in your home directory (you may do this
.\"O directly, with a text editor, or indirectly via \fIfetchmailconf\fR).
.\"O When there is a conflict between the command-line arguments and the
.\"O arguments in this file, the command-line arguments take precedence.
fetchmail ¤òÀßÄꤹ¤ë¹¥¤Þ¤·¤¤ÊýË¡¤Ï¡¢
\&\fI.fetchmailrc\fR ¤ò¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤ËºîÀ®¤¹¤ë¤³¤È¤Ç¤¹
(¤³¤ì¤Ï¥Æ¥­¥¹¥È¥¨¥Ç¥£¥¿¤ÇľÀܹԤʤ¦¤³¤È¤â¤Ç¤­¤Þ¤¹¤·¡¢
\fIfetchmailconf\fR ¤ò»È¤Ã¤ÆÂÐÏÃŪ¤Ë¹Ô¤Ê¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹)¡£
¥³¥Þ¥ó¥É¥é¥¤¥ó°ú¤­¿ô¤È¡¢¤³¤Î¥Õ¥¡¥¤¥ëÃæ¤Î°ú¤­¿ô¤¬½Å¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
¥³¥Þ¥ó¥É¥é¥¤¥ó°ú¤­¿ô¤ÎÊý¤¬Í¥À褵¤ì¤Þ¤¹¡£
.PP
.\"O To protect the security of your passwords, when --version is not on
.\"O your \fI~/.fetchmailrc\fR may not have more than 0600 (u=rw,g=,o=) permissions;
.\"O .I fetchmail
.\"O will complain and exit otherwise.
¥Ñ¥¹¥ï¡¼¥É¤Îµ¡Ì©¤ò¼é¤ë¤¿¤á¡¢--version ¥ª¥×¥·¥ç¥ó¤¬Í­¸ú¤Ç¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢
\fI~/.fetchmailrc\fR ¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤Ï
600 (u=rw,g=,o=) ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
600 °Ê³°¤Î¾ì¹ç¤Ë¤Ï¡¢
.I fetchmail
¤Ï¡¢¥¨¥é¡¼½ÐÎϤò¹Ô¤Ã¤Æ½ªÎ»¤·¤Þ¤¹¡£
.PP
.\"O You may read the \fI.fetchmailrc\fR file as a list of commands to 
.\"O be executed when 
.\"O .I fetchmail
.\"O is called with no arguments.
.I fetchmail
¤¬°ú¤­¿ô¤Ê¤·¤Ç¼Â¹Ô¤µ¤ì¤ë¾ì¹ç¡¢\fI.fetchmailrc\fR ¥Õ¥¡¥¤¥ë¤Ï¼Â¹Ô¤µ¤ì¤ë
¥³¥Þ¥ó¥É¤Î¥ê¥¹¥È¤È¤·¤ÆÆɤळ¤È¤¬¤Ç¤­¤Þ¤¹¡£
.\"O .SS Run Control Syntax
.SS ¼Â¹ÔÀ©¸æ¤Îµ­Ë¡
.PP
.\"O Comments begin with a '#' and extend through the end of the line.
.\"O Otherwise the file consists of a series of server entries or global
.\"O option statements in a free-format, token-oriented syntax.
¥³¥á¥ó¥È¤Ï '#' ¤Ç»Ï¤Þ¤ê¡¢¤½¤Î¹Ô¤ÎºÇ¸å¤Þ¤Ç³¤­¤Þ¤¹¡£
¤½¤¦¤Ç¤Ê¤¤¾ì¹ç¡¢¤³¤Î¥Õ¥¡¥¤¥ë¤Ï
¥Õ¥ê¡¼¥Õ¥©¡¼¥Þ¥Ã¥È¤«¤Ä¥È¡¼¥¯¥ó»Ø¸þ¤Îʸˡ¤Ç½ñ¤«¤ì¤¿¡¢
°ìÏ¢¤Î¥µ¡¼¥Ð¥¨¥ó¥È¥ê¤«Æ°ºîÁ´ÂΤΥª¥×¥·¥ç¥ó¤Îµ­½Ò¤Ç¹½À®¤µ¤ì¤Þ¤¹¡£
.PP
.\"O There are four kinds of tokens: grammar keywords, numbers
.\"O (i.e. decimal digit sequences), unquoted strings, and quoted strings.
.\"O A quoted string is bounded by double quotes and may contain
.\"O whitespace (and quoted digits are treated as a string).  An unquoted
.\"O string is any whitespace-delimited token that is neither numeric, string
.\"O quoted nor contains the special characters `,', `;', `:', or `='.
¥È¡¼¥¯¥ó¤Ë¤Ï 4 ¼ïÎढ¤ê¤Þ¤¹: 
¤¹¤Ê¤ï¤Á¡¢Ê¸Ë¡¥­¡¼¥ï¡¼¥É¡¢¿ô»ú (¤Ä¤Þ¤ê10¿Ê¿ô¤òʤ٤¿¤â¤Î)¡¢
¥¯¥©¡¼¥È¤µ¤ì¤Æ¤¤¤Ê¤¤Ê¸»úÎó¡¢¥¯¥©¡¼¥È¤µ¤ì¤¿Ê¸»úÎó¤Ç¤¹¡£
¥¯¥©¡¼¥È¤µ¤ì¤¿Ê¸»úÎó¤Ï¥À¥Ö¥ë¥¯¥©¡¼¥È¤Ç°Ï¤Þ¤ì¡¢¶õÇòʸ»ú¤ò´Þ¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹
(¥¯¥©¡¼¥È¤µ¤ì¤¿¿ôÃͤÏʸ»úÎó¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹)¡£
¥¯¥©¡¼¥È¤µ¤ì¤Æ¤¤¤Ê¤¤Ê¸»úÎó¤Ï¡¢¶õÇò¤Ç¶èÀÚ¤é¤ì¤ëǤ°Õ¤Î¥È¡¼¥¯¥ó¤Ç¤¢¤ê¡¢
¿ôÃͤ䥯¥©¡¼¥È¤µ¤ì¤¿Ê¸»úÎó¤Ç¤Ê¤¯¡¢
Æüìʸ»ú `,', `;', `:', `=' ¤â´Þ¤Þ¤Ê¤¤¤â¤Î¤Ç¤¹¡£
.PP
.\"O Any amount of whitespace separates tokens in server entries, but is
.\"O otherwise ignored. You may use standard C-style escapes (\en, \et,
.\"O \eb, octal, and hex) to embed non-printable characters or string
.\"O delimiters in strings.
Ǥ°Õ¤Î¿ô¤Î¶õÇòʸ»ú¤Ï¥µ¡¼¥Ð¥¨¥ó¥È¥êÃæ¤Î¥È¡¼¥¯¥ó¤ò¶èÀÚ¤ê¤Þ¤¹¤¬¡¢
¤½¤ì°Ê³°¤Ë¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£
ɸ½à¤Î C ¸À¸ì·Á¼°¤Î¥¨¥¹¥±¡¼¥×ʸ»ú (\en, \et, \eb, 8¿Ê¿ô, 16¿Ê¿ô) ¤òÍѤ¤¤Æ
ɽ¼¨ÉÔ²Äǽ¤Êʸ»úÎó¤äʸ»úÎó¤Î¶èÀÚ¤êʸ»ú¤òʸ»úÎóÃæ¤ËËä¤á¹þ¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.PP
.\"O Each server entry consists of one of the keywords `poll' or `skip',
.\"O followed by a server name, followed by server options, followed by any
.\"O number of user descriptions.  Note: the most common cause of syntax
.\"O errors is mixing up user and server options.
³Æ¥µ¡¼¥Ð¥¨¥ó¥È¥ê¤Ï¡¢¥­¡¼¥ï¡¼¥É `poll' ¤Þ¤¿¤Ï `skip'¡¢
¤³¤ì¤Ë³¤¯¥µ¡¼¥Ð̾¡¢¤½¤Î¸å¤Ë³¤¯¥µ¡¼¥Ð¥ª¥×¥·¥ç¥ó¡¢
¤µ¤é¤Ë¤½¤Î¸å¤Ë³¤¯Ç¤°Õ¤Î¿ô¤Î¥æ¡¼¥¶µ­½Ò¤«¤é¹½À®¤µ¤ì¤Þ¤¹¡£
Ãí°Õ: °ìÈÖµ¯¤³¤·¤ä¤¹¤¤Ê¸Ë¡¥¨¥é¡¼¤Î¸¶°ø¤Ï¡¢
¥æ¡¼¥¶¥ª¥×¥·¥ç¥ó¤È¥µ¡¼¥Ð¥ª¥×¥·¥ç¥ó¤òº®¤¼¤Æ¤·¤Þ¤¦¤³¤È¤Ç¤¹¡£
.PP
.\"O For backward compatibility, the word `server' is a synonym for `poll'.
¸åÊý¸ß´¹À­¤Î¤¿¤á¡¢¥­¡¼¥ï¡¼¥É `server' ¤Ï `poll' ¤ÈƱµÁ¤Ë¤Ê¤ê¤Þ¤¹¡£
.PP 
.\"O You can use the noise keywords `and', `with',
.\"O \&`has', `wants', and `options' anywhere in an entry to make
.\"O it resemble English.  They're ignored, but but can make entries much
.\"O easier to read at a glance.  The punctuation characters ':', ';' and
.\"O \&',' are also ignored.
±Ñ¸ì¤Ë»÷¤»¤ë¤¿¤á¡¢¥Î¥¤¥º¥ï¡¼¥É `and', `with', `has', `wants', `options' ¤ò
¥¨¥ó¥È¥êÃæ¤ÎǤ°Õ¤Î¾ì½ê¤Ç»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤ì¤é¤Ï̵»ë¤µ¤ì¤Þ¤¹¤¬¡¢¥¨¥ó¥È¥ê¤¬¤º¤Ã¤ÈÆɤߤ䤹¤¯¤Ê¤ê¤Þ¤¹¡£
¶èÀÚ¤êʸ»ú ':', ';', ',' ¤âƱ¤¸¤¯Ìµ»ë¤µ¤ì¤Þ¤¹¡£
.PP
.\"O .SS Poll vs. Skip
.SS poll ÂÐ skip
.\"O The `poll' verb tells fetchmail to query this host when it is run with
.\"O no arguments.  The `skip' verb tells
.\"O .I fetchmail 
.\"O not to poll this host unless it is explicitly named on the command
.\"O line.  (The `skip' verb allows you to experiment with test entries
.\"O safely, or easily disable entries for hosts that are temporarily down.)
`poll' ¤ò»ØÄꤹ¤ë¤È¡¢fetchmail ¤¬°ú¤­¿ô¤Ê¤·¤Ç¼Â¹Ô¤·¤¿»þ¡¢
¤³¤Î¥Û¥¹¥È¤Ø¤ÎÌ䤤¹ç¤ï¤»¤¬¹Ô¤ï¤ì¤Þ¤¹¡£
`skip' ¤ò»ØÄꤹ¤ë¤È¡¢¥³¥Þ¥ó¥É¥é¥¤¥ó¤ÇÌÀ¼¨Åª¤Ë»ØÄꤷ¤Ê¤¤¸Â¤ê
.I fetchmail 
¤Ï¤³¤Î¥Û¥¹¥È¤Ë¥Ý¡¼¥ê¥ó¥°¤ò¹Ô¤¤¤Þ¤»¤ó¡£
(`skip' ¤ò»È¤¦¤È¡¢¥Æ¥¹¥ÈÍÑ¥¨¥ó¥È¥ê¤Ç°ÂÁ´¤Ë¼Â¸³¤ò¹Ô¤Ê¤¦¤³¤È¤ä¡¢
°ì»þŪ¤ËÍî¤Á¤Æ¤¤¤ë¥Û¥¹¥ÈÍѤΥ¨¥ó¥È¥ê¤ò´Êñ¤Ë̵¸ú¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£)
.PP
.\"O .SS Keyword/Option Summary
.SS ¥­¡¼¥ï¡¼¥É/¥ª¥×¥·¥ç¥ó¤Î¤Þ¤È¤á
.\"O Here are the legal options.  Keyword suffixes enclosed in
.\"O square brackets are optional.  Those corresponding to command-line
.\"O options are followed by `-' and the appropriate option letter.
°Ê²¼¤ÏÀµ¼°¤Ê¥ª¥×¥·¥ç¥ó¤Ç¤¹¡£
Âç³ç¸Ì ([]) ¤Ç³ç¤é¤ì¤Æ¤¤¤ë¥­¡¼¥ï¡¼¥É¥µ¥Õ¥£¥Ã¥¯¥¹¤Ï¾Êά²Äǽ¤Ç¤¹¡£
¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤ËÂбþ¤¹¤ë¤â¤Î¤Î¸å¤Ë¤Ï¡¢
`-' ¤ÈŬÀڤʥª¥×¥·¥ç¥óʸ»ú¤¬¤¢¤ê¤Þ¤¹¡£

.\"O Here are the legal global options:
Àµ¼°¤ÊÆ°ºîÁ´ÂΤΥª¥×¥·¥ç¥ó¤ò°Ê²¼¤Ë¼¨¤·¤Þ¤¹:

.TS
l l lw34.
.\"O Keyword    Opt     Function
¥­¡¼¥ï¡¼¥É      ¥ª¥×¥·¥ç¥ó      µ¡Ç½
_
set daemon      \&      T{
.\"O Set a background poll interval in seconds
¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤Ç¤Î¥Ý¡¼¥ê¥ó¥°´Ö³Ö¤òÉÿô¤ÇÀßÄꤷ¤Þ¤¹¡£
T}
set postmaster          \&      T{
.\"O Give the name of the last-resort mail recipient
ºÇ½ªÅª¤Ê¥á¡¼¥ë¼õ¼è¿Í¤Î̾Á°¤ò»ØÄꤷ¤Þ¤¹¡£
T}
set no bouncemail       \&      T{
.\"O Direct error mail to postmaster rather than sender
Á÷¿®¼Ô¤Ç¤Ï¤Ê¤¯¡¢postmaster ¤Ë¥¨¥é¡¼¥á¡¼¥ë¤òÁ÷¤ê¤Þ¤¹¡£
T}
set no spambounce       \&      T{
.\"O Send spam bounces
¥¹¥Ñ¥àËɸæ¤ò¼õ¤±¤¿¤È¤­¤Ëº¹Ìᤷ¥á¡¼¥ë¤òÁ÷¤ê¤Þ¤¹¡£
T}
set logfile     \&      T{
.\"O Name of a file to dump error and status messages to
¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤È¾õÂÖ¥á¥Ã¥»¡¼¥¸¤ò½ñ¤­¹þ¤à¥Õ¥¡¥¤¥ë̾
T}
set idfile      \&      T{
.\"O Name of the file to store UID lists in
UID ¥ê¥¹¥È¤ò³ÊǼ¤¹¤ë¥Õ¥¡¥¤¥ë̾¡£
T}
set syslog      \&      T{
.\"O Do error logging through syslog(3).
syslog(3) ¤ò»È¤Ã¤¿¥¨¥é¡¼¤Î¥í¥°¼èÆÀ¤ò¹Ô¤¤¤Þ¤¹¡£
T}
set nosyslog    \&      T{
.\"O Turn off error logging through syslog(3).
syslog(3) ¤ò»È¤Ã¤¿¥¨¥é¡¼¤Î¥í¥°¼èÆÀ¤ò»ß¤á¤Þ¤¹¡£
T}
set properties  \&      T{
.\"O String value is ignored by fetchmail (may be used by extension scripts)
fetchmail ¤¬Ìµ»ë¤¹¤ëʸ»úÎó¤ÎÃÍ (³ÈÄ¥¥¹¥¯¥ê¥×¥È¤¬»È¤¦¤³¤È¤¬¤¢¤ê¤Þ¤¹)¡£
T}
.TE

.\"O Here are the legal server options:
°Ê²¼¤ÎÀµ¼°¤Ê¥µ¡¼¥Ð¥ª¥×¥·¥ç¥ó¤ò¼¨¤·¤Þ¤¹:

.TS
l l lw34.
.\"O Keyword    Opt     Function
¥­¡¼¥ï¡¼¥É      ¥ª¥×¥·¥ç¥ó      µ¡Ç½
_
via             \&      T{
.\"O Specify DNS name of mailserver, overriding poll name
¥á¡¼¥ë¥µ¡¼¥Ð¤Î DNS ̾¤ò»ØÄꤷ¤Þ¤¹¡£
¤³¤ì¤Ï poll ̾¤ò¾å½ñ¤­¤·¤Þ¤¹¡£
T}
proto[col]      -p      T{
.\"O Specify protocol (case insensitive):
¥×¥í¥È¥³¥ë¤ò»ØÄꤷ¤Þ¤¹ (Âçʸ»ú¡¦¾®Ê¸»ú¤Ï´Ø·¸¤¢¤ê¤Þ¤»¤ó):
POP2, POP3, IMAP, APOP, KPOP¡£
T}
local[domains]  \&      T{
.\"O Specify domain(s) to be regarded as local
¥í¡¼¥«¥ë¤È¤·¤Æ°·¤¦¥É¥á¥¤¥ó¤ò»ØÄꤷ¤Þ¤¹¡£
T}
port            -P      T{
.\"O Specify TCP/IP service port
TCP/IP ¤Î¥µ¡¼¥Ó¥¹¥Ý¡¼¥È¤ò»ØÄꤷ¤Þ¤¹¡£
T}
auth[enticate]  \&      T{
.\"O Set authentication type (default `password')
ǧ¾Ú¤Î¥¿¥¤¥×¤òÀßÄꤷ¤Þ¤¹ (¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï `password')¡£
T}
timeout         -t      T{
.\"O Server inactivity timeout in seconds (default 300)
¥µ¡¼¥Ð¤¬Æ°ºî¤·¤Æ¤¤¤Ê¤¤»þ¤Î¥¿¥¤¥à¥¢¥¦¥ÈÃͤòÉÿô¤Ç»ØÄꤷ¤Þ¤¹
(¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 300)¡£
T}
envelope        -E      T{
.\"O Specify envelope-address header name
¥¨¥ó¥Ù¥í¡¼¥×¥¢¥É¥ì¥¹¤Î¥Ø¥Ã¥À̾¤ò»ØÄꤷ¤Þ¤¹¡£
T}
no envelope     \&      T{
.\"O Disable looking for envelope address
¥¨¥ó¥Ù¥í¡¼¥×¥¢¥É¥ì¥¹¤Î¸¡º÷¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£
T}
qvirtual        -Q      T{
.\"O Qmail virtual domain prefix to remove from user name
¥æ¡¼¥¶Ì¾¤«¤é¼è¤ê½ü¤¯¡¢qmail ¤Î¥Ð¡¼¥Á¥ã¥ë¥É¥á¥¤¥ó¤Î¥×¥ì¥Õ¥£¥Ã¥¯¥¹¡£
T}
aka             \&      T{
.\"O Specify alternate DNS names of mailserver
¥á¡¼¥ë¥µ¡¼¥Ð¤ÎÊ̤ΠDNS ̾
T}
interface       -I      T{
.\"O specify IP interface(s) that must be up for server poll to take place
¥µ¡¼¥Ð¤Ø¤Î¥Ý¡¼¥ê¥ó¥°¤ò¹Ô¤¦¤¿¤á¤Ë¤ÏΩ¤Á¾å¤¬¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤
IP ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ò»ØÄꤷ¤Þ¤¹¡£
T}
monitor         -M      T{
.\"O Specify IP address to monitor for activity
Æ°ºî¤ò´Æ»ë¤¹¤ë IP ¥¢¥É¥ì¥¹¤ò»ØÄꤷ¤Þ¤¹¡£
T}
plugin          \&      T{
.\"O Specify command through which to make server connections.
¥µ¡¼¥ÐÀܳ¤ò³ÎΩ¤¹¤ë¤¿¤á¤Î¥³¥Þ¥ó¥É¤ò»ØÄꤷ¤Þ¤¹¡£
T}
plugout         \&      T{
.\"O Specify command through which to make listener connections.
¥ê¥¹¥ÊÀܳ¤ò³ÎΩ¤¹¤ë¤¿¤á¤Î¥³¥Þ¥ó¥É¤ò»ØÄꤷ¤Þ¤¹¡£
T}
dns             \&      T{
.\"O Enable DNS lookup for multidrop (default)
¥Þ¥ë¥Á¥É¥í¥Ã¥×ÍѤΠDNS »²¾È¤òÍ­¸ú¤Ë¤·¤Þ¤¹ (¥Ç¥Õ¥©¥ë¥È)¡£
T}
no dns          \&      T{
.\"O Disable DNS lookup for multidrop
¥Þ¥ë¥Á¥É¥í¥Ã¥×ÍѤΠDNS »²¾È¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£
T}
checkalias      \&      T{
.\"O Do comparison by IP address for multidrop
¥Þ¥ë¥Á¥É¥í¥Ã¥×¤Î¤¿¤á¤Ë IP ¥¢¥É¥ì¥¹¤Ë¤è¤ëÈæ³Ó¤ò¹Ô¤¤¤Þ¤¹¡£
T}
no checkalias   \&      T{
.\"O Do comparison by name for multidrop (default)
¥Þ¥ë¥Á¥É¥í¥Ã¥×¤Î¤¿¤á¤Ë̾Á°¤Ë¤è¤ëÈæ³Ó¤ò¹Ô¤¤¤Þ¤¹ (¥Ç¥Õ¥©¥ë¥È)¡£
T}
uidl            -U      T{
.\"O Force POP3 to use client-side UIDLs
POP3 ¤Çɬ¤º¥¯¥é¥¤¥¢¥ó¥È¦¤Ç UIDL ¤ò»È¤¦¤è¤¦¤Ë¤·¤Þ¤¹¡£
T}
no uidl         \&      T{
.\"O Turn off POP3 use of client-side UIDLs (default)
POP3 ¤Ç¤Î UIDL ¤Î»ÈÍѤò»ß¤á¤Þ¤¹ (¥Ç¥Õ¥©¥ë¥È)¡£
T}
interval        \&      T{
.\"O Only check this site every N poll cycles; N is a numeric argument.
¤³¤Î¥µ¥¤¥È¤À¤±¤ò N ¥Ý¡¼¥ê¥ó¥°¥µ¥¤¥¯¥ëËè¤Ë¥Á¥§¥Ã¥¯¤·¤Þ¤¹¡£
N ¤Ï¿ôÃͤΰú¤­¿ô¤Ç¤¹¡£
T}
netsec          \&      T{
.\"O Pass in IPsec security option request.
IPsec ¥»¥­¥å¥ê¥Æ¥£¥ª¥×¥·¥ç¥óÍ×µá¤òÅϤ·¤Þ¤¹¡£
T}
principal       \&      T{
.\"O Set Kerberos principal (only useful with imap and kerberos)
Kerberos ǧ¾Ú¤Î principal ¤òÀßÄꤷ¤Þ¤¹
(imap ¤È kerberos ¤Î¾ì¹ç¤Ë¤Î¤ßÍ­¸ú¤Ç¤¹)¡£
T}
.TE

.\"O Here are the legal user options:
Àµ¼°¤Ê¥æ¡¼¥¶¥ª¥×¥·¥ç¥ó¤ò°Ê²¼¤Ë¼¨¤·¤Þ¤¹:

.TS
l l lw34.
.\"O Keyword    Opt     Function
¥­¡¼¥ï¡¼¥É      ¥ª¥×¥·¥ç¥ó      µ¡Ç½
_
user[name]      -u      T{
.\"O Set remote user name 
.\"O (local user name if name followed by `here') 
¥ê¥â¡¼¥È¤Î¥æ¡¼¥¶Ì¾¤òÀßÄꤷ¤Þ¤¹
(name ¤Î¸å¤Ë `here' ¤¬¤¢¤ë¤È¡¢¥í¡¼¥«¥ë¤Î¥æ¡¼¥¶Ì¾¤Ç¤¹)¡£
T}
is              \&      T{
.\"O Connect local and remote user names
¥í¡¼¥«¥ë¤È¥ê¥â¡¼¥È¤Î¥æ¡¼¥¶Ì¾¤ò·Ò¤®¤Þ¤¹¡£
T}
to              \&      T{
.\"O Connect local and remote user names
¥í¡¼¥«¥ë¤È¥ê¥â¡¼¥È¤Î¥æ¡¼¥¶Ì¾¤ò·Ò¤®¤Þ¤¹¡£
T}
pass[word]      \&      T{
.\"O Specify remote account password
¥ê¥â¡¼¥È¥¢¥«¥¦¥ó¥È¤Î¥Ñ¥¹¥ï¡¼¥É¤ò»ØÄꤷ¤Þ¤¹¡£
T}
ssl             T{
.\"O Connect to server over the specified base protocol using SSL encryption
SSL ¤Ë¤è¤ë°Å¹æ²½¤ò»È¤¤¡¢
»ØÄꤵ¤ì¤¿´ðËÜ¥×¥í¥È¥³¥ë¤ò»È¤Ã¤Æ¥µ¡¼¥Ð¤ÈÀܳ¤·¤Þ¤¹¡£
T}
sslcert                 T{
.\"O Specify file for client side public SSL certificate
¥¯¥é¥¤¥¢¥ó¥È¦¤Î¸ø³« SSL ¾ÚÌÀ½ñ¤ò»ØÄꤷ¤Þ¤¹¡£
T}
sslkey                  T{
.\"O Specify file for client side private SSL key
¥¯¥é¥¤¥¢¥ó¥È¦¤ÎÈëÌ© SSL ¸°¤ò»ØÄꤷ¤Þ¤¹¡£
T}
sslproto                T{
.\"O Force ssl protocol for connection
Àܳ¤Î¤¿¤á¤Ë ssl ¥×¥í¥È¥³¥ë¤ò»È¤ï¤»¤Þ¤¹¡£
T}
folder          -r      T{
.\"O Specify remote folder to query
Ì䤤¹ç¤ï¤»¤ò¤¹¤ë¥ê¥â¡¼¥È¤Î¥Õ¥©¥ë¥À¤ò»ØÄꤷ¤Þ¤¹¡£
T}
smtphost        -S      T{
.\"O Specify smtp host(s) to forward to
žÁ÷Àè¤Î SMTP ¥Û¥¹¥È (·²) ¤ò»ØÄꤷ¤Þ¤¹¡£
T}
fetchdomains    \&      T{
.\"O Specify domains for which mail should be fetched
¥á¡¼¥ë¤ò¼èÆÀ¤¹¤ë¥É¥á¥¤¥ó¤ò»ØÄꤷ¤Þ¤¹¡£
T}
smtpaddress     -D      T{
.\"O Specify the domain to be put in RCPT TO lines
RCPT TO ¹Ô¤Ë½ñ¤¯¥É¥á¥¤¥ó¤ò»ØÄꤷ¤Þ¤¹¡£
T}
smtpname                T{
.\"O Specify the user and domain to be put in RCPT TO lines
RCPT TO ¹Ô¤Ë½ñ¤¯¥æ¡¼¥¶¤È¥É¥á¥¤¥ó¤ò»ØÄꤷ¤Þ¤¹¡£
T}
antispam        -Z      T{
.\"O Specify what SMTP returns are interpreted as spam-policy blocks
¥¹¥Ñ¥àËɸæ¤È²ò¼á¤µ¤ì¤ë SMTP ¤ÎÊÖ¤·Ãͤò»ØÄꤷ¤Þ¤¹¡£
T}
mda             -m      T{
.\"O Specify MDA for local delivery
¥í¡¼¥«¥ë¤ÎÇÛÁ÷¤Ë»È¤¦ MDA ¤ò»ØÄꤷ¤Þ¤¹¡£
T}
bsmtp           -o      T{
.\"O Specify BSMTP batch file to append to
Äɲ乤ë BSMTP ¥Ð¥Ã¥Á¥Õ¥¡¥¤¥ë¤ò»ØÄꤷ¤Þ¤¹¡£
T}
preconnect      \&      T{
.\"O Command to be executed before each connection
¤½¤ì¤¾¤ì¤ÎÀܳ¤ÎÁ°¤Ë¼Â¹Ô¤¹¤ë¥³¥Þ¥ó¥É¡£
T}
postconnect     \&      T{
.\"O Command to be executed after each connection
¤½¤ì¤¾¤ì¤ÎÀܳ¤Î¸å¤Ë¼Â¹Ô¤¹¤ë¥³¥Þ¥ó¥É¡£
T}
keep            -k      T{
.\"O Don't delete seen messages from server
´ûÆɤΥá¥Ã¥»¡¼¥¸¤ò¥µ¡¼¥Ð¤«¤éºï½ü¤·¤Þ¤»¤ó¡£
T}
flush           -F      T{
.\"O Flush all seen messages before querying
Ì䤤¹ç¤ï¤»¤ÎÁ°¤Ë´ûÆɤΥá¥Ã¥»¡¼¥¸¤òÁ´¤Æ¥Õ¥é¥Ã¥·¥å¤·¤Þ¤¹¡£
T}
fetchall        -a      T{
.\"O Fetch all messages whether seen or not
´ûÆÉ¡¦Ì¤Æɤˤ«¤«¤ï¤é¤ºÁ´¤Æ¤Î¥á¥Ã¥»¡¼¥¸¤ò¼èÆÀ¤·¤Þ¤¹¡£
T}
rewrite         \&      T{
.\"O Rewrite destination addresses for reply (default)
¥ê¥×¥é¥¤¤Î¤¿¤á¤ËÌÜŪ¥¢¥É¥ì¥¹¤ò½ñ¤­´¹¤¨¤Þ¤¹ (¥Ç¥Õ¥©¥ë¥È)¡£
T}
stripcr         \&      T{
.\"O Strip carriage returns from ends of lines
¹ÔËö¤«¤é¥­¥ã¥ê¥Ã¥¸¥ê¥¿¡¼¥óʸ»ú¤ò¼è¤ê½ü¤­¤Þ¤¹¡£
T}
forcecr         \&      T{
.\"O Force carriage returns at ends of lines
¹ÔËö¤Ë¥­¥ã¥ê¥Ã¥¸¥ê¥¿¡¼¥óʸ»ú¤ò¶¯À©¤·¤Þ¤¹¡£
T}
pass8bits       \&      T{
.\"O Force BODY=8BITMIME to ESMTP listener
ESMTP ¥ê¥¹¥Ê¤ËÂФ·¡¢BODY=8BITMIME ¤ò¶¯À©¤·¤Þ¤¹¡£
T}
dropstatus      \&      T{
.\"O Strip Status and X-Mozilla-Status lines out of incoming mail
¤ä¤Ã¤Æ¤¯¤ë¥á¡¼¥ë¤«¤é Status ¹Ô¤È X-Mozilla-Status ¹Ô¤ò¼è¤ê½ü¤­¤Þ¤¹¡£
T}
dropdelivered   \&      T{
.\"O Strip Delivered-To lines out of incoming mail
¤ä¤Ã¤Æ¤¯¤ë¥á¡¼¥ë¤«¤é Delivered-To ¹Ô¤ò¼è¤ê½ü¤­¤Þ¤¹¡£
T}
mimedecode      \&      T{
.\"O Convert quoted-printable to 8-bit in MIME messages
quoted-printable ¤ò 8¥Ó¥Ã¥È¤Î MIME ·Á¼°¤Î¥á¥Ã¥»¡¼¥¸¤ËÊÑ´¹¤·¤Þ¤¹¡£
T}
idle            \&      T{
.\"O Idle waiting for new messages after each poll (IMAP only)
³Æ¥Ý¡¼¥ê¥ó¥°¤Î¸å¡¢¿·¤·¤¤¥á¥Ã¥»¡¼¥¸¤òÂԤĥ¢¥¤¥É¥ë»þ´Ö (IMAP ÀìÍÑ)¡£
T}
no keep         -K      T{
.\"O Delete seen messages from server (default)
´ûÆɤΥá¥Ã¥»¡¼¥¸¤ò¥µ¡¼¥Ð¤«¤éºï½ü¤·¤Þ¤¹ (¥Ç¥Õ¥©¥ë¥È)¡£
T}
no flush        \&      T{
.\"O Don't flush all seen messages before querying (default)
Ì䤤¹ç¤ï¤»¤ÎÁ°¤Ë´ûÆÉ¥á¥Ã¥»¡¼¥¸Á´¤Æ¤Ï¥Õ¥é¥Ã¥·¥å¤·¤Þ¤»¤ó (¥Ç¥Õ¥©¥ë¥È)¡£
T}
no fetchall     \&      T{
.\"O Retrieve only new messages (default)
¿·µ¬¥á¥Ã¥»¡¼¥¸¤À¤±¤ò¼èÆÀ¤·¤Þ¤¹ (¥Ç¥Õ¥©¥ë¥È)¡£
T}
no rewrite      \&      T{
.\"O Don't rewrite headers
¥Ø¥Ã¥À¤ò½ñ¤­´¹¤¨¤Þ¤»¤ó¡£
T}
no stripcr      \&      T{
.\"O Don't strip carriage returns (default)
¥­¥ã¥ê¥Ã¥¸¥ê¥¿¡¼¥óʸ»ú¤ò¼è¤ê½ü¤­¤Þ¤»¤ó (¥Ç¥Õ¥©¥ë¥È)¡£
T}
no forcecr      \&      T{
.\"O Don't force carriage returns at EOL (default)
¹ÔËö¤Ë¤Ï¥­¥ã¥ê¥Ã¥¸¥ê¥¿¡¼¥óʸ»ú¤ò¶¯À©¤·¤Þ¤»¤ó (¥Ç¥Õ¥©¥ë¥È)¡£
T}
no pass8bits    \&      T{
.\"O Don't force BODY=8BITMIME to ESMTP listener (default)
ESMTP ¥ê¥¹¥Ê¤Ë BODY=8BITMIME ¤ò¶¯À©¤·¤Þ¤»¤ó (¥Ç¥Õ¥©¥ë¥È)¡£
T}
no dropstatus   \&      T{
.\"O Don't drop Status headers (default)
Status ¥Ø¥Ã¥À¤ò¼Î¤Æ¤Þ¤»¤ó (¥Ç¥Õ¥©¥ë¥È)¡£
T}
no mimedecode   \&      T{
.\"O Don't convert quoted-printable to 8-bit in MIME messages (default)
quoted-printable ¤ò 8 ¥Ó¥Ã¥È MIME ·Á¼°¤Î
¥á¥Ã¥»¡¼¥¸¤Ë¤ÏÊÑ´¹¤·¤Þ¤»¤ó (¥Ç¥Õ¥©¥ë¥È)¡£
T}
limit           -l      T{
.\"O Set message size limit
¥á¥Ã¥»¡¼¥¸¤Î¥µ¥¤¥º¤Î¾å¸Â¤òÀßÄꤷ¤Þ¤¹¡£
T}
warnings        -w      T{
.\"O Set message size warning interval
¥á¥Ã¥»¡¼¥¸¥µ¥¤¥º¤Ë´Ø¤¹¤ë·Ù¹ð¤Î»þ´Ö´Ö³Ö¤òÀßÄꤷ¤Þ¤¹¡£
T}
batchlimit      -b      T{
.\"O Max # messages to forward in single connect
1 ²ó¤ÎÀܳ¤ÇžÁ÷¤¹¤ë¤¹¤ëºÇÂç¥á¥Ã¥»¡¼¥¸¿ô¡£
T}
fetchlimit      -B      T{
.\"O Max # messages to fetch in single connect
1 ²ó¤ÎÀܳ¤Ç¼èÆÀ¤¹¤ëºÇÂç¥á¥Ã¥»¡¼¥¸¿ô¡£
T}
expunge         -e      T{
.\"O Perform an expunge on every #th message (IMAP and POP3 only)
²¿²óÌܤΥá¥Ã¥»¡¼¥¸¤´¤È¤Ëºï½ü¤ò¼Â¹Ô¤¹¤ë¤«¤ò»ØÄꤷ¤Þ¤¹ (IMAP ¤È POP3 ÀìÍÑ)¡£
T}
tracepolls      \&      T{
.\"O Add poll tracing information to the Received header
¥Ý¡¼¥ê¥ó¥°¥È¥ì¡¼¥¹¾ðÊó¤ò Received ¥Ø¥Ã¥À¤ËÄɲä·¤Þ¤¹¡£
T}
properties      \&      T{
.\"O String value is ignored by fetchmail (may be used by extension scripts)
fetchmail ¤¬Ìµ»ë¤¹¤ëʸ»úÎóÃÍ (³ÈÄ¥¥¹¥¯¥ê¥×¥È¤Ç»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹)¡£
T}
.TE
.PP
.\"O Remember that all user options must \fIfollow\fR all server options.
¥æ¡¼¥¶¥ª¥×¥·¥ç¥ó¤ÏÁ´¤Æ¥µ¡¼¥Ð¥ª¥×¥·¥ç¥ó¤è¤ê\fI¸å¤Ç¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó\fR¡£
.PP
.\"O In the .fetchmailrc file, the `envelope' string argument may be
.\"O preceded by a whitespace-separated number.  This number, if specified,
.\"O is the number of such headers to skip (that is, an argument of 1
.\"O selects the second header of the given type).  This is sometime useful
.\"O for ignoring bogus Received headers created by an ISP's local delivery
.\"O agent.
 .fetchmailrc ¤Ë¤ª¤¤¤Æ¤Ï¡¢`envelope' ʸ»úÎó°ú¤­¿ô¤ÎÁ°¤Ë¡¢
(¶õÇò¤Ç¶èÀڤäÆ) ¿ôÃͤòÃÖ¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤Î¿ô»ú¤¬»ØÄꤵ¤ì¤¿¾ì¹ç¡¢¤³¤ÎÃͤϤ³¤Î¤è¤¦¤Ê¥Ø¥Ã¥À¤òÈô¤Ð¤¹¿ô¤Ç¤¹
(¤Ä¤Þ¤ê¡¢¤³¤Î°ú¤­¿ô¤Ë 1 ¤ò»ØÄꤹ¤ë¤È¡¢
Í¿¤¨¤é¤ì¤¿¥¿¥¤¥×¤Î 2 ÈÖÌܤΥإåÀ¤¬ÁªÂò¤µ¤ì¤Þ¤¹)¡£
¤³¤ì¤Ï¡¢ISP ¤Î¥í¡¼¥«¥ë¤ÎÇÛÁ÷¥¨¡¼¥¸¥§¥ó¥È¤¬ÉÕ¤±¤¿
µ¶¤Î Received ¥Ø¥Ã¥À¤ò̵»ë¤¹¤ë»þ¤ËÊØÍø¤Ç¤¹¡£
.\"O .SS Keywords Not Corresponding To Option Switches
.SS ¥ª¥×¥·¥ç¥ó¥¹¥¤¥Ã¥Á¤ËÂбþ¤·¤Ê¤¤¥­¡¼¥ï¡¼¥É
.PP
.\"O The `folder' and `smtphost' options (unlike their command-line
.\"O equivalents) can take a space- or comma-separated list of names
.\"O following them.
`folder' ¤È `smtphost' ¥ª¥×¥·¥ç¥ó¤Ë¤Ï
(ƱÅù¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤È¤Ï°Û¤Ê¤ê)¡¢
¶õÇò¶èÀÚ¤ê¤Þ¤¿¤Ï¥³¥ó¥Þ¶èÀÚ¤ê¤Î̾Á°¤Î¥ê¥¹¥È¤ò³¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.PP
.\"O All options correspond to the obvious command-line arguments, except
.\"O the following: `via', `interval', `aka', `is', `to', `dns'/`no dns',
.\"O `checkalias'/`no checkalias', `password', `preconnect', `postconnect',
.\"O `localdomains', `stripcr'/`no stripcr', `forcecr'/`no forcecr',
.\"O `pass8bits'/`no pass8bits' `dropstatus/no dropstatus',
.\"O `dropdelivered/no dropdelivered', `mimedecode/no mimedecode', `idle/no
.\"O idle', and `no envelope'.
Á´¤Æ¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢¸«¤¿Ä̤ê¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó°ú¤­¿ô¤ËÂбþ¤·¤Þ¤¹¤¬¡¢
°Ê²¼¤Î¤â¤Î¤Ï¤³¤ì¤Ë³ºÅö¤·¤Þ¤»¤ó: 
`via', `interval', `aka', `is', `to', `dns'/`no dns',
`checkalias'/`no checkalias', `password', `preconnect', `postconnect',
`localdomains', `stripcr'/`no stripcr', `forcecr'/`no forcecr',
`pass8bits'/`no pass8bits' `dropstatus/no dropstatus',
`dropdelivered/no dropdelivered', `mimedecode/no mimedecode',
`idle/no idle', `no envelope'.
.PP
.\"O The `via' option is for if you want to have more
.\"O than one configuration pointing at the same site.  If it is present,
.\"O the string argument will be taken as the actual DNS name of the 
.\"O mailserver host to query.
.\"O This will override the argument of poll, which can then simply be a
.\"O distinct label for the configuration (e.g. what you would give on the
.\"O command line to explicitly query this host).
`via' ¥ª¥×¥·¥ç¥ó¤Ï
Ʊ¤¸¥µ¥¤¥È¤ò»Ø¤¹Ê£¿ô¤ÎÀßÄê¤ò»È¤¦¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£
¤³¤ì¤¬¤¢¤ë¾ì¹ç¡¢Ê¸»úÎó°ú¤­¿ô¤ÏÌ䤤¹ç¤ï¤»Àè¤Î
¥á¡¼¥ë¥µ¡¼¥Ð¤Î¼ÂºÝ¤Î DNS ̾¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£
¤³¤ì¤Ï poll °ú¤­¿ô¤ò¾å½ñ¤­¤·¡¢¤³¤ì¤òÀßÄê¤ò¶èÊ̤¹¤ëñ¤Ê¤ë¥é¥Ù¥ë
(Î㤨¤Ð¡¢¤³¤Î¥Û¥¹¥È¤òÌÀ¼¨Åª¤Ë»ØÄꤹ¤ë»þ¤Ë¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ç»ØÄꤹ¤ë¤â¤Î)
¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.PP
.\"O The `interval' option (which takes a numeric argument) allows you to poll a
.\"O server less frequently than the basic poll interval.  If you say
.\"O \&`interval N' the server this option is attached to will only be
.\"O queried every N poll intervals. 
`interval' ¥ª¥×¥·¥ç¥ó (¿ôÃͤΰú¤­¿ô¤ò¼è¤ê¤Þ¤¹) ¤ò»È¤¦¤È¡¢
´ðËÜŪ¤Ê¥Ý¡¼¥ê¥ó¥°´Ö³Ö¤è¤ê¾¯¤Ê¤¤ÉÑÅÙ¤Ç
¥µ¡¼¥Ð¤Ë¥Ý¡¼¥ê¥ó¥°¤ò¹Ô¤ï¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
\&`interval N' ¤ò»ØÄꤹ¤ë¤È¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤¬³ä¤êÅö¤Æ¤é¤ì¤¿
¥µ¡¼¥Ð¤ËÂФ¹¤ëÌ䤤¹ç¤ï¤»¤Ï N ²ó¤´¤È¤Î¥Ý¡¼¥ê¥ó¥°´Ö³Ö¤Ç¤·¤«¹Ô¤ï¤ì¤Þ¤»¤ó¡£
.PP
.\"O The `is' or `to' keywords associate the following local (client)
.\"O name(s) (or server-name to client-name mappings separated by =) with
.\"O the mailserver user name in the entry.  If an is/to list has `*' as
.\"O its last name, unrecognized names are simply passed through.
`is' ¤Þ¤¿¤Ï `to' ¥­¡¼¥ï¡¼¥É¤Ï¡¢¤½¤Î¸å¤Ë³¤¯¥í¡¼¥«¥ë (¥¯¥é¥¤¥¢¥ó¥È) ̾
(¤Þ¤¿¤Ï¡¢= ¤Ç¶èÀÚ¤é¤ì¤ë¥µ¡¼¥Ð̾¤«¤é¥¯¥é¥¤¥¢¥ó¥È̾¤Ø¤Î¥Þ¥Ã¥Ô¥ó¥°) ¤ò
¥¨¥ó¥È¥êÃæ¤Î¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥æ¡¼¥¶Ì¾¤È´ØÏ¢ÉÕ¤±¤Þ¤¹¡£
is/to ¤Î¥ê¥¹¥È¤ÎºÇ¸å¤Î̾Á°¤Ë `*' ¤¬¤¢¤ì¤Ð¡¢Ç§¼±¤µ¤ì¤Ê¤¤Ì¾Á°¤â¤½¤Î¤Þ¤ÞÄ̤·¤Þ¤¹¡£
.PP
.\"O A single local name can be used to support redirecting your mail when
.\"O your username on the client machine is different from your name on the
.\"O mailserver.  When there is only a single local name, mail is forwarded
.\"O to that local username regardless of the message's Received, To, Cc,
.\"O and Bcc headers.  In this case 
.\"O .I fetchmail
.\"O never does DNS lookups.
1 ¤Ä¤Î¥í¡¼¥«¥ë̾¤ò»È¤Ã¤Æ¡¢¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¤Ç¤Î¥æ¡¼¥¶Ì¾¤¬
¥á¡¼¥ë¥µ¡¼¥Ð¾å¤Î̾Á°¤È°Û¤Ê¤ë»þ¤Ë¡¢
¥á¡¼¥ë¤Î¥ê¥À¥¤¥ì¥¯¥È¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¥í¡¼¥«¥ë̾¤¬°ì¤Ä¤·¤«¤Ê¤¤¤È¤­¤Ï¡¢
¥á¥Ã¥»¡¼¥¸¤Î Received, To, Cc, Bcc ¥Ø¥Ã¥À¤Ë´Ø¤é¤º¡¢
¥á¡¼¥ë¤Ï¥í¡¼¥«¥ë¤Î¥æ¡¼¥¶Ì¾°¸¤ËžÁ÷¤µ¤ì¤Þ¤¹¡£
¤³¤Î¾ì¹ç¤Ë¤Ï¡¢
.I fetchmail
¤Ï DNS ¤Î»²¾È¤ò¹Ô¤¤¤Þ¤»¤ó¡£
.PP
.\"O When there is more than one local name (or name mapping) the
.\"O \fIfetchmail\fR code does look at the Received, To, Cc, and Bcc
.\"O headers of retrieved mail (this is `multidrop mode').  It looks for
.\"O addresses with hostname parts that match your poll name or your `via',
.\"O `aka' or `localdomains' options, and usually also for hostname parts
.\"O which DNS tells it are aliases of the mailserver.  See the discussion
.\"O of `dns', `checkalias', `localdomains', and `aka' for details on how
.\"O matching addresses are handled.
¥í¡¼¥«¥ë̾ (¤Þ¤¿¤Ï̾Á°¥Þ¥Ã¥Ô¥ó¥°) ¤¬Ê£¿ô¤¢¤ë»þ¤Ë¤Ï¡¢
\fIfetchmail\fR ¤Î¥³¡¼¥É¤Ï¼èÆÀ¤·¤¿¥á¡¼¥ë¤Î
Received, To, Cc, Bcc ¥Ø¥Ã¥À¤ò»²¾È¤·¤Þ¤¹
(¤³¤ì¤¬¡Ö¥Þ¥ë¥Á¥É¥í¥Ã¥×¥â¡¼¥É (multidrop mode)¡×¤Ç¤¹)¡£
\fIfetchmail\fR ¤Ï poll ̾¡¢`via', `aka', `localdomains' ¥ª¥×¥·¥ç¥ó¤Î
¤¤¤º¤ì¤«¤Ë¥Þ¥Ã¥Á¤¹¤ë¡¢¥Û¥¹¥ÈÉôʬ¤ò»ý¤Ä¥¢¥É¥ì¥¹¤òõ¤·¡¢
¤Þ¤¿ DNS ¤ÇÄ´¤Ù¤ë¤È¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥¨¥¤¥ê¥¢¥¹¤Ç¤¢¤ë¥Û¥¹¥È̾Éôʬ¤âÄ̾ï¤Ïõ¤·¤Þ¤¹¡£
¥¢¥É¥ì¥¹¤Î¥Þ¥Ã¥Á¥ó¥°¤Î½èÍýÊýË¡¤Î¾Ü¤·¤¤ÆâÍƤˤĤ¤¤Æ¤Ï¡¢
`dns', `checkalias', `localdomains', `aka' ¤ÎÀâÌÀ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
.PP
.\"O If \fIfetchmail\fR cannot match any mailserver usernames or
.\"O localdomain addresses, the mail will be bounced.
.\"O Normally it will be bounced to the sender, but if `nobounce' is on
.\"O it will go to the postmaster (which in turn defaults to being the
.\"O calling user).
\fIfetchmail\fR ¤¬¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥æ¡¼¥¶Ì¾¤Ë¤â
¥í¡¼¥«¥ë¥É¥á¥¤¥ó¤Ë¤â¥Þ¥Ã¥Á¤µ¤»¤é¤ì¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢¥á¡¼¥ë¤Ïº¹¤·Ìᤵ¤ì¤Þ¤¹¡£
¤³¤Î¥á¡¼¥ë¤ÏÄ̾º¹½Ð¿Í¤ËÌᤵ¤ì¤Þ¤¹¤¬¡¢
`nobounce' ¥ª¥×¥·¥ç¥ó¤¬Í­¸ú¤Ê¤é¤Ð¡¢¤³¤ì¤Ï postmaster ¤ËÁ÷¤é¤ì¤Þ¤¹
(¼¡¤Ë¡¢¤³¤ì¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç \fIfetchmail\fR ¤ò¸Æ¤Ó½Ð¤·¤¿¥æ¡¼¥¶¤Ë¤Ê¤ê¤Þ¤¹)¡£
.PP
.\"O The `dns' option (normally on) controls the way addresses from
.\"O multidrop mailboxes are checked.  On, it enables logic to check each
.\"O host address that doesn't match an `aka' or `localdomains' declaration
.\"O by looking it up with DNS.  When a mailserver username is recognized
.\"O attached to a matching hostname part, its local mapping is added to
.\"O the list of local recipients.
`dns' ¥ª¥×¥·¥ç¥ó (Ä̾ï¤ÏÍ­¸ú) ¤Ï¡¢¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤«¤é¼è¤ê½Ð¤·¤¿
¥¢¥É¥ì¥¹¤ò¥Á¥§¥Ã¥¯¤¹¤ëÊýË¡¤òÀ©¸æ¤·¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬Í­¸ú¤Î»þ¤Ë¤Ï¡¢DNS ¤ò»È¤Ã¤¿»²¾È¤ò¹Ô¤Ê¤¦¤³¤È¤Ë¤è¤ê¡¢
`aka' ¤Þ¤¿¤Ï `localdomains' ¤ÎÀë¸À¤Ë¥Þ¥Ã¥Á¤·¤Ê¤¤¥Û¥¹¥È¤½¤ì¤¾¤ì¤Î¥¢¥É¥ì¥¹¤ò
¥Á¥§¥Ã¥¯¤¹¤ë¥í¥¸¥Ã¥¯¤¬Í­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£
¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥æ¡¼¥¶Ì¾¤¬¡¢
¥Þ¥Ã¥Á¤¹¤ë¥Û¥¹¥È̾Éôʬ¤Ë³ä¤êÅö¤Æ¤é¤ì¤Æ¤¤¤ë¤³¤È¤¬Ç§¼±¤µ¤ì¤¿»þ¡¢
¤½¤Î¥í¡¼¥«¥ë¥Þ¥Ã¥Ô¥ó¥°¤¬¥í¡¼¥«¥ë¤Î¼õ¿®¼Ô¤Î¥ê¥¹¥È¤ËÄɲ䵤ì¤Þ¤¹¡£
.PP
.\"O The `checkalias' option (normally off) extends the lookups performed
.\"O by the `dns' keyword in multidrop mode, providing a way to cope with
.\"O remote MTAs that identify themselves using their canonical name, while
.\"O they're polled using an alias.
`checkalias' ¥ª¥×¥·¥ç¥ó (Ä̾ï¤Ï̵¸ú) ¤Ï¡¢
¥Þ¥ë¥Á¥É¥í¥Ã¥×¥â¡¼¥É¤Î `dns' ¥­¡¼¥ï¡¼¥É¤¬¼Â¹Ô¤·¤¿¸¡½Ð·ë²Ì¤ò³ÈÄ¥¤·¡¢
¥¨¥¤¥ê¥¢¥¹¤ò»È¤Ã¤Æ¥Ý¡¼¥ê¥ó¥°¤µ¤ì¤ë¤â¤Î¤Î¡¢
¼«Ê¬¼«¿È¤ò¼±Ê̤¹¤ë¤Ë¤Ï¥«¥Î¥Ë¥«¥ë¤Ê̾Á° (canonical name) ¤òÍѤ¤¤ë
¥ê¥â¡¼¥È¤Î MTA ¤ò¤¦¤Þ¤¯°·¤¦ÊýË¡¤òÄ󶡤·¤Þ¤¹¡£
.\"O When such a server is polled, checks to extract the envelope address
.\"O fail, and
.\"O .IR fetchmail 
.\"O reverts to delivery using the To/Cc/Bcc headers (See below 
.\"O `Header vs. Envelope addresses'). 
¤³¤Î¤è¤¦¤Ê¥µ¡¼¥Ð¤¬¥Ý¡¼¥ê¥ó¥°¤µ¤ì¤¿¤È¤­¤Ï¡¢
envelope ¥¢¥É¥ì¥¹¤¬Å¸³«¤µ¤ì¤¿¤³¤È¤Î¥Á¥§¥Ã¥¯¤Ï¼ºÇÔ¤·¡¢
.IR fetchmail 
¤Ï To/Cc/Bcc ¥Ø¥Ã¥À¤ò»È¤Ã¤¿ÇÛÁ÷¤ËÌá¤ê¤Þ¤¹
(¸å½Ò¤Î¡Ö¥Ø¥Ã¥ÀÂÐ envelope ¥¢¥É¥ì¥¹¡×¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤)¡£
.\"O Specifying this option instructs
.\"O .IR fetchmail 
.\"O to retrieve all the IP addresses associated with both the poll name
.\"O and the name used by the remote MTA and to do a comparison of the IP
.\"O addresses.  This comes in handy in situations where the remote server
.\"O undergoes frequent canonical name changes, that would otherwise
.\"O require modifications to the rcfile.  `checkalias' has no effect if
.\"O `no dns' is specified in the rcfile.
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È¡¢
.IR fetchmail 
¤ËÂФ¹¤ë¡¢
poll ̾¤È¥ê¥â¡¼¥È¤Î MTA ¤¬»È¤¦Ì¾Á°¤ÎξÊý¤Ë´Ø·¸¤¹¤ëÁ´¤Æ¤Î IP ¥¢¥É¥ì¥¹¤ò¼èÆÀ¤·¡¢
¤³¤ì¤é¤Î IP ¥¢¥É¥ì¥¹¤ÎÈæ³Ó¤ò¹Ô¤¦¤³¤È¤Î»Ø¼¨¤Ë¤Ê¤ê¤Þ¤¹¡£
¤³¤ì¤Ï¡¢¥ê¥â¡¼¥È¥µ¡¼¥Ð¤Î¥«¥Î¥Ë¥«¥ë¤Ê̾Á°¤¬ÉÑÈˤËÊѤï¤ë¾õ¶·¤ÇÌò¤ËΩ¤Á¤Þ¤¹¡£
¤³¤ì¤ò»È¤ï¤Ê¤±¤ì¤Ð¡¢¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë¤òÊѹ¹¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë¤Ç `no dns' ¤¬»ØÄꤵ¤ì¤¿¾ì¹ç¤Ï¡¢`checkalias' ¤Ï̵¸ú¤Ç¤¹¡£
.PP
.\"O The `aka' option is for use with multidrop mailboxes.  It allows you
.\"O to pre-declare a list of DNS aliases for a server.  This is an
.\"O optimization hack that allows you to trade space for speed.  When
.\"O .IR fetchmail ,
.\"O while processing a multidrop mailbox, grovels through message headers
.\"O looking for names of the mailserver, pre-declaring common ones can
.\"O save it from having to do DNS lookups.  Note: the names you give
.\"O as arguments to `aka' are matched as suffixes -- if you specify 
.\"O (say) `aka netaxs.com', this will match not just a hostnamed
.\"O netaxs.com, but any hostname that ends with `.netaxs.com'; such as 
.\"O (say) pop3.netaxs.com and mail.netaxs.com.
`aka' ¥ª¥×¥·¥ç¥ó¤Ï¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤È°ì½ï¤Ë»È¤¦¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢¥µ¡¼¥Ð¤Î DNS Ū¤ÊÊÌ̾¤Î¥ê¥¹¥È¤ò
ͽ¤áÀë¸À¤·¤Æ¤ª¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤ì¤Ï¡¢Â®ÅÙ¤ÈÍÆÎ̤Υȥ졼¥É¥ª¥Õ¤ò²Äǽ¤Ë¤¹¤ë¡¢ºÇŬ²½¤Î¤¿¤á¤Î¥Ï¥Ã¥¯¤Ç¤¹¡£
¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤ò½èÍý¤·¤Æ¤¤¤ë´Ö¤Ë¡¢
.IR fetchmail
¤¬¥á¥Ã¥»¡¼¥¸¤Î¥Ø¥Ã¥À¤ò»È¤Ã¤¿¥á¡¼¥ë¥µ¡¼¥Ð¤Î̾Á°¤Î¸¡º÷¤ò¤¢¤­¤é¤á¤¿»þ¡¢
ͽ¤áÀë¸À¤·¤Æ¤¢¤ë¶¦Ä̤Î̾Á°¤ò»È¤¦¤È¡¢DNS ¤ò»²¾È¤¹¤ë¤Ï¤á¤Ë¤Ê¤é¤Ê¤¤¤ÇºÑ¤ß¤Þ¤¹¡£
`aka' ¤Î°ú¤­¿ô¤È¤·¤ÆÍ¿¤¨¤¿Ì¾Á°¤Ï¡¢
³ÈÄ¥»Ò¤È¤·¤Æ¥Þ¥Ã¥Á¤µ¤ì¤ëÅÀ¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤ --
Î㤨¤Ð `aka netaxs.com' ¤ò»ØÄꤷ¤¿¾ì¹ç¡¢
ñ¤Ë netaxs.com ¤È¤¤¤¦Ì¾Á°¤Î¥Û¥¹¥È¤Ë¤Ï¥Þ¥Ã¥Á¤·¤Þ¤»¤ó¤¬¡¢
pop3.netaxs.com ¤ä mail.netaxs.com ¤È¤¤¤Ã¤¿
`.netaxs.com' ¤Ç½ª¤ëǤ°Õ¤Î¥Û¥¹¥È̾¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£
.PP
.\"O The `localdomains' option allows you to declare a list of domains
.\"O which fetchmail should consider local.  When fetchmail is parsing
.\"O address lines in multidrop modes, and a trailing segment of a host
.\"O name matches a declared local domain, that address is passed through
.\"O to the listener or MDA unaltered (local-name mappings are \fInot\fR
.\"O applied).
`localdomains' ¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢¥í¡¼¥«¥ë¤Ç¤¢¤ë¤È fetchmail ¤¬È½ÃǤ¹¤ë
¥É¥á¥¤¥ó¤Î¥ê¥¹¥È¤òÀë¸À¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
fetchmail ¤¬¥Þ¥ë¥Á¥É¥í¥Ã¥×¥â¡¼¥É¤Ç¥¢¥É¥ì¥¹¹Ô¤òŸ³«¤·¡¢
¤«¤Ä¸å¤Ë³¤¯¥Û¥¹¥È̾¤ÎÉôʬ¤¬Àë¸À¤µ¤ì¤¿¥í¡¼¥«¥ë¥É¥á¥¤¥ó¤Ë¥Þ¥Ã¥Á¤¹¤ë»þ¡¢
¤½¤Î¥¢¥É¥ì¥¹¤ÏÊѹ¹¤µ¤ì¤º¤Ë¥ê¥¹¥Ê¤Þ¤¿¤Ï MDA ¤ËÅϤµ¤ì¤Þ¤¹
(¥í¡¼¥«¥ë̾¥Þ¥Ã¥Ô¥ó¥°¤ÏŬÍÑ\fI¤µ¤ì¤Þ¤»¤ó\fR)¡£
.PP
.\"O If you are using `localdomains', you may also need to specify \&`no
.\"O envelope', which disables \fIfetchmail\fR's normal attempt to deduce
.\"O an envelope address from the Received line or X-Envelope-To header or
.\"O whatever header has been previously set by `envelope'.  If you set `no
.\"O envelope' in the defaults entry it is possible to undo that in
.\"O individual entries by using `envelope <string>'.  As a special case,
.\"O \&`envelope "Received"' restores the default parsing of
.\"O Received lines.
`localdomains' ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
\&`no envelope' ¤â»ØÄꤹ¤ëɬÍפ¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢\fIfetchmail\fR ¤ÎÄ̾ï¤Î¡¢
Received ¹Ô¤ä X-Envelope-To ¥Ø¥Ã¥À¡¢
¤¢¤ë¤¤¤Ï°ÊÁ°¤Ë `envelope' ¤ÇÀßÄꤵ¤ì¤¿¥Ø¥Ã¥À¤Î
¤¤¤º¤ì¤«¤«¤é envelope ¥¢¥É¥ì¥¹¤ò¿äÄꤷ¤è¤¦¤È¤¹¤ëÆ°ºî¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£
¥Ç¥Õ¥©¥ë¥È¤Î¥¨¥ó¥È¥êÃæ¤Ç `no envelope' ¤òÀßÄꤷ¤¿¾ì¹ç¡¢
`envelope <string>' ¤òÍѤ¤¤Æ¸ÄÊÌ¥¨¥ó¥È¥êÃæ¤Ç¤³¤ì¤ò¼è¤ê¾Ã¤¹¤³¤È¤¬²Äǽ¤Ç¤¹¡£
ÆÃÊ̤ʾì¹ç¤È¤·¤Æ¡¢\&`envelope "Received"' ¤Ç Received ¹Ô¤ÎŸ³«¤Î
¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤¬Éü¸µ¤µ¤ì¤Þ¤¹¡£
.PP
.\"O The \fBpassword\fR option requires a string argument, which is the password
.\"O to be used with the entry's server.
\fBpassword\fR ¥ª¥×¥·¥ç¥ó¤Ïʸ»úÎó¤Î°ú¤­¿ô¤òɬÍפȤ·¤Þ¤¹¡£
¤³¤Îʸ»úÎó¤Ï¥¨¥ó¥È¥ê¤Î¥µ¡¼¥Ð¤Ç»È¤¦¥Ñ¥¹¥ï¡¼¥É¤Ç¤¹¡£
.PP
.\"O The `preconnect' keyword allows you to specify a shell command to be
.\"O executed just before each time
.\"O .I fetchmail
.\"O establishes a mailserver connection.  This may be useful if you are 
.\"O attempting to set up secure POP connections with the aid of
.\"O .IR ssh (1).
.\"O If the command returns a nonzero status, the poll of that mailserver
.\"O will be aborted.
`preconnect' ¥­¡¼¥ï¡¼¥É¤ò»È¤¦¤È¡¢
.I fetchmail
¤¬¥á¡¼¥ë¥µ¡¼¥Ð¤Ø¤ÎÀܳ¤ò³ÎΩ¤¹¤ëľÁ°¤ËËè²ó¼Â¹Ô¤¹¤ë
¥·¥§¥ë¥³¥Þ¥ó¥É¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤ì¤Ï¡¢
.IR ssh (1)
¤ËÊä½õ¤µ¤»¤Æ°ÂÁ´¤Ê POP Àܳ¤ÎÀßÄê¤ò¤·¤è¤¦¤È¤¹¤ë»þ¤ËÌò¤ËΩ¤Ä¤«¤â¤·¤ì¤Þ¤»¤ó¡£
¥³¥Þ¥ó¥É¤¬¥¼¥í¤Ç¤Ê¤¤¥¹¥Æ¡¼¥¿¥¹¤òÊÖ¤·¤¿¾ì¹ç¡¢
¤½¤Î¥á¡¼¥ë¥µ¡¼¥Ð¤Ø¤Î¥Ý¡¼¥ê¥ó¥°¤Ï°Û¾ï½ªÎ»¤·¤Þ¤¹¡£
.PP
.\"O Similarly, the `postconnect' keyword similarly allows you to specify a
.\"O shell command to be executed just after each time a mailserver
.\"O connection is taken down.
ƱÍͤˡ¢`postconnect' ¥­¡¼¥ï¡¼¥É¤ò»È¤¦¤È¡¢¥á¡¼¥ë¥µ¡¼¥Ð¤Ø¤ÎÀܳ¤¬Àڤ줿
ľ¸å¤ËËè²ó¼Â¹Ô¤¹¤ë¥·¥§¥ë¥³¥Þ¥ó¥É¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.PP
.\"O The `forcecr' option controls whether lines terminated by LF only are
.\"O given CRLF termination before forwarding.  Strictly speaking RFC821
.\"O requires this, but few MTAs enforce the requirement it so this option
.\"O is normally off (only one such MTA, qmail, is in significant use at
.\"O time of writing).  
`forcecr' ¥ª¥×¥·¥ç¥ó¤Ï¡¢LF ¤À¤±¤Ç½ª¤ï¤ë¹Ô¤òžÁ÷¤ÎÁ°¤Ë
CRLF ¤Ç½ª¤ï¤ë¤è¤¦¤Ë¤¹¤ë¤«¤É¤¦¤«¤òÀ©¸æ¤·¤Þ¤¹¡£
¸·Ì©¤Ë¸À¤¦¤È RFC821 ¤Ï¤³¤ì¤òÍ׵ᤷ¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢
¤³¤ì¤òɬ¿Ü¤È¤·¤Æ¤¤¤ë MTA ¤Ï¤Û¤È¤ó¤É¤Ê¤¤¤Î¤Ç¡¢
¤³¤Î¥ª¥×¥·¥ç¥ó¤ÏÄ̾ï¤Ï̵¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹ 
(¤³¤Î¤è¤¦¤Ê MTA ¤ÇÆä˻Ȥï¤ì¤Æ¤¤¤ë¤Î¤Ï qmail ¤À¤±¤Ç¡¢
½ñ¤­¹þ¤ß»þ¤Ë¤³¤ì¤ò¹Ô¤¤¤Þ¤¹)¡£
.PP
.\"O The `stripcr' option controls whether carriage returns are stripped
.\"O out of retrieved mail before it is forwarded.  It is normally not
.\"O necessary to set this, because it defaults to `on' (CR stripping
.\"O enabled) when there is an MDA declared but `off' (CR stripping
.\"O disabled) when forwarding is via SMTP.  If `stripcr' and `forcecr' are
.\"O both on, `stripcr' will override.
`stripcr' ¥ª¥×¥·¥ç¥ó¤Ï¡¢¼èÆÀ¤·¤¿¥á¡¼¥ë¤òžÁ÷¤¹¤ëÁ°¤Ë
¥­¥ã¥ê¥Ã¥¸¥ê¥¿¡¼¥óʸ»ú¤ò¼è¤ê½ü¤¯¤«¤É¤¦¤«¤òÀ©¸æ¤·¤Þ¤¹¡£
Ä̾ï¤Ï¤³¤ì¤ò¥»¥Ã¥È¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£
¤Ê¤¼¤Ê¤é¡¢MDA ¤¬Àë¸À¤µ¤ì¤Æ¤¤¤ë¤È¤­¤Ë¤Ï¡¢
¤³¤ì¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¡Ö¥ª¥ó¡×(CR ºï½ü¤¬Í­¸ú) ¤È¤Ê¤ê¡¢
SMTP ·Ðͳ¤ÇžÁ÷¤µ¤ì¤ë¤È¤­¤Ë¤Ï¡Ö¥ª¥Õ¡×(CR ºï½ü¤¬Ìµ¸ú) ¤È¤Ê¤ë¤«¤é¤Ç¤¹¡£
`stripcr' ¤È `forcecr' ¤¬Î¾Êý¤È¤â¥ª¥ó¤Ê¤é¤Ð¡¢`stripcr' ¤¬Í¥À褵¤ì¤Þ¤¹¡£
.PP
.\"O The `pass8bits' option exists to cope with Microsoft mail programs that
.\"O stupidly slap a "Content-Transfer-Encoding: 7bit" on everything.  With
.\"O this option off (the default) and such a header present, 
.\"O .I fetchmail
.\"O declares BODY=7BIT to an ESMTP-capable listener; this causes problems for
.\"O messages actually using 8-bit ISO or KOI-8 character sets, which will
.\"O be garbled by having the high bits of all characters stripped.  If
.\"O \&`pass8bits' is on, 
.\"O .I fetchmail
.\"O is forced to declare BODY=8BITMIME to any ESMTP-capable listener.  If
.\"O the listener is 8-bit-clean (as all the major ones now are) the right
.\"O thing will probably result.

`pass8bits' ¤Ï¡¢²¿¤Ë¤Ç¤â "Content-Transfer-Encoding: 7bit" ¤òÉÕ¤±¤Æ¤¯¤ë
Çϼ¯¤Ê Microsoft ¤Î¥á¡¼¥é¤ò¤¦¤Þ¤¯°·¤¦¤¿¤á¤Ë¸ºß¤·¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬Ìµ¸ú (¥Ç¥Õ¥©¥ë¥È) ¤Ç¡¢¤«¤Ä¤³¤Î¥Ø¥Ã¥À¤¬Â¸ºß¤¹¤ë¤È¡¢
.I fetchmail
¤Ï ESMTP µ¡Ç½¤ò»ý¤Ä¥ê¥¹¥Ê¤ËÂФ·¤Æ BODY=7BIT ¤òÀë¸À¤·¤Þ¤¹¡£
¼ÂºÝ¤Ë¤Ï
8-bit ISO ¤ä KOI-8 ¤Îʸ»ú½¸¹ç¤ò»È¤Ã¤Æ¤¤¤ë¥á¥Ã¥»¡¼¥¸¤Î¾ì¹ç¡¢
¤³¤ì¤ÏÌäÂê¤òµ¯¤³¤·¤Þ¤¹¡£
¤³¤ì¤é¤Îʸ»ú¤Ï¾å°Ì¥Ó¥Ã¥È¤¬Á´¤ÆÍî¤È¤µ¤ì¤Æ¤·¤Þ¤¦¤¿¤á¡¢
ʸ»ú²½¤±¤·¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
\&`pass8bits' ¤¬¥ª¥ó¤Ç¤¢¤ì¤Ð¡¢
.I fetchmail
¤Ï ESMTP µ¡Ç½¤ò»ý¤Ä¥ê¥¹¥ÊÁ´¤Æ¤ËÂФ·¤Æɬ¤º BODY=8BITMIME ¤òÀë¸À¤·¤Þ¤¹¡£
¥ê¥¹¥Ê¤¬ 8 ¥Ó¥Ã¥È¥¯¥ê¡¼¥ó¤Ç¤¢¤ì¤Ð (ºÇ¶á¤Î¤á¤Ü¤·¤¤¤â¤Î¤ÏÁ´Éô¤½¤¦¤Ç¤¹)¡¢
¤¿¤Ö¤ó¤¦¤Þ¤¯¤¤¤¯¤Ç¤·¤ç¤¦¡£
.PP
.\"O The `dropstatus' option controls whether nonempty Status and
.\"O X-Mozilla-Status lines are retained in fetched mail (the default) or
.\"O discarded.  Retaining them allows your MUA to see what messages (if
.\"O any) were marked seen on the server.  On the other hand, it can
.\"O confuse some new-mail notifiers, which assume that anything with a
.\"O Status line in it has been seen.  (Note: the empty Status lines
.\"O inserted by some buggy POP servers are unconditionally discarded.)
`dropstatus' ¥ª¥×¥·¥ç¥ó¤Ï¡¢¼èÆÀ¤·¤¿¥á¡¼¥ëÃæ¤Î¶õ¤Ç¤Ê¤¤ Status ¹Ô¤È
X-Mozilla-Status ¹Ô¤ò»Ä¤¹ (¥Ç¥Õ¥©¥ë¥È) ¤«ÇË´þ¤¹¤ë¤«¤òÀ©¸æ¤·¤Þ¤¹¡£
¤³¤ì¤é¤ò»Ä¤¹¤È¡¢¤ª»È¤¤¤Î MUA ¤Ç (¤â¤·¤¢¤ì¤Ð)
¤É¤Î¥á¥Ã¥»¡¼¥¸¤¬¥µ¡¼¥Ð¾å¤Ç´ûÆɤΰõ¤¬ÉÕ¤±¤é¤ì¤Æ¤¤¤ë¤«¤òÃΤ뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£
°ìÊý¡¢¤³¤ÎÆ°ºî¤Ï¿·Ãå¥á¡¼¥ëÄÌÃÎ¥×¥í¥°¥é¥à¤Î°ìÉô¤òº®Í𤵤»¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
¤³¤ì¤é¤Î¥×¥í¥°¥é¥à¤Ï¡¢
Status ¹Ô¤¬ÉÕ¤¤¤Æ¤¤¤ë¤â¤Î¤ÏÁ´¤Æ´ûÆɤÈÁÛÄꤹ¤ë¤Î¤Ç¤¹¡£
(Ãí°Õ: °ìÉô¤Î¥Ð¥°¤Ã¤Ý¤¤ POP ¥µ¡¼¥Ð¤¬ÉÕ¤±¤ë
¶õ¤Î Status ¹Ô¤Ï̵¾ò·ï¤Ëºï½ü¤µ¤ì¤Þ¤¹¡£)
.PP
.\"O The `dropdelivered' option controls wether Delivered-To headers will
.\"O be kept in fetched mail (the default) or discarded. These headers are 
.\"O added by Qmail and Postfix mailservers in order to avoid mail loops but
.\"O may get in your way if you try to "mirror" a mailserver within the same
.\"O domain. Use with caution.
`dropdelivered' ¥ª¥×¥·¥ç¥ó¤Ï¡¢¼èÆÀ¤·¤¿¥á¡¼¥ëÃæ¤Î
Delivered-To ¥Ø¥Ã¥À¤ò»Ä¤¹ (¥Ç¥Õ¥©¥ë¥È) ¤«ÇË´þ¤¹¤ë¤«¤òÀ©¸æ¤·¤Þ¤¹¡£
¤³¤Î¥Ø¥Ã¥À¤Ï¡¢¥á¡¼¥ë¥µ¡¼¥Ð Qmail ¤È Postfix ¤¬
¥ë¡¼¥×¤òËɻߤ¹¤ë¤¿¤á¤Ë»ÈÍѤ·¤Æ¤¤¤Þ¤¹¤¬¡¢
Ʊ¤¸¥É¥á¥¤¥óÆâ¤Ç¥á¡¼¥ë¥µ¡¼¥Ð¤ò¡Ö¥ß¥é¡¼¡×¤·¤è¤¦¤È¤¹¤ë¾ì¹ç¤Ï¼ÙËâ¤Ë¤Ê¤ê¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢Ãí°Õ¤·¤Æ»ÈÍѤ·¤Æ²¼¤µ¤¤¡£
.PP
.\"O The `mimedecode' option controls whether MIME messages using the
.\"O quoted-printable encoding are automatically converted into pure 8-bit
.\"O data. If you are delivering mail to an ESMTP-capable, 8-bit-clean
.\"O listener (that includes all of the major MTAs like sendmail), then
.\"O this will automatically convert quoted-printable message headers and
.\"O data into 8-bit data, making it easier to understand when reading
.\"O mail. If your e-mail programs know how to deal with MIME messages,
.\"O then this option is not needed.  The mimedecode option is off by
.\"O default, because doing RFC2047 conversion on headers throws away
.\"O character-set information and can lead to bad results if the encoding
.\"O of the headers differs from the body encoding.
`mimedecode' ¥ª¥×¥·¥ç¥ó¤Ï¡¢quoted-printable ¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤òÍѤ¤¤Æ¤¤¤ë
MIME ¥á¥Ã¥»¡¼¥¸¤ò½ã¿è¤Ê 8 ¥Ó¥Ã¥È¥Ç¡¼¥¿¤Ë¼«Æ°Åª¤ËÊÑ´¹¤¹¤ë¤«¤É¤¦¤«¤òÀ©¸æ¤·¤Þ¤¹¡£
ESMTP µ¡Ç½¤ò»ý¤Á¡¢8 ¥Ó¥Ã¥È¥¯¥ê¡¼¥ó¤Ê¥ê¥¹¥Ê
(¤³¤ì¤Ë¤Ï sendmail ¤Ê¤É¤Îͭ̾¤Ê MTA ¤ÎÂçÉôʬ¤¬´Þ¤Þ¤ì¤Þ¤¹) ¤Ë
¥á¡¼¥ë¤òÇÛÁ÷¤¹¤ë¾ì¹ç¤Ë¤Ï¡¢
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È quoted-printable ¤Ç½ñ¤«¤ì¤¿
¥á¥Ã¥»¡¼¥¸¥Ø¥Ã¥À¤È¥Ç¡¼¥¿¤Ï¼«Æ°Åª¤Ë 8 ¥Ó¥Ã¥È¥Ç¡¼¥¿¤ËÊÑ´¹¤µ¤ì¡¢
¥á¡¼¥ë¤òÆɤà¤È¤­¤ËÍý²ò¤·¤ä¤¹¤¯¤Ê¤ê¤Þ¤¹¡£
¤ª»È¤¤¤ÎÅŻҥ᡼¥ë¥×¥í¥°¥é¥à¤¬ MIME ¥á¥Ã¥»¡¼¥¸¤ò°·¤¨¤ë¤Ê¤é¤Ð¡¢
¤³¤Î¥ª¥×¥·¥ç¥ó¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£
mimedecode ¥ª¥×¥·¥ç¥ó¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç̵¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
¤Ê¤¼¤Ê¤é¡¢¥Ø¥Ã¥À¤ËÂФ·¤Æ RFC2047 ¤ÎÊÑ´¹¤ò¹Ô¤¦¤Èʸ»ú½¸¹ç¤Î¾ðÊ󤬾䨤Ƥ·¤Þ¤¤¡¢
¥Ø¥Ã¥À¤Î¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤¬ËÜʸ¤Î¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤È°Û¤Ê¤ë¾ì¹ç¤Ë
¹¥¤Þ¤·¤¯¤Ê¤¤·ë²Ì¤Ë¤Ê¤ë¤«¤é¤Ç¤¹¡£
.PP
.\"O The `idle' option is usable only with IMAP servers supporting the
.\"O RFC2177 IDLE command extension.  If it is enabled, and fetchmail
.\"O detects that IDLE is supported, an IDLE will be issued at the end
.\"O of each poll.  This will tell the IMAP server to hold the connection
.\"O open and notify the client when new mail is available.  If you need to
.\"O poll a link frequently, IDLE can save bandwidth by eliminating TCP/IP
.\"O connects and LOGIN/LOGOUT sequences. On the other hand, an IDLE 
.\"O connection will eat almost all of your fetchmail's time, because it
.\"O will never drop the connection and allow other pools to occur unless
.\"O the server times out the IDLE.  It also doesn't work with multiple 
.\"O folders; only the first folder will ever be polled.
`idle' ¥ª¥×¥·¥ç¥ó¤Ï IMAP ¥µ¡¼¥Ð¤¬ RFC2177 IDLE ¥³¥Þ¥ó¥É³ÈÄ¥¤ò
¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¾ì¹ç¤Ë¤Î¤ß»ÈÍѤǤ­¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Æ¡¢
¤«¤Ä IDLE ¥³¥Þ¥ó¥É¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤³¤È¤ò fetchmail ¤¬¸¡ÃΤ·¤¿¾ì¹ç¡¢
¥Ý¡¼¥ê¥ó¥°¤Î½ªÎ»Ëè¤Ë IDLE ¥³¥Þ¥ó¥É¤¬È¯¹Ô¤µ¤ì¤Þ¤¹¡£
¤³¤Î¥³¥Þ¥ó¥É¤ò»È¤¦¤³¤È¤Ç¡¢
IMAP ¥µ¡¼¥Ð¤ËÀܳ¤ò¥ª¡¼¥×¥ó¤ËÊÝ»ý¤µ¤»¡¢
¿·¤·¤¤¥á¡¼¥ë¤¬Í褿¤³¤È¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÄÌÃΤµ¤»¤Þ¤¹¡£
ÉÑÈˤ˥ݡ¼¥ê¥ó¥°¤ò¹Ô¤¦É¬Íפ¬¤¢¤ë¾ì¹ç¡¢
IDLE ¥³¥Þ¥ó¥É¤Ï¡¢TCP/IP Àܳ¤È¥í¥°¥¤¥ó/¥í¥°¥¢¥¦¥È¥·¡¼¥±¥ó¥¹¤ò¤Ê¤¯¤¹¤³¤È¤Ç¡¢
¥Ð¥ó¥ÉÉý¤ò²¡¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
°ìÊý¤Ç¡¢IDLE Àܳ¤Ï fetchmail ¤Î¤Û¤È¤ó¤É¤Î»þ´Ö¤òÀê¤á¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
¤Ê¤¼¤Ê¤é¡¢IDLE ¥³¥Þ¥ó¥É¤ÏÀܳ¤òÀڤ餺¡¢
¥µ¡¼¥Ð¤¬ IDLE ¤ò¥¿¥¤¥à¥¢¥¦¥È¤·¤Ê¤¤¸Â¤ê
Ê̤Υס¼¥ë¤¬µ¯¤³¤ë¤³¤È¤òµö²Ä¤·¤Æ¤·¤Þ¤¦¤¿¤á¤Ç¤¹¡£
Ê£¿ô¤Î¥Õ¥©¥ë¥À¤¬¤¢¤ë¾ì¹ç¤âÆ°ºî¤»¤º¡¢
ºÇ½é¤Î¥Õ¥©¥ë¥À¤Î¤ß¤¬¥Ý¡¼¥ê¥ó¥°¤µ¤ì¤Þ¤¹¡£
.PP
.\"O The `properties' option is an extension mechanism.  It takes a string
.\"O argument, which is ignored by fetchmail itself.  The string argument may be
.\"O used to store configuration information for scripts which require it.
.\"O In particular, the output of `--configdump' option will make properties
.\"O associated with a user entry readily available to a Python script.
`properties' ¥ª¥×¥·¥ç¥ó¤Ï³ÈÄ¥¤Î¤¿¤á¤Îµ¡¹½¤Ç¤¹¡£
¤³¤ì¤Ïʸ»úÎó¤Î°ú¤­¿ô¤ò¼è¤ê¤Þ¤¹¤¬¡¢fetchmail ¼«¿È¤Ï¤³¤ì¤ò̵»ë¤·¤Þ¤¹¡£
¤³¤Îʸ»úÎó°ú¤­¿ô¤ò»È¤Ã¤Æ¡¢
ÀßÄê¾ðÊó¤òɬÍפȤ¹¤ë¥¹¥¯¥ê¥×¥È¤Î¤¿¤á¤Î¾ðÊó¤òÊÝ»ý¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
Æäˡ¢`--configdump'  ¥ª¥×¥·¥ç¥ó¤Î½ÐÎϤϡ¢
¤½¤Î¤Þ¤Þ Python ¥¹¥¯¥ê¥×¥È¤È¤·¤ÆÍøÍѤǤ­¤ë¡¢
¥æ¡¼¥¶¥¨¥ó¥È¥ê¤Ë´ØÏ¢¤¹¤ë¥×¥í¥Ñ¥Æ¥£¤È¤Ê¤ê¤Þ¤¹¡£
.PP
.\"O .SS Miscellaneous Run Control Options
.SS ¤½¤Î¾¤Î¼Â¹ÔÀ©¸æ¥ª¥×¥·¥ç¥ó
.\"O The words `here' and `there' have useful English-like
.\"O significance.  Normally `user eric is esr' would mean that 
.\"O mail for the remote user `eric' is to be delivered to `esr',
.\"O but you can make this clearer by saying `user eric there is esr here',
.\"O or reverse it by saying `user esr here is eric there'
`here' ¤È `there' ¤Ï¡¢±Ñ¸ì¤ÈƱ¤¸¤è¤¦¤Ê°ÕÌ£¤Ç»È¤¨¤ëÊØÍø¤Êñ¸ì¤Ç¤¹¡£
Ä̾ï `user eric is esr' ¤Ï¡¢¥ê¥â¡¼¥È¥æ¡¼¥¶ `eric' °¸¤Î¥á¡¼¥ë¤¬
`esr' °¸¤ËÇÛ㤵¤ì¤ë¤È¤¤¤¦°ÕÌ£¤Ç¤¹¡£
¤·¤«¤·¡¢`user eric there is esr here' ¤È½ñ¤¯¤³¤È¤Ç¤â¤Ã¤Èʬ¤«¤ê¤ä¤¹¤¯¤·¤¿¤ê¡¢
`user esr here is eric there' ¤È½ñ¤¤¤Æ°ÕÌ£¤òÈ¿ÂФˤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.PP
.\"O Legal protocol identifiers for use with the `protocol' keyword are:
`protocol' ¥­¡¼¥ï¡¼¥É¤Ç»ÈÍѤǤ­¤ëÍ­¸ú¤Ê¥×¥í¥È¥³¥ë¼±Ê̻Ҥò°Ê²¼¤Ë¼¨¤·¤Þ¤¹:

.\"O     auto (or AUTO)
.\"O     pop2 (or POP2)
.\"O     pop3 (or POP3)
.\"O     sdps (or SDPS)
.\"O     imap (or IMAP)
.\"O     apop (or APOP)
.\"O     kpop (or KPOP)
    auto (¤Þ¤¿¤Ï AUTO)
    pop2 (¤Þ¤¿¤Ï POP2)
    pop3 (¤Þ¤¿¤Ï POP3)
    sdps (¤Þ¤¿¤Ï SDPS)
    imap (¤Þ¤¿¤Ï IMAP)
    apop (¤Þ¤¿¤Ï APOP)
    kpop (¤Þ¤¿¤Ï KPOP)

.PP
.\"O Legal authentication types are `any', `password', `kerberos', 'kereberos_v5' 
.\"O and `gssapi', `cram-md5', `otp', `ntlm', `ssh`.
.\"O The `password' type specifies authentication by normal transmission of a
.\"O password (the password may be plaintext or subject to
.\"O protocol-specific encryption as in APOP); `kerberos' tells
.\"O \fIfetchmail\fR to try to get a Kerberos ticket at the start of each
.\"O query instead, and send an arbitrary string as the password; and
.\"O `gssapi' tells fetchmail to use GSSAPI authentication.  See the description
.\"O of the `auth' keyword for more.
Í­¸ú¤Êǧ¾Ú¤Î¥¿¥¤¥×¤Ï `any', `password', `kerberos', 'kerberos_v5', 
`gssapi', `cram-md5', `otp', `ntlm', `ssh` ¤Ç¤¹¡£
`password' ¥¿¥¤¥×¤ÏÉáÄ̤Υѥ¹¥ï¡¼¥ÉÁ÷¿®¤Ë¤è¤ëǧ¾Ú¤ò»ØÄꤷ¤Þ¤¹
(¥Ñ¥¹¥ï¡¼¥É¤Ï¥×¥ì¡¼¥ó¥Æ¥­¥¹¥È¤Î¤³¤È¤â¤¢¤ì¤Ð¡¢
APOP ¤Î¤è¤¦¤Ë¥×¥í¥È¥³¥ë¸ÇÍ­¤Î°Å¹æ²½¤¬¤µ¤ì¤Æ¤¤¤ë¤³¤È¤â¤¢¤ê¤Þ¤¹)¡£
`kerberos' ¤ò»ØÄꤹ¤ë¤È¥Ñ¥¹¥ï¡¼¥Éǧ¾Ú¤Ï¹Ô¤ï¤ì¤º¡¢
\fIfetchmail\fR ¤Ï¤½¤ì¤¾¤ì¤ÎÌ䤤¹ç¤ï¤»¤Î³«»Ï»þ¤Ë Kerberos ¤Î¥Á¥±¥Ã¥È¤ò¼èÆÀ¤·¡¢
¥Ñ¥¹¥ï¡¼¥É¤È¤·¤ÆǤ°Õ¤Îʸ»úÎó¤òÁ÷¿®¤·¤è¤¦¤È¤·¤Þ¤¹¡£
`gssapi' ¤ò»ØÄꤹ¤ë¤È fetchmail ¤Ï GSSAPI ǧ¾Ú¤ò»È¤¤¤Þ¤¹¡£
¤µ¤é¤Ë¾Ü¤·¤¤¾ðÊó¤Ë¤Ä¤¤¤Æ¤Ï `auth' ¥­¡¼¥ï¡¼¥É¤ÎÀâÌÀ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
.PP
.\"O Specifying `kpop' sets POP3 protocol over port 1109 with Kerberos V4
.\"O authentication.  These defaults may be overridden by later options.
`kpop' ¤ò»ØÄꤹ¤ë¤È¡¢1109 È֥ݡ¼¥È¾å¤Ç
Kerberos V4 ǧ¾Ú¤ò»È¤¦ POP3 ¥×¥í¥È¥³¥ë¤¬ÀßÄꤵ¤ì¤Þ¤¹¡£
¤³¤ì¤é¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤϡ¢¸å¤Ë¸½¤ï¤ì¤ë¥ª¥×¥·¥ç¥ó¤Ë¤è¤Ã¤Æ¾å½ñ¤­¤µ¤ì¤Þ¤¹¡£
.PP
.\"O There are currently four global option statements; `set logfile'
.\"O followed by a string sets the same global specified by --logfile.  A
.\"O command-line --logfile option will override this.  Also, `set daemon'
.\"O sets the poll interval as --daemon does.  This can be overridden by a
.\"O command-line --daemon option; in particular --daemon 0 can be used to
.\"O force foreground operation. The `set postmaster' statement sets the
.\"O address to which multidrop mail defaults if there are no local
.\"O matches.  Finally, `set syslog' sends log messages to syslogd(8).
¥°¥í¡¼¥Ð¥ë¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ëʸ¤Ï¸½ºß 4 ¤Ä¤¢¤ê¤Þ¤¹¡£
`set logfile' ¤Î¸å¤Ëʸ»úÎó¤òµ­½Ò¤·¤¿¤â¤Î¤Ï¡¢
--logfile ¥ª¥×¥·¥ç¥ó¤Î»ØÄê¤ÈƱ¤¸¥°¥í¡¼¥Ð¥ë¤ÊÀßÄê¤ò¹Ô¤¤¤Þ¤¹¡£
¥³¥Þ¥ó¥É¥é¥¤¥ó¤Î --logfile ¤Ï¤³¤ì¤ò¾å½ñ¤­¤·¤Þ¤¹¡£
¤Þ¤¿ `set daemon' ¤Ï¡¢--daemon ¥ª¥×¥·¥ç¥ó¤ÈƱ¤¸¤è¤¦¤Ë
¥Ý¡¼¥ê¥ó¥°´Ö³Ö¤òÀßÄꤷ¤Þ¤¹¡£
¤³¤ì¤Ï¥³¥Þ¥ó¥É¥é¥¤¥ó¤Î --daemon ¥ª¥×¥·¥ç¥ó¤Ç¾å½ñ¤­¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
ÆÃÎã¤È¤·¤Æ¡¢--daemon 0 ¤ò»È¤Ã¤Æ¡¢
¶¯À©Åª¤Ë¥Õ¥©¥¢¥°¥é¥¦¥ó¥ÉÆ°ºî¤ò¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
`set postmater' ʸ¤Ï¡¢¥í¡¼¥«¥ë¤Ç°ìÃפ¹¤ë¤â¤Î¤¬¤Ê¤¤¾ì¹ç¤Ë
¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¤¬¥Ç¥Õ¥©¥ë¥È¤ÇÁ÷¤é¤ì¤ë¥¢¥É¥ì¥¹¤òÀßÄꤷ¤Þ¤¹¡£
ºÇ¸å¤Ë¡¢`set syslog' ¤ò»ØÄꤹ¤ë¤È¥í¥°¥á¥Ã¥»¡¼¥¸¤¬ syslogd(8) ¤Ë
Á÷¤é¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

.\"O .SH INTERACTION WITH RFC 822
.SH RFC 822 ¤È¤ÎÁê¸ßºîÍÑ
.\"O When trying to determine the originating address of a message,
.\"O fetchmail looks through headers in the following order: 
¥á¥Ã¥»¡¼¥¸¤ÎÁ÷¿®¥¢¥É¥ì¥¹¤ò·è¤á¤è¤¦¤È¤¹¤ë¤È¤­¡¢
fetchmail ¤Ï°Ê²¼¤Î½ç¤Ç¥Ø¥Ã¥À¤ò»²¾È¤·¤Æ¹Ô¤­¤Þ¤¹:

        Return-Path:
.\"O         Resent-Sender: (ignored if it doesn't contain an @ or !)
.\"O         Sender: (ignored if it doesn't contain an @ or !)
        Resent-Sender: (@ ¤Þ¤¿¤Ï ! ¤ò´Þ¤ó¤Ç¤¤¤Ê¤¤¾ì¹ç¤Ï̵»ë¤µ¤ì¤ë)
        Sender: (@ ¤Þ¤¿¤Ï ! ¤ò´Þ¤ó¤Ç¤¤¤Ê¤¤¾ì¹ç¤Ï̵»ë¤µ¤ì¤ë)
        Resent-From:
        From:
        Reply-To:
        Apparently-From:

.\"O The originating address is used for logging, and to set the MAIL FROM
.\"O address when forwarding to SMTP.  This order is intended to cope
.\"O gracefully with receiving mailing list messages in multidrop mode. The
.\"O intent is that if a local address doesn't exist, the bounce message
.\"O won't be returned blindly to the author or to the list itself, but
.\"O rather to the list manager (which is less annoying).
Á÷¿®¥¢¥É¥ì¥¹¤Ï¥í¥°¤Îµ­Ï¿¤È¡¢
SMTP ¤ËžÁ÷¤¹¤ë»þ¤Î MAIL FROM ¥¢¥É¥ì¥¹¤ÎÀßÄê¤Î¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£
¤³¤Î½ç½ø¤Ï¥Þ¥ë¥Á¥É¥í¥Ã¥×¥â¡¼¥É¤Ç¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Î¼õ¿®¤ò
¤¦¤Þ¤¯½èÍý¤¹¤ë¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£
¤½¤ÎÌÜŪ¤Ï¡¢¥í¡¼¥«¥ë¥¢¥É¥ì¥¹¤¬Â¸ºß¤·¤Ê¤¤¾ì¹ç¤Ë¡¢
º¹¤·Ìᤷ¥á¥Ã¥»¡¼¥¸¤¬¥á¡¼¥ë¤ò½Ð¤·¤¿¿Í¤ä¥á¡¼¥ê¥ó¥°¥ê¥¹¥ÈËÜÂΤˤà¤ä¤ß¤ËÊÖ¤µ¤ì¤º¡¢
¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Î´ÉÍý¼Ô¤ËÆϤ¯¤è¤¦¤Ë¤¹¤ë¤³¤È¤Ç¤¹
(¤³¤Á¤é¤ÎÊý¤¬¤Þ¤À¥Þ¥·¤Ç¤¹)¡£

.\"O In multidrop mode, destination headers are processed as follows:
.\"O First, fetchmail looks for the Received: header (or whichever one is
.\"O specified by the `envelope' option) to determine the local
.\"O recipient address. If the mail is addressed to more than one recipient,
.\"O the Received line won't contain any information regarding recipient addresses.
¥Þ¥ë¥Á¥É¥í¥Ã¥×¥â¡¼¥É¤Ç¤Ï¡¢°¸Àè¤Î¥Ø¥Ã¥À¤Ï°Ê²¼¤Î¤è¤¦¤Ë½èÍý¤µ¤ì¤Þ¤¹: 
ºÇ½é¤Ë¡¢fetchmail ¤Ï Received: ¥Ø¥Ã¥À
(¤¢¤ë¤¤¤Ï¡¢`envelope' ¤Ç»ØÄꤷ¤¿Ç¤°Õ¤Î¥Ø¥Ã¥À) ¤òõ¤·¡¢
¥í¡¼¥«¥ë¤Î¼õ¿®¼Ô¥¢¥É¥ì¥¹¤ò·è¤á¤Þ¤¹¡£
¤â¤·¥á¡¼¥ë¤¬Ê£¿ô¤Î¼õ¿®¼Ô¤Ë°¸¤Æ¤¿¤â¤Î¤Ç¤¢¤ì¤Ð¡¢
Received ¤Ï¼õ¿®¼Ô¤Î¥¢¥É¥ì¥¹¤È¤¤¤¦ÅÀ¤Ç¤ÏÁ´¤¯¾ðÊó¤ò»ý¤Ã¤Æ¤¤¤Ê¤¤¤Ç¤·¤ç¤¦¡£

.\"O Then fetchmail looks for the Resent-To:, Resent-Cc:, and Resent-Bcc:
.\"O lines.  If they exists, they should contain the final recipients and
.\"O have precedence over their To:/Cc:/Bcc: counterparts.  If the Resent-*
.\"O lines doesn't exist, the To:, Cc:, Bcc: and Apparently-To: lines are
.\"O looked for. (The presence of a Resent-To: is taken to imply that the
.\"O person referred by the To: address has already received the original
.\"O copy of the mail).
¼¡¤Ë¡¢fetchmail ¤Ï Resent-To:, Resent-Cc:, Resent-Bcc: ¹Ô¤òõ¤·¤Þ¤¹¡£
¤³¤ì¤é¤Î¥Ø¥Ã¥À¤¬Â¸ºß¤¹¤ë¾ì¹ç¡¢¤³¤ì¤é¤Ë¤ÏºÇ½ªÅª¤Ê¼õ¿®¼Ô¤¬½ñ¤«¤ì¤Æ¤ª¤ê¡¢
ÂФˤʤäƤ¤¤ë To:/Cc:/Bcc: ¤è¤ê¤âÍ¥À褵¤ì¤Þ¤¹¡£
¤â¤· Resent-* ¹Ô¤¬Â¸ºß¤·¤Ê¤±¤ì¤Ð¡¢
To:, Cc:, Bcc:, Apparently-To: ¹Ô¤¬Ãµ¤µ¤ì¤Þ¤¹¡£
(Resent-To: ¤¬¤¢¤ë¤È¡¢To: ¥¢¥É¥ì¥¹¤¬»Ø¤·¤Æ¤¤¤ë¿Íʪ¤Ï
´û¤Ë¤½¤Î¥á¡¼¥ë¤Î¥³¥Ô¡¼¤ò¼õ¤±¼è¤Ã¤Æ¤¤¤ë¤â¤Î¤È¹Í¤¨¤é¤ì¤Þ¤¹¡£)

.\"O .SH CONFIGURATION EXAMPLES
.SH ÀßÄêÎã
.\"O Note that although there are password declarations in a good many
.\"O of the examples below, this is mainly for illustrative purposes.
.\"O We recommend stashing account/password pairs in your $HOME/.netrc
.\"O file, where they can be used not just by fetchmail but by ftp(1) and
.\"O other programs.
°Ê²¼¤Î¿¤¯¤ÎÎã¤Ç¤Ï¡¢password Àë¸À¤¬¤¢¤ë¤¬¡¢
¤³¤ì¤Ï¼ç¤ËÎ㼨¤Î¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£
¥¢¥«¥¦¥ó¥È/¥Ñ¥¹¥ï¡¼¥É¤Î¥Ú¥¢¤ò $HOME/.netrc ¥Õ¥¡¥¤¥ë¤Ë
±£¤·¤Æ¤ª¤¯¤³¤È¤ò¤ª´«¤á¤·¤Þ¤¹¡£
¤³¤Î¥Õ¥¡¥¤¥ë¤Ï fetchmail ¤À¤±¤Ç¤Ê¤¯ ftp(1) ¤ä¤½¤Î¾¤Î¥×¥í¥°¥é¥à¤Ç¤â
»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

.\"O Basic format is:
´ðËÜ¥Õ¥©¡¼¥Þ¥Ã¥È¤ò°Ê²¼¤Ë¼¨¤·¤Þ¤¹:

.nf
  poll SERVERNAME protocol PROTOCOL username NAME password PASSWORD 
.fi
.PP
.\"O Example:
Îã:

.nf
  poll pop.provider.net protocol pop3 username "jsmith" password "secret1"
.fi
.PP
.\"O Or, using some abbreviations:
¾Êά·Á¤ò»È¤¨¤ë¤â¤Î¤â¤¢¤ê¤Þ¤¹:

.nf
  poll pop.provider.net proto pop3 user "jsmith" password "secret1"
.fi
.PP
.\"O Multiple servers may be listed:
Ê£¿ô¤Î¥µ¡¼¥Ð¤òʤ٤뤳¤È¤¬¤Ç¤­¤Þ¤¹:

.nf
  poll pop.provider.net proto pop3 user "jsmith" pass "secret1"
  poll other.provider.net proto pop2 user "John.Smith" pass "My^Hat"
.fi

.\"O Here's a version of those two with more whitespace and some noise words: 
¾åµ­¤Î 2 ¤Ä¤ÎÎã¤Ë¤Ä¤¤¤Æ¡¢¶õÇòʸ»ú¤È¥Î¥¤¥º¥ï¡¼¥É¤ò¤¤¤¯¤Ä¤«Áý¤ä¤·¤¿¤â¤Î
¤ò¼¨¤·¤Þ¤¹:

.nf
  poll pop.provider.net proto pop3
      user "jsmith", with password secret1, is "jsmith" here;
  poll other.provider.net proto pop2:
      user "John.Smith", with password "My^Hat", is "John.Smith" here;
.fi

.\"O This version is much easier to read and doesn't cost significantly
.\"O more (parsing is done only once, at startup time).
¤³¤¦½ñ¤¤¤¿Êý¤¬¤º¤Ã¤ÈÆɤߤ䤹¤¤¤Ç¤¹¤¬¡¢½èÍý¤Î¼ê´Ö¤Ï¤½¤ó¤Ê¤Ë¤«¤«¤ê¤Þ¤»¤ó
(µ¯Æ°»þ¤Ë°ìÅÙ¹Ô¤ï¤ì¤ë¤À¤±¤Ç¤¹)¡£

.PP
.\"O If you need to include whitespace in a parameter string, enclose the
.\"O string in double quotes.  Thus:
¥Ñ¥é¥á¡¼¥¿Ê¸»úÎó¤Ë¶õÇòʸ»ú¤ò´Þ¤á¤ëɬÍפ¬¤¢¤ë¾ì¹ç¤Ë¤Ï¡¢
ʸ»úÎó¤ò¥À¥Ö¥ë¥¯¥©¡¼¥È¤Ç°Ï¤ß¤Þ¤·¤ç¤¦¡£
°Ê²¼¤Î¤è¤¦¤Ê·Á¤Ç¤¹:

.nf
  poll mail.provider.net with proto pop3:
        user "jsmith" there has password "u can't krak this"
                    is jws here and wants mda "/bin/mail"
.fi

.\"O You may have an initial server description headed by the keyword
.\"O `defaults' instead of `poll' followed by a name.  Such a record
.\"O is interpreted as defaults for all queries to use. It may be overwritten
.\"O by individual server descriptions.  So, you could write:
ºÇ½é¤Î¥µ¡¼¥Ðµ­½Ò¤Ç¤Ï¡¢Ì¾Á°¤ÎÁ°¤Ë¥­¡¼¥ï¡¼¥É `poll' ¤Ç¤Ï¤Ê¤¯¡¢
¥­¡¼¥ï¡¼¥É`defaults' ¤òÃÖ¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤Î¤è¤¦¤Ê¥ì¥³¡¼¥É¤Ï¡¢
Á´¤Æ¤ÎÌ䤤¹ç¤ï¤»¤Ç»È¤ï¤ì¤ë¥Ç¥Õ¥©¥ë¥ÈÃͤȤ·¤Æ²ò¼á¤µ¤ì¤Þ¤¹¡£
¤³¤ì¤Ï¸ÄÊ̤Υµ¡¼¥Ðµ­½Ò¤Ç¾å½ñ¤­¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤Ä¤Þ¤ê¡¢°Ê²¼¤Î¤è¤¦¤Ë½ñ¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹:

.nf
  defaults proto pop3
        user "jsmith"
  poll pop.provider.net
        pass "secret1"
  poll mail.provider.net
        user "jjsmith" there has password "secret2"
.fi

.\"O It's possible to specify more than one user per server (this is only
.\"O likely to be useful when running fetchmail in daemon mode as root).
.\"O The `user' keyword leads off a user description, and every user specification
.\"O in a multi-user entry must include it.  Here's an example:
¥µ¡¼¥Ð¤´¤È¤ËÊ£¿ô¤Î¥æ¡¼¥¶¤ò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹
(¤³¤ì¤¬Ìò¤ËΩ¤Ä¤Î¤Ï¿ʬ¡¢
root ¤¬¥Ç¡¼¥â¥ó¥â¡¼¥É¤Ç fetchmail ¤ò¼Â¹Ô¤¹¤ë¤È¤­¤À¤±¤Ç¤·¤ç¤¦)¡£
1 ¿Í¤Î¥æ¡¼¥¶µ­½Ò¤Ï `user' ¥­¡¼¥ï¡¼¥É¤Ç»Ï¤Þ¤ê¡¢
¥æ¡¼¥¶¥¨¥ó¥È¥ê¤¬Ê£¿ô¤¢¤ë¾ì¹ç¤Ë¤Ï¡¢
¤³¤Î¥­¡¼¥ï¡¼¥É¤¬¥æ¡¼¥¶»ØÄꤽ¤ì¤¾¤ì¤Ë´Þ¤Þ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
°Ê²¼¤ËÎã¤ò¼¨¤·¤Þ¤¹:

.nf
  poll pop.provider.net proto pop3 port 3111
        user "jsmith" with pass "secret1" is "smith" here
        user jones with pass "secret2" is "jjones" here keep
.fi

.\"O This associates the local username `smith' with the pop.provider.net
.\"O username `jsmith' and the local username `jjones' with the
.\"O pop.provider.net username `jones'.  Mail for `jones' is kept on the
.\"O server after download.
¤³¤ì¤Ï¡¢¥í¡¼¥«¥ë¤Î¥æ¡¼¥¶Ì¾ `smith' ¤ò
the pop.provider.net ¤Î¥æ¡¼¥¶Ì¾ `jsmith' ¤ËÂбþ¤µ¤»¡¢
¥í¡¼¥«¥ë¤Î¥æ¡¼¥¶Ì¾ `jjones' ¤ò
pop.provider.net ¤Î¥æ¡¼¥¶Ì¾ `jones' ¤ËÂбþ¤µ¤»¤Þ¤¹¡£
`jones' ¤Î¥á¡¼¥ë¤Ï¥À¥¦¥ó¥í¡¼¥É¸å¤â¥µ¡¼¥Ð¡¼¤Ë»Ä¤µ¤ì¤Þ¤¹¡£
.PP
.\"O Here's what a simple retrieval configuration for a multi-drop mailbox
.\"O looks like:
¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¥Ü¥Ã¥¯¥¹ÍѤμèÆÀ¤ò¹Ô¤¦´Êñ¤ÊÀßÄ꤬¤É¤ó¤Ê´¶¤¸¤«¤ò
°Ê²¼¤Ë¼¨¤·¤Þ¤¹:

.nf
  poll pop.provider.net:
        user maildrop with pass secret1 to golux 'hurkle'='happy' snark here
.fi

.\"O This says that the mailbox of account `maildrop' on the server is a
.\"O multi-drop box, and that messages in it should be parsed for the
.\"O server user names `golux', `hurkle', and `snark'.  It further
.\"O specifies that `golux' and `snark' have the same name on the
.\"O client as on the server, but mail for server user `hurkle' should be
.\"O delivered to client user `happy'.
¤³¤ì¤Ï¡¢¥µ¡¼¥Ð¾å¤Î¥¢¥«¥¦¥ó¥È `maildrop' ¤¬¥Þ¥ë¥Á¥É¥í¥Ã¥×¥Ü¥Ã¥¯¥¹¤Ç¤¢¤ê¡¢
¤½¤ÎÃæ¤Î¥á¥Ã¥»¡¼¥¸¤Ï¥µ¡¼¥Ð¤Î¥æ¡¼¥¶Ì¾ `golux', `hurkle', `snark' ¤ËÂФ·¤Æ
Ÿ³«¤¹¤ë¤È¤¤¤¦»ØÄê¤Ç¤¹¡£
¤³¤ì¤Ï¤µ¤é¤Ë¡¢`golux' ¤È `snark' ¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Ç¤â
¥µ¡¼¥Ð¤ÈƱ¤¸Ì¾Á°¤ò»ý¤Ä¤±¤ì¤É¡¢
¥µ¡¼¥Ð¤Î¥æ¡¼¥¶ `hurkle' °¸¤Î¥á¡¼¥ë¤Ï
¥¯¥é¥¤¥¢¥ó¥È¤Î¥æ¡¼¥¶ `happy' ¤ËÇÛÁ÷¤¹¤ë¤³¤È¤â»ØÄꤷ¤Þ¤¹¡£
.PP
.\"O Here's an example of another kind of multidrop connection:
Ê̤μïÎà¤Î¥Þ¥ë¥Á¥É¥í¥Ã¥×Àܳ¤ÎÎã¤ò¼¨¤·¤Þ¤¹:

.nf
  poll pop.provider.net localdomains loonytoons.org toons.org:
        user maildrop with pass secret1 to * here
.fi

.\"O This also says that the mailbox of account `maildrop' on the server is
.\"O a multi-drop box.  It tells fetchmail that any address in the
.\"O loonytoons.org or toons.org domains (including subdomain addresses like
.\"O `joe@daffy.loonytoons.org') should be passed through to the local SMTP
.\"O listener without modification.  Be careful of mail loops if you do this!
¤³¤ì¤â¡¢¥µ¡¼¥Ð¾å¤Î¥¢¥«¥¦¥ó¥È `maildrop' ¤¬
¥Þ¥ë¥Á¥É¥í¥Ã¥×¥Ü¥Ã¥¯¥¹¤Ç¤¢¤ë¤³¤È¤ò»ØÄꤷ¤Þ¤¹¡£
¤³¤ì¤Ï fetchmail ¤ËÂФ·¡¢
loonytoons.org ¤ä toons.org ¥É¥á¥¤¥óÆâ¤Î¥¢¥É¥ì¥¹Á´¤Æ
(`joe@daffy.loonytoons.org' ¤Î¤è¤¦¤Ê¥µ¥Ö¥É¥á¥¤¥ó¤Î¥¢¥É¥ì¥¹¤â´Þ¤ß¤Þ¤¹) ¤Ï
Êѹ¹¤»¤º¤Ë¥í¡¼¥«¥ë¤Î SMTP ¥ê¥¹¥Ê¤ØÅϤ¹¤³¤È¤ò»Ø¼¨¤·¤Þ¤¹¡£
¤³¤ì¤ò¹Ô¤¦¤È¤­¤Ë¤Ï¥á¡¼¥ë¤Î¥ë¡¼¥×¤Ë¤ÏÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤!
.PP
.\"O Here's an example configuration using ssh and the plugin option.  The
.\"O queries are made directly on the stdin and stdout of imapd via ssh.
.\"O Note that in this setup, IMAP authentication can be skipped.
ssh ¤È plugin ¥ª¥×¥·¥ç¥ó¤òÍѤ¤¤¿°ì¤Ä¤ÎÀßÄêÎã¤ò¼¨¤·¤Þ¤¹¡£
Ì䤤¹ç¤ï¤»¤Ï¡¢ssh ¤ò·Ðͳ¤·¤Æ¡¢imapd ¤Îɸ½àÆþÎϤÈɸ½à½ÐÎϤÇľÀܹԤï¤ì¤Þ¤¹¡£
¤³¤ÎÀßÄê¤Ç¤Ï IMAP ǧ¾Ú¤¬Èô¤Ð¤µ¤ì¤ë¤³¤È¤ËÃí°Õ¤·¤Æ²¼¤µ¤¤¡£

.nf
poll mailhost.net with proto imap:
        plugin "ssh %h /usr/sbin/imapd" auth ssh;
        user esr is esr here
.fi

.\"O .SH THE USE AND ABUSE OF MULTIDROP MAILBOXES
.SH ¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤ÎÎɤ¤»È¤¤Êý¤ÈÎɤ¯¤Ê¤¤»È¤¤Êý
.\"O Use the multiple-local-recipients feature with caution -- it can bite.
.\"O All multidrop features are ineffective in ETRN and ODMR modes.
¥í¡¼¥«¥ë¤Î¼õ¿®¼Ô¤òÊ£¿ô»ý¤Äµ¡Ç½¤ÏÃí°Õ¤·¤Æ»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
Äˤ¤Ìܤò¸«¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
ETRN ¤È ODMR ¥â¡¼¥É¤Ç¤Ï¥Þ¥ë¥Á¥É¥í¥Ã¥×µ¡Ç½¤ÏÁ´¤¯»È¤¨¤Ê¤¤ÅÀ¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

.\"O Also, note that in multidrop mode duplicate mails are suppressed.  A
.\"O piece of mail is considered duplicate if it has the same message-ID as
.\"O the message immediately preceding and more than one addressee.  Such
.\"O runs of messages may be generated when copies of a message addressed
.\"O to multiple users are delivered to a multidrop box.
¤Þ¤¿¡¢¥Þ¥ë¥Á¥É¥í¥Ã¥×¥â¡¼¥É¤Ç¤ÏÊ£À½¤µ¤ì¤¿¥á¡¼¥ë¤Ï
¾Ã¤µ¤ì¤ëÅÀ¤Ë¤âÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
¤¢¤ë¥á¡¼¥ë¤¬Ê£À½¤µ¤ì¤Æ¤¤¤ë¤ÈȽÃǤµ¤ì¤ë¤Î¤Ï¡¢
ľÁ°¤Î¥á¥Ã¥»¡¼¥¸¤ÈƱ¤¸¥á¥Ã¥»¡¼¥¸ ID ¤¬ÉÕ¤¤¤Æ¤¤¤Æ¡¢
Ê£¿ô¤Î¥¢¥É¥ì¥¹¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ç¤¹¡£
¤³¤Î¤è¤¦¤Ë¥á¥Ã¥»¡¼¥¸¤¬Ï¢Â³¤¹¤ë¤³¤È¤Ï¡¢
Ê£¿ô¤Î¥æ¡¼¥¶°¸¤Î 1 Ä̤Υ᡼¥ë¤Î¥³¥Ô¡¼¤¬
1 ¤Ä¤Î¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤ËÇÛÁ÷¤µ¤ì¤¿»þ¤Ëµ¯¤³¤ê¤Þ¤¹¡£

.\"O .SS Header vs. Envelope addresses 
.SS ¥Ø¥Ã¥ÀÂÐ envelope ¥¢¥É¥ì¥¹
.\"O The fundamental problem is that by having your mailserver toss several
.\"O peoples' mail in a single maildrop box, you may have thrown away
.\"O potentially vital information about who each piece of mail was
.\"O actually addressed to (the `envelope address', as opposed to the
.\"O header addresses in the RFC822 To/Cc/Bcc headers).  This `envelope
.\"O address' is the address you need in order to reroute mail properly.
´ðËÜŪ¤ÊÌäÂê¤Ï¡¢¥á¡¼¥ë¥µ¡¼¥Ð¤ËÊ£¿ô¤Î¥æ¡¼¥¶¤Î¥á¡¼¥ë¤ò
1 ¤Ä¤Î¥á¡¼¥ë¥É¥í¥Ã¥×¤ØÅꤲ¤µ¤»¤ë¤³¤È¤Ë¤è¤ê¡¢
¤½¤ì¤¾¤ì¤Î¥á¡¼¥ë¤¬¼ÂºÝ¤ËÆϤ±¤é¤ì¤Æ¤¤¤¿¥æ¡¼¥¶¤Ë´Ø¤¹¤ë¡¢
¤â¤·¤«¤¹¤ë¤ÈÈó¾ï¤Ë½ÅÍפ«¤â¤·¤ì¤Ê¤¤¾ðÊó
(`envelope ¥¢¥É¥ì¥¹', RFC822 ¤Î To/Cc/Bcc ¥Ø¥Ã¥À¤È¤ÏÂÐΩ¤¹¤ë¤â¤Î¤Ç¤¹) ¤ò
¼Î¤Æ¤Æ¤·¤Þ¤¦²ÄǽÀ­¤¬¤¢¤ë¤³¤È¤Ç¤¹¡£
¤³¤Î `envelope ¥¢¥É¥ì¥¹' ¤Ï¡¢
¥á¡¼¥ë¤òŬÀڤ˿¶¤êʬ¤±¤ë¤¿¤á¤ËɬÍפʥ¢¥É¥ì¥¹¤Ç¤¹¡£
.PP
.\"O Sometimes 
.\"O .I fetchmail
.\"O can deduce the envelope address.  If the mailserver MTA is
.\"O .I sendmail
.\"O and the item of mail had just one recipient, the MTA will have written
.\"O a `by/for' clause that gives the envelope addressee into its Received
.\"O header. But this doesn't work reliably for other MTAs, nor if there is
.\"O more than one recipient.  By default, \fIfetchmail\fR looks for
.\"O envelope addresses in these lines; you can restore this default with
.\"O -E "Received" or \&`envelope Received'.
.I fetchmail
¤¬ envelope ¥¢¥É¥ì¥¹¤ò¿äÄê¤Ç¤­¤ë¤³¤È¤â»þ¡¹¤¢¤ê¤Þ¤¹¡£
¥á¡¼¥ë¥µ¡¼¥Ð¤Î MTA ¤¬
.I sendmail
¤Ç¤¢¤ê¡¢¥á¡¼¥ë¤Î¼õ¿®¼Ô¤¬ 1 ¿Í¤·¤«¤¤¤Ê¤¤¾ì¹ç¡¢MTA ¤Ï envelope ¥¢¥É¥ì¥¹¤ò
Received ¥Ø¥Ã¥À¤ËÍ¿¤¨¤ë `by/for' ¤Î¹à¤ò½ñ¤¤¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¡£
¤·¤«¤·¡¢¤³¤ì¤Ï¾¤Î MTA ¤Ç¤â³Î¼Â¤ËÆ°ºî¤¹¤ë¤È¤Ï¸À¤¨¤Þ¤»¤ó¤·¡¢
Ê£¿ô¤Î¼õ¿®¼Ô¤¬¤¤¤ë¾ì¹ç¤Ë¤âÆ°ºî¤·¤Þ¤»¤ó¡£
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢\fIfetchmail\fR ¤Ï¤³¤ì¤é¤Î¹Ô¤Ç envelope ¥¢¥É¥ì¥¹¤òõ¤·¤Þ¤¹¡£
-E "Received" ¤Þ¤¿¤Ï \&`envelope Received' ¤ò»ØÄꤹ¤ë¤È
Æ°ºî¤ò¤³¤Î¥Ç¥Õ¥©¥ë¥È¤ËÌ᤹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.PP
.\"O Alternatively, some SMTP listeners and/or mail servers insert a header
.\"O in each message containing a copy of the envelope addresses.  This
.\"O header (when it exists) is often `X-Envelope-To'.  Fetchmail's
.\"O assumption about this can be changed with the -E or `envelope' option.
.\"O Note that writing an envelope header of this kind exposes the names of
.\"O recipients (including blind-copy recipients) to all receivers of the
.\"O messages; it is therefore regarded by some administrators as a
.\"O security/privacy problem.
¤³¤ì¤ò¹Ô¤¦Âå¤ï¤ê¤Ë¡¢°ìÉô¤Î SMTP ¥ê¥¹¥Ê¤ä¥á¡¼¥ë¥µ¡¼¥Ð¤Ï¡¢
envelope ¥¢¥É¥ì¥¹¤Î¥³¥Ô¡¼¤ò»ý¤Ä¥Ø¥Ã¥À¤ò³Æ¥á¥Ã¥»¡¼¥¸¤ËÁÞÆþ¤·¤Þ¤¹¡£
¤³¤Î¥Ø¥Ã¥À¤Ï (¸ºß¤¹¤ë¤Ê¤é¤Ð) `X-Envelope-To' ¤Î¤³¤È¤¬¤è¤¯¤¢¤ê¤Þ¤¹¡£
-E ¥ª¥×¥·¥ç¥ó¤Þ¤¿¤Ï `envelope' ¥ª¥×¥·¥ç¥ó¤òÍѤ¤¤ë¤È¡¢
fetchmail ¤¬ÁÛÄꤹ¤ë¥Ø¥Ã¥À¤òÊѹ¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤³¤Î¼ïÎà¤Î envelope ¥Ø¥Ã¥À¤ò½ñ¤¯¤È¡¢(¥Ö¥é¥¤¥ó¥É¥³¥Ô¡¼¤Î¼õ¿®¼Ô¤â´Þ¤á¤¿)
Á´¤Æ¤Î¼õ¿®¼Ô¤Î̾Á°¤¬¥á¥Ã¥»¡¼¥¸¼õ¿®¼Ô¤ËÌÀ¤é¤«¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
¤·¤¿¤¬¤Ã¤Æ¡¢¤³¤ì¤ò¥»¥­¥å¥ê¥Æ¥£/¥×¥é¥¤¥Ð¥·¡¼¤ÎÌäÂê¤Ç¤¢¤ë¤È
¹Í¤¨¤ë¥·¥¹¥Æ¥à´ÉÍý¼Ô¤â¤¤¤Þ¤¹¡£
.PP
.\"O A slight variation of the `X-Envelope-To' header is the `Delivered-To' put
.\"O by qmail to avoid mail loops. It will probably prefix the user name with a
.\"O string that normally matches the user's domain. To remove this prefix you
.\"O can use the -Q or `qvirtual' option.
`X-Envelope-To' ¤ò¾¯¤·ÊѤ¨¤¿¤â¤Î¤¬¡¢
qmail ¤¬¥á¡¼¥ë¤Î¥ë¡¼¥×¤òÈò¤±¤ë¤¿¤á¤ËÄɲ乤ë `Delivered-To' ¥Ø¥Ã¥À¤Ç¤¹¡£
¤³¤ì¤Ï¡¢Ä̾ï¤Ï¥æ¡¼¥¶¤Î¥É¥á¥¤¥ó¤Ë
¥Þ¥Ã¥Á¤¹¤ëʸ»úÎó¤ÎÁ°¤Ë¡¢¥æ¡¼¥¶Ì¾¤òÃÖ¤¤¤¿¤â¤Î¤Ç¤¢¤ë¤³¤È¤¬Â¿¤¤¤Ç¤¹¡£
¤³¤Î¥×¥ì¥Õ¥£¥Ã¥¯¥¹¤ò¼è¤ê½ü¤¯¤Ë¤Ï¡¢
-Q ¤Þ¤¿¤Ï `qvirtual' ¥ª¥×¥·¥ç¥ó¤ò»È¤¤¤Þ¤¹¡£
.PP
.\"O Sometimes, unfortunately, neither of these methods works.  When they
.\"O all fail, fetchmail must fall back on the contents of To/Cc/Bcc
.\"O headers to try to determine recipient addressees -- and these are not
.\"O reliable.  In particular, mailing-list software often ships mail with
.\"O only the list broadcast address in the To header.
»ÄÇ°¤Ê¤¬¤é¡¢¤³¤ì¤é¤¬Î¾Êý¤È¤â¤¦¤Þ¤¯Æ°ºî¤·¤Ê¤¤¤³¤È¤â¤¢¤ê¤Þ¤¹¡£
¤³¤ì¤é¤¬Á´¤Æ¼ºÇÔ¤·¤¿¾ì¹ç¡¢fetchmail ¤Ï To/Cc/Bcc ¥Ø¥Ã¥À¤«¤é½Ðľ¤·¤Æ¡¢
¼õ¿®¼Ô¤Î¥¢¥É¥ì¥¹¤ò·è¤á¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¤¬¡¢¤³¤ì¤é¤Î¥Ø¥Ã¥À¤Ï¿®Íê¤Ç¤­¤Þ¤»¤ó¡£
Æäˡ¢¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Î¥½¥Õ¥È¥¦¥§¥¢¤¬
¥ê¥¹¥ÈÁ´ÂΤΥ¢¥É¥ì¥¹¤·¤« To ¥Ø¥Ã¥À¤ËÉÕ¤±¤Ê¤¤¤Ç¥á¡¼¥ë¤òÁ÷¤ë¤³¤È¤¬¤è¤¯¤¢¤ê¤Þ¤¹¡£
.PP
.\"O When
.\"O .I fetchmail
.\"O cannot deduce a recipient address that is local, and the intended
.\"O recipient address was anyone other than fetchmail's invoking user,
.\"O mail will get lost.  This is what makes the multidrop feature risky.
.I fetchmail
¤¬¥í¡¼¥«¥ë¤Î¼õ¿®¼Ô¥¢¥É¥ì¥¹¤ò¿äÄê¤Ç¤­¤º¡¢
¤«¤ÄËÜÍè¤Î¼õ¿®¼Ô¤Î¥¢¥É¥ì¥¹¤¬ fetchmail ¤ò¼Â¹Ô¤·¤¿¥æ¡¼¥¶°Ê³°¤Ç¤¢¤ë¾ì¹ç¡¢
¥á¡¼¥ë¤Ï̵¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¦¤Ç¤·¤ç¤¦¡£
¤³¤ì¤¬¥Þ¥ë¥Á¥É¥í¥Ã¥×µ¡Ç½¤ò´í¸±¤Ë¤·¤Æ¤¤¤ëÍ×°ø¤Ç¤¹¡£
.PP
.\"O A related problem is that when you blind-copy a mail message, the Bcc
.\"O information is carried \fIonly\fR as envelope address (it's not put
.\"O in the headers fetchmail can see unless there is an X-Envelope
.\"O header).  Thus, blind-copying to someone who gets mail over a
.\"O fetchmail link will fail unless the the mailserver host routinely
.\"O writes X-Envelope or an equivalent header into messages in your maildrop.
¤³¤ì¤Ë´ØÏ¢¤¹¤ëÌäÂê¤Ï¡¢¥á¡¼¥ë¤Î¥á¥Ã¥»¡¼¥¸¤ò¥Ö¥é¥¤¥ó¥É¥³¥Ô¡¼¤¹¤ë¤È¤­¡¢
Bcc ¾ðÊó¤Ï envelope ¥¢¥É¥ì¥¹¤È¤·¤Æ\fI¤Î¤ß\fRÅÁ¤¨¤é¤ì¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹
(X-Envelope ¥Ø¥Ã¥À¤¬¤Ê¤±¤ì¤Ð¡¢fetchmail ¤¬Æɤá¤ë¥Ø¥Ã¥À¤Ë¤Ï½ñ¤«¤ì¤Þ¤»¤ó)¡£
¤·¤¿¤¬¤Ã¤Æ¡¢¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥Û¥¹¥È¤¬¾ï¤Ë X-Envelope ¥Ø¥Ã¥À¤¢¤ë¤¤¤Ï¤³¤ì¤È
ƱÅù¤Î¥Ø¥Ã¥À¤ò¥á¡¼¥ë¥É¥í¥Ã¥×¤ËÆþ¤ì¤ë¥á¥Ã¥»¡¼¥¸¤Ë½ñ¤¯¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢
fetchmail ·Ðͳ¤Ç¥á¡¼¥ë¤ò¼èÆÀ¤¹¤ë¥æ¡¼¥¶°¸¤Î¥Ö¥é¥¤¥ó¥É¥³¥Ô¡¼¤Ï¼ºÇÔ¤·¤Þ¤¹¡£

.\"O .SS Good Ways To Use Multidrop Mailboxes
.SS ¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤ÎÎɤ¤»È¤¤Êý
.\"O Multiple local names can be used to administer a mailing list from the
.\"O client side of a \fIfetchmail\fR collection.  Suppose your name is
.\"O \&`esr', and you want to both pick up your own mail and maintain a mailing
.\"O list called (say) "fetchmail-friends", and you want to keep the alias
.\"O list on your client machine.
¥í¡¼¥«¥ë̾¤òÊ£¿ô»È¤¦¤³¤È¤Ë¤è¤ê¡¢\fIfetchmail\fR ¤Î¥¯¥é¥¤¥¢¥ó¥È¦¤«¤é
¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤ò´ÉÍý¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤¢¤Ê¤¿¤Î¥æ¡¼¥¶Ì¾¤¬ \&`esr' ¤Ç¤¢¤ê¡¢¼«Ê¬°¸¤Î¥á¡¼¥ë¤ò¼õ¤±¼è¤ë¤³¤È¤È
(Î㤨¤Ð) "fetchmail-friends" ¤È¤¤¤¦
̾Á°¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Î´ÉÍý¤òξÊý¤ä¤ê¤¿¤¤¤È¤·¤Þ¤¹¡£
¤½¤ì¤«¤é¡¢¤¢¤Ê¤¿¤Î¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¤Ç
¥¨¥¤¥ê¥¢¥¹¤Î¥ê¥¹¥È¤â´ÉÍý¤·¤¿¤¤¤â¤Î¤È¤·¤Þ¤¹¡£
.PP
.\"O On your server, you can alias \&`fetchmail-friends' to `esr'; then, in
.\"O your \fI.fetchmailrc\fR, declare \&`to esr fetchmail-friends here'.
.\"O Then, when mail including `fetchmail-friends' as a local address
.\"O gets fetched, the list name will be appended to the list of
.\"O recipients your SMTP listener sees.  Therefore it will undergo alias
.\"O expansion locally.  Be sure to include `esr' in the local alias
.\"O expansion of fetchmail-friends, or you'll never see mail sent only to
.\"O the list.  Also be sure that your listener has the "me-too" option set
.\"O (sendmail's -oXm command-line option or OXm declaration) so your name
.\"O isn't removed from alias expansions in messages you send.
¥µ¡¼¥Ð¤Ç¤Ï¡¢\&`fetchmail-friends' ¤ò `esr' ¤Ë
¥¨¥¤¥ê¥¢¥¹ÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤½¤ì¤«¤é¡¢\fI.fetchmailrc\fR ¤Ç¤Ï
\&`to esr fetchmail-friends here'¤òÀë¸À¤·¤Þ¤¹¡£
¤¹¤ë¤È¡¢`fetchmail-friends' ¤ò¥í¡¼¥«¥ë¥¢¥É¥ì¥¹¤È¤·¤Æ´Þ¤ó¤Ç¤¤¤ë
¥á¡¼¥ë¤¬¼èÆÀ¤µ¤ì¤¿¤È¤­¡¢
¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Î̾Á°¤¬ SMTP ¥ê¥¹¥Ê¤¬¸«¤Æ¤¤¤ë¼õ¿®¼Ô¤Î¥ê¥¹¥È¤ËÄɲ䵤ì¤Þ¤¹¡£
¤·¤¿¤¬¤Ã¤Æ¡¢¥¨¥¤¥ê¥¢¥¹¤ÎŸ³«¤Ï¥í¡¼¥«¥ë¤Ç¹Ô¤ï¤ì¤Þ¤¹¡£
ɬ¤º¡¢`esr' ¤ò fetchmail-friends ¤Î¥í¡¼¥«¥ë¤Î¥¨¥¤¥ê¥¢¥¹Å¸³«¤Ë´Þ¤á¤Æ¤¯¤À¤µ¤¤¡£
¤µ¤â¤Ê¤¤¤È¡¢¤³¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤À¤±¤¬°¸Àè¤Ë¤Ê¤Ã¤Æ¤¤¤ë
¥á¡¼¥ë¤òÀäÂФ˸«¤ë¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£
¤Þ¤¿¡¢¥ê¥¹¥Ê¤Î¡Ö¼«Ê¬¤Ë¤â¡×¤È¤¤¤¦¥ª¥×¥·¥ç¥ó¤òɬ¤º¥»¥Ã¥È¤·¤Æ
(sendmail ¤Ç¤Ï -oXm ¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤«¡¢OXm Àë¸À¤Ç¤¹)¡¢
¤¢¤Ê¤¿¤¬Á÷¤Ã¤¿¥á¥Ã¥»¡¼¥¸¤Î¥¨¥¤¥ê¥¢¥¹Å¸³«¤«¤é
¤¢¤Ê¤¿¤Î̾Á°¤¬ºï½ü¤µ¤ì¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
.PP
.\"O This trick is not without its problems, however.  You'll begin to see
.\"O this when a message comes in that is addressed only to a mailing list
.\"O you do \fInot\fR have declared as a local name.  Each such message
.\"O will feature an `X-Fetchmail-Warning' header which is generated
.\"O because fetchmail cannot find a valid local name in the recipient
.\"O addresses.  Such messages default (as was described above) to being
.\"O sent to the local user running
.\"O .IR fetchmail ,
.\"O but the program has no way to know that that's actually the right thing.
¤·¤«¤·¡¢¤³¤Î¥È¥ê¥Ã¥¯¤ËÌäÂ꤬¤Ê¤¤¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
¤¢¤Ê¤¿¤¬¥í¡¼¥«¥ë̾¤È¤·¤ÆÀë¸À¤·¤Æ
\fI¤¤¤Ê¤¤\fR¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤À¤±¤¬°¸Àè¤Ë¤Ê¤Ã¤Æ¤¤¤ë¥á¡¼¥ë¤¬Íè¤ë¤È¡¢
¤½¤ÎÌäÂ꤬ÌÀ¤é¤«¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
¤³¤Î¤è¤¦¤Ê¥á¥Ã¥»¡¼¥¸¤Î¤½¤ì¤¾¤ì¤Ë¤Ï¡¢
`X-Fetchmail-Warning' ¥Ø¥Ã¥À¤¬ÉÕ¤¤¤Æ¤¤¤Þ¤¹¡£
¤³¤Î¥Ø¥Ã¥À¤Ï¡¢fetchmail ¤¬¼õ¿®¼Ô¥¢¥É¥ì¥¹Ãæ¤Ç
Í­¸ú¤Ê¥í¡¼¥«¥ë̾¤ò¸«¤Ä¤±¤é¤ì¤Ê¤«¤Ã¤¿¤¿¤á¤ËÀ¸À®¤µ¤ì¤ë¤â¤Î¤Ç¤¹¡£
¤³¤Î¤è¤¦¤Ê¥á¥Ã¥»¡¼¥¸¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Ç (´û¤Ë½Ò¤Ù¤¿¤è¤¦¤Ë)
.IR fetchmail
¤ò¼Â¹Ô¤·¤Æ¤¤¤ë¥í¡¼¥«¥ë¥æ¡¼¥¶¤ËÁ÷¤é¤ì¤Þ¤¹¤¬¡¢
¤½¤ì¤¬ËÜÅö¤ËÀµ¤·¤¤½èÃ֤ʤΤ«¤ò¥×¥í¥°¥é¥à¦¤«¤éÃΤëÊýË¡¤Ï¤¢¤ê¤Þ¤»¤ó¡£

.\"O .SS Bad Ways To Abuse Multidrop Mailboxes
.SS ¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤ÎÎɤ¯¤Ê¤¤»È¤¤Êý
.\"O Multidrop mailboxes and 
.\"O .I fetchmail
.\"O serving multiple users in daemon mode do not mix.  The problem, again, is
.\"O mail from mailing lists, which typically does not have an individual
.\"O recipient address on it.   Unless 
.\"O .I fetchmail
.\"O can deduce an envelope address, such mail will only go to the account
.\"O running fetchmail (probably root).  Also, blind-copied users are very
.\"O likely never to see their mail at all.
¥Þ¥ë¥Á¥É¥í¥Ã¥×¥á¡¼¥ë¥Ü¥Ã¥¯¥¹¤È¡¢¥Ç¡¼¥â¥ó¥â¡¼¥É¤ÇÊ£¿ô¤Î¥æ¡¼¥¶¤Ë¥µ¡¼¥Ó¥¹¤ò¹Ô¤¦
.I fetchmail
¤òƱ»þ¤Ë»È¤Ã¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
·«¤êÊÖ¤·¤Þ¤¹¤¬¡¢¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤«¤é¤Î¥á¡¼¥ë¤ÇÌäÂ꤬µ¯¤³¤ê¤Þ¤¹¡£
¤³¤Î¤è¤¦¤Ê¥á¡¼¥ë¤Ë¤ÏÄ̾¼õ¿®¼Ô¸Ä¿Í¤Î¥¢¥É¥ì¥¹¤¬½ñ¤«¤ì¤Æ¤¤¤Ê¤¤¤Î¤Ç¤¹¡£
.I fetchmail
¤¬ envelope ¥¢¥É¥ì¥¹¤ò¿äÄê¤Ç¤­¤Ê¤±¤ì¤Ð¡¢¤³¤Î¤è¤¦¤Ê¥á¡¼¥ë¤Ï fetchmail
¤ò¼Â¹Ô¤·¤¿¥æ¡¼¥¶ (root ¤Ç¤¢¤ë¤³¤È¤¬Â¿¤¤¤Ç¤·¤ç¤¦) ¤Ë¤·¤«ÆϤ­¤Þ¤»¤ó¡£
¤Þ¤¿¡¢¥Ö¥é¥¤¥ó¥É¥³¥Ô¡¼¤Î°¸Àè¤Ë¤Ê¤Ã¤Æ¤¤¤ë¥æ¡¼¥¶¤Ï¤­¤Ã¤È¡¢
¤³¤Î¤è¤¦¤Ê¥á¡¼¥ë¤¬Á´¤¯Æɤá¤Ê¤¤¤Ç¤·¤ç¤¦¡£
.PP
.\"O If you're tempted to use 
.\"O .I fetchmail 
.\"O to retrieve mail for multiple users from a single mail drop via POP or
.\"O IMAP, think again (and reread the section on header and envelope
.\"O addresses above).  It would be smarter to just let the mail sit in the
.\"O mailserver's queue and use fetchmail's ETRN or ODMR modes to trigger
.\"O SMTP sends periodically (of course, this means you have to poll more
.\"O frequently than the mailserver's expiry period).  If you can't arrange
.\"O this, try setting up a UUCP feed.
¤â¤·¡¢
.I fetchmail 
¤ò»È¤Ã¤Æ 1 ¤Ä¤Î¥á¡¼¥ë¥É¥í¥Ã¥×¤«¤é POP ¤ä IMAP ·Ðͳ¤Ç
Ê£¿ô¥æ¡¼¥¶°¸¤Î¥á¡¼¥ë¤ò¼èÆÀ¤·¤è¤¦¤È¹Í¤¨¤Æ¤¤¤ë¤Ê¤é¤Ð¡¢¹Í¤¨Ä¾¤·¤Æ¤¯¤À¤µ¤¤
(¤½¤·¤Æ¡¢Á°½Ò¤Î¥Ø¥Ã¥À¤È envelope ¥¢¥É¥ì¥¹¤Ë´Ø¤¹¤ë
¥»¥¯¥·¥ç¥ó¤òÆɤßľ¤·¤Æ¤¯¤À¤µ¤¤)¡£
¥á¡¼¥ë¤Ïñ¤Ë¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥­¥å¡¼¤ËÆþ¤ì¤Æ¤ª¤­¡¢
fetchmail ¤Î ETRN ¤ä ODMR ¥â¡¼¥É¤ò»È¤Ã¤ÆÄê´üŪ¤Ë
SMTP ¤Ç¤ÎÁ÷¿®¤ò¹Ô¤ï¤»¤ëÊý¤¬¸­¤¤¤ä¤ê¤«¤¿¤Ç¤·¤ç¤¦
(¤³¤Î¾ì¹ç¤Ï¤â¤Á¤í¤ó¡¢¥á¡¼¥ë¥µ¡¼¥Ð¤Ç¤Î¥á¡¼¥ë¤ÎÍ­¸ú´ü¸Â¤è¤ê¤âû¤¤´Ö³Ö¤Ç
¥Ý¡¼¥ê¥ó¥°¤ò¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤³¤È¤Ë¤Ê¤ê¤Þ¤¹)¡£
¤³¤Î¤è¤¦¤ÊÀßÄ꤬¤Ç¤­¤Ê¤¤¤Î¤Ê¤é¤Ð¡¢UUCP ¤Ë¤è¤ëÇÛÁ÷¤òÀßÄꤷ¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
.PP
.\"O If you absolutely \fImust\fR use multidrop for this purpose, make sure
.\"O your mailserver writes an envelope-address header that fetchmail can
.\"O see.  Otherwise you \fIwill\fR lose mail and it \fIwill\fR come back
.\"O to haunt you.
¤É¤¦¤·¤Æ¤â¤³¤ÎÌÜŪ¤Ç¥Þ¥ë¥Á¥É¥í¥Ã¥×¤ò\fI»È¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤\fR¤Î¤Ç¤¢¤ì¤Ð¡¢
fetchmail ¤¬»²¾È¤Ç¤­¤ë envelope ¥¢¥É¥ì¥¹¥Ø¥Ã¥À¤ò
¥á¡¼¥ë¥µ¡¼¥Ð¤¬½ñ¤­¹þ¤à¤è¤¦¤Ëɬ¤º¤·¤Æ¤¯¤À¤µ¤¤¡£
¤µ¤â¤Ê¤¯¤Ð¡¢¥á¡¼¥ë¤Ï¤­¤Ã¤È̵¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¤¡¢
¤¢¤Ê¤¿¤ò¼ö¤¦¤¿¤á¤Ëµ¢¤Ã¤Æ¤¯¤ë¤³¤È¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£

.\"O .SS Speeding Up Multidrop Checking
.SS ¥Þ¥ë¥Á¥É¥í¥Ã¥×¤Î¥Á¥§¥Ã¥¯¤Î¹â®²½
.\"O Normally, when multiple users are declared 
.\"O .I fetchmail
.\"O extracts recipient addresses as described above and checks each host
.\"O part with DNS to see if it's an alias of the mailserver.  If so, the
.\"O name mappings described in the to ... here declaration are done and
.\"O the mail locally delivered.
Ä̾ï¤Ï¡¢Ê£¿ô¤Î¥æ¡¼¥¶¤¬Àë¸À¤µ¤ì¤Æ¤¤¤ë¤È¤­¡¢
.I fetchmail
¤Ï¼õ¿®¼Ô¥¢¥É¥ì¥¹¤òÀèÄøÀâÌÀ¤·¤¿¤è¤¦¤ËŸ³«¤·¡¢
¤½¤ì¤¾¤ì¤Î¥Û¥¹¥ÈÉôʬ¤ò DNS¤Ç¥Á¥§¥Ã¥¯¤·¡¢
¤³¤ì¤¬¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥¨¥¤¥ê¥¢¥¹¤«¤É¤¦¤«¤òÄ´¤Ù¤Þ¤¹¡£
¤½¤¦¤Ç¤¢¤ì¤Ð¡¢¡Öto ... here¡×Àë¸À¤Çµ­½Ò¤µ¤ì¤¿Ì¾Á°¤Î¥Þ¥Ã¥Ô¥ó¥°¤¬¼Â¹Ô¤µ¤ì¡¢
¥á¡¼¥ë¤¬¥í¡¼¥«¥ë¤ËÇÛÁ÷¤µ¤ì¤Þ¤¹¡£
.PP
.\"O This is the safest but also slowest method.  To speed it up,
.\"O pre-declare mailserver aliases with `aka'; these are checked before
.\"O DNS lookups are done.  If you're certain your aka list contains
.\"O .B all
.\"O DNS aliases of the mailserver (and all MX names pointing at it) 
.\"O you can declare `no dns' to suppress DNS lookups entirely and
.\"O \fIonly\fR match against the aka list.
¤³¤ì¤Ï¤È¤Æ¤â°ÂÁ´¤Ç¤¹¤¬¡¢Èó¾ï¤ËÃÙ¤¤ÊýË¡¤Ç¤¹¡£
¤³¤ì¤ò¹â®²½¤¹¤ë¤¿¤á¤Ë¤Ï¡¢
`aka' ¤ò»È¤Ã¤Æ¥á¡¼¥ë¥µ¡¼¥Ð¤Î¥¨¥¤¥ê¥¢¥¹¤òͽ¤áÀë¸À¤·¤Æ¤¯¤À¤µ¤¤¡£
¤³¤ì¤é¤Ï DNS ¤Î»²¾È¤ò¹Ô¤¦Á°¤Ë¥Á¥§¥Ã¥¯¤µ¤ì¤Þ¤¹¡£
aka ¤Î¥ê¥¹¥È¤¬¥á¡¼¥ë¥µ¡¼¥Ð¤Î DNS ¥¨¥¤¥ê¥¢¥¹
(¤ª¤è¤Ó¡¢¤³¤ì¤ò»Ø¤¹Á´¤Æ¤Î MX ̾) ¤ò
.B Á´¤Æ
´Þ¤ó¤Ç¤¤¤ë¤³¤È¤¬³Î¤«¤Ç¤¢¤ì¤Ð¡¢`no dns' ¤òÀë¸À¤·¤Æ DNS »²¾È¤ò´°Á´¤Ë»ß¤á¡¢
aka ¥ê¥¹¥È¤ËÂФ·¤Æ\fI¤Î¤ß\fR¥Þ¥Ã¥Á¥ó¥°¤ò¹Ô¤ï¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

.\"O .SH EXIT CODES
.SH ½ªÎ»¥³¡¼¥É
.\"O To facilitate the use of 
.\"O .I fetchmail
.\"O in shell scripts, an exit code is returned to give an indication
.\"O of what occurred during a given connection.
¥·¥§¥ë¥¹¥¯¥ê¥×¥ÈÆâ¤Ç
.I fetchmail
¤ò¤¦¤Þ¤¯»È¤¨¤ë¤è¤¦¤Ë¡¢Í¿¤¨¤é¤ì¤¿Àܳ¤Î´Ö¤Ëµ¯¤­¤¿¤³¤È¤òÅÁ¤¨¤ë¤¿¤á¤Î
½ªÎ»¥³¡¼¥É¤¬ÊÖ¤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
.PP
.\"O The exit codes returned by 
.\"O .I fetchmail
.\"O are as follows:
.I fetchmail
¤¬ÊÖ¤¹½ªÎ»¥³¡¼¥É¤ò°Ê²¼¤Ë¼¨¤·¤Þ¤¹:
.IP 0
.\"O One or more messages were successfully retrieved (or, if the -c option
.\"O was selected, were found waiting but not retrieved).
1 ¤Ä°Ê¾å¤Î¥á¥Ã¥»¡¼¥¸¤¬¤¦¤Þ¤¯¼èÆÀ¤Ç¤­¤¿¾ì¹ç
(-c ¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Æ¤¤¤ë»þ¤Ï¡¢
¼èÆÀÂÔ¤Á¤Î¥á¡¼¥ë¤ò¸«¤Ä¤±¡¢¼èÆÀ¤ò¹Ô¤ï¤Ê¤«¤Ã¤¿¾ì¹ç)¡£
.IP 1
.\"O There was no mail awaiting retrieval.  (There may have been old mail still
.\"O on the server but not selected for retrieval.)
¼èÆÀÂÔ¤Á¤Î¥á¡¼¥ë¤¬Ìµ¤«¤Ã¤¿¾ì¹ç¡£
(¥µ¡¼¥Ð¾å¤Ë¸Å¤¤¥á¡¼¥ë¤¬¤Þ¤À¤¢¤ë¤±¤ì¤É¡¢
¼èÆÀ¤µ¤ì¤ë¤â¤Î¤È¤·¤ÆÁª¤Ð¤ì¤Æ¤¤¤Ê¤«¤Ã¤¿¾ì¹ç¤â¤¢¤ê¤Þ¤¹¡£)
.IP 2
.\"O An error was encountered when attempting to open a socket to retrieve
.\"O mail.  If you don't know what a socket is, don't worry about it --
.\"O just treat this as an 'unrecoverable error'.  This error can also be
.\"O because a protocol fetchmail wants to use is not listed in /etc/services.
¥á¡¼¥ë¼èÆÀ¤Î¤¿¤á¤Ë¥½¥±¥Ã¥È¤ò¥ª¡¼¥×¥ó¤·¤è¤¦¤È¤·¤¿¤È¤­¤Ë¥¨¥é¡¼¤Ë½Ð²ñ¤Ã¤¿¾ì¹ç¡£
¥½¥±¥Ã¥È¤¬²¿¤«¤òÃΤé¤Ê¤¯¤Æ¤â¡¢¿´ÇۤˤϵڤӤޤ»¤ó¡£
¤³¤ì¤Ïñ¤Ë¡Ö¤É¤¦¤·¤è¤¦¤â¤Ê¤¤¥¨¥é¡¼¡×¤È¤·¤Æ°·¤Ã¤Æ¤¯¤À¤µ¤¤¡£
¤³¤Î¥¨¥é¡¼¤Ï fetchmail ¤¬»È¤ª¤¦¤È¤·¤¿¥×¥í¥È¥³¥ë¤¬
/etc/services ¤Ë¥ê¥¹¥È¤µ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ë¤âµ¯¤³¤ê¤Þ¤¹¡£
.IP 3
.\"O The user authentication step failed.  This usually means that a bad 
.\"O user-id, password, or APOP id was specified.  Or it may mean that you 
.\"O tried to run fetchmail under circumstances where it did not have
.\"O standard input attached to a terminal and could not prompt for a
.\"O missing password.
¥æ¡¼¥¶Ç§¾Ú¤Î¥¹¥Æ¥Ã¥×¤Ç¼ºÇÔ¤·¤¿¾ì¹ç¡£
¤³¤ì¤ÏÄ̾¥æ¡¼¥¶ ID¡¢¥Ñ¥¹¥ï¡¼¥É¡¢
APOP ID ¤Î»ØÄ꤬´Ö°ã¤Ã¤Æ¤¤¤ë¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£
¤³¤ì°Ê³°¤Î¾ì¹ç¤Ç¤Ï¡¢É¸½àÆþÎϤ¬Ã¼Ëö¤ËÀܳ¤µ¤ì¤Æ¤¤¤Ê¤¤¾õ¶·¤Ç
fetchmail ¤ò¼Â¹Ô¤·¤è¤¦¤È¤·¤Æ¤¤¤Æ¡¢
ÆþÎϤǤ­¤Ê¤«¤Ã¤¿¥Ñ¥¹¥ï¡¼¥É¤òÆþÎϤ¹¤ë¤¿¤á¤Î¥×¥í¥ó¥×¥È¤¬
½Ð¤»¤Ê¤¤¤³¤È¤ò°ÕÌ£¤·¤Æ¤¤¤Þ¤¹¡£
.IP 4
.\"O Some sort of fatal protocol error was detected.
²¿¤é¤«¤Î¼ïÎà¤ÎÃ×̿Ū¤Ê¥×¥í¥È¥³¥ë¥¨¥é¡¼¤¬¸¡½Ð¤µ¤ì¤¿¾ì¹ç¡£
.IP 5
.\"O There was a syntax error in the arguments to 
.\"O .I fetchmail.
.I fetchmail
¤ËÍ¿¤¨¤¿°ú¤­¿ô¤Ëʸˡ¥¨¥é¡¼¤¬¤¢¤ë¾ì¹ç¡£
.IP 6
.\"O The run control file had bad permissions.
¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤¬Àµ¤·¤¯¤Ê¤¤¾ì¹ç¡£
.IP 7
.\"O There was an error condition reported by the server.  Can also
.\"O fire if
.\"O .I fetchmail
.\"O timed out while waiting for the server.
¥µ¡¼¥Ð¤«¤é¥¨¥é¡¼¾õÂÖ¤¬Êó¹ð¤µ¤ì¤¿¾ì¹ç¡£
¥µ¡¼¥Ð¤Ø¤ÎÀܳÂÔ¤Á¤Ç
.I fetchmail
¤¬¥¿¥¤¥à¥¢¥¦¥È¤òµ¯¤³¤·¤¿»þ¤Ë¤â¤³¤¦¤Ê¤ê¤Þ¤¹¡£
.IP 8
.\"O Client-side exclusion error.  This means 
.\"O .I fetchmail
.\"O either found another copy of itself already running, or failed in such
.\"O a way that it isn't sure whether another copy is running.
¥¯¥é¥¤¥¢¥ó¥È¦¤ÎÇÓ¾¥¨¥é¡¼¤Î¾ì¹ç¡£¤³¤ì¤Ï
.I fetchmail
¤¬´û¤ËÆ°ºî¤·¤Æ¤¤¤ëÊ̤Î
.I fetchmail
¤ò¸¡½Ð¤·¤¿¤«¡¢¸¡½Ð¤Ë¼ºÇÔ¤·¤¿¤¿¤á
.I fetchmail
¤¬Æ°ºî¤·¤Æ¤¤¤ë¤«¤É¤¦¤«¤Ï¤Ã¤­¤ê¤·¤Ê¤¤¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£
.IP 9
.\"O The user authentication step failed because the server responded "lock
.\"O busy".  Try again after a brief pause!  This error is not implemented
.\"O for all protocols, nor for all servers.  If not implemented for your
.\"O server, "3" will be returned instead, see above.  May be returned when
.\"O talking to qpopper or other servers that can respond with "lock busy"
.\"O or some similar text containing the word "lock".
¥µ¡¼¥Ð¤¬±þÅú¤Ç "lock busy" ¤òÊÖ¤·¤¿¤¿¤á¤Ë¡¢
¥æ¡¼¥¶Ç§¾Ú¥¹¥Æ¥Ã¥×¤¬¼ºÇÔ¤·¤¿¾ì¹ç¡£
¤Á¤ç¤Ã¤ÈÂԤäƤ«¤éºÆÄ©À路¤Æ¤¯¤À¤µ¤¤!
¤³¤Î¥¨¥é¡¼¤Ï¥×¥í¥È¥³¥ëÁ´¤Æ¤Ë¼ÂÁõ¤µ¤ì¤Æ¤¤¤ë¤ï¤±¤Ç¤Ï¤Ê¤¤¤Ç¤¹¤·¡¢
¥µ¡¼¥ÐÁ´¤Æ¤Ë¼ÂÁõ¤µ¤ì¤Æ¤¤¤ë¤ï¤±¤Ç¤â¤¢¤ê¤Þ¤»¤ó¡£
¤³¤Î¥¨¥é¡¼¤¬¥µ¡¼¥Ð¤Ë¼ÂÁõ¤µ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢
¤³¤Î¥³¡¼¥É¤Ç¤Ï¤Ê¤¯ "2" ¤¬ÊÖ¤µ¤ì¤Þ¤¹ (Á°¤Î¹àÌܤò»²¾È¤·¤Æ¤¯¤À¤µ¤¤)¡£
"lock busy" ¤ä¤³¤ì¤Ë»÷¤¿¥Æ¥­¥¹¥È¤Ç "lock" ¤È¤¤¤¦¸ì¤ò´Þ¤à¤â¤Î¤ò±þÅú¤È¤·¤ÆÊÖ¤¹¡¢
qpopper ¤ä¾¤Î¥µ¡¼¥Ð¤ÈÄÌ¿®¤·¤¿¤È¤­¤Ë¤³¤Î¥³¡¼¥É¤¬ÊÖ¤µ¤ì¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
.IP 10
.\"O The 
.\"O .I fetchmail
.\"O run failed while trying to do an SMTP port open or transaction.
SMTP ¥Ý¡¼¥È¤Î¥ª¡¼¥×¥ó¤ä¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤ò¹Ô¤ª¤¦¤È¤·¤Æ¤¤¤ë»þ¤Ë
.I fetchmail
¤ÎÆ°ºî¤¬¼ºÇÔ¤·¤¿¾ì¹ç¡£
.IP 11
.\"O Fatal DNS error.  Fetchmail encountered an error while performing
.\"O a DNS lookup at startup and could not proceed.
Ã×̿Ū¤Ê DNS ¤Î¥¨¥é¡¼¡£fetchmail ¤¬µ¯Æ°»þ¤Ë DNS ¤Î»²¾È¤Ë¼ºÇÔ¤·¡¢
¤½¤ÎÀè¤ò¼Â¹Ô¤Ç¤­¤Ê¤«¤Ã¤¿¤È¤­¤Ëµ¯¤³¤ê¤Þ¤¹¡£
.IP 12
.\"O BSMTP batch file could not be opened.
BSMTP ¤Î¥Ð¥Ã¥Á¥Õ¥¡¥¤¥ë¤ò¥ª¡¼¥×¥ó¤Ç¤­¤Ê¤«¤Ã¤¿¾ì¹ç¡£
.IP 13
.\"O Poll terminated by a fetch limit (see the --fetchlimit option).
¼èÆÀ¤ÎÀ©¸Â¤Ë¤è¤ê¥Ý¡¼¥ê¥ó¥°¤¬½ªÎ»¤·¤¿ (--fetchlimit ¥ª¥×¥·¥ç¥ó¤ò»²¾È)¡£
.IP 14
.\"O Server busy indication.
¥µ¡¼¥Ð¤¬¥Ó¥¸¡¼¤Ç¤¢¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£
.IP 23
.\"O Internal error.  You should see a message on standard error with
.\"O details.
ÆâÉô¥¨¥é¡¼¤Î¾ì¹ç¡£É¸½à¥¨¥é¡¼½ÐÎϤ˽Фë¥á¥Ã¥»¡¼¥¸¤ò¾Ü¤·¤¯¸«¤Æ¤¯¤À¤µ¤¤¡£
.PP
.\"O When
.\"O .I fetchmail
.\"O queries more than one host, return status is 0 if \fIany\fR query
.\"O successfully retrieved mail. Otherwise the returned error status is
.\"O that of the last host queried.
.I fetchmail
¤¬Ê£¿ô¤Î¥Û¥¹¥È¤ËÌ䤤¹ç¤ï¤»¤ò¹Ô¤¦¾ì¹ç¡¢
\fI¤¤¤º¤ì¤«\fR¤ÎÌ䤤¹ç¤ï¤»¤Ç¥á¡¼¥ë¤ò¤¦¤Þ¤¯¼èÆÀ¤Ç¤­¤ì¤Ð¡¢
¥¹¥Æ¡¼¥¿¥¹ 0 ¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£
¤½¤¦¤Ç¤Ê¤¤¤ËÊÖ¤µ¤ì¤ë¥¨¥é¡¼¥¹¥Æ¡¼¥¿¥¹¤Ï¡¢
ºÇ¸å¤ËÌ䤤¹ç¤ï¤»¤ò¹Ô¤Ã¤¿¥Û¥¹¥È¤Î¥¹¥Æ¡¼¥¿¥¹¤È¤Ê¤ê¤Þ¤¹¡£

.\"O .SH FILES
.SH ¥Õ¥¡¥¤¥ë
.TP 5
~/.fetchmailrc
.\"O default run control file
¥Ç¥Õ¥©¥ë¥È¤Î¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë
.TP 5
~/.fetchids
.\"O default location of file associating hosts with last message IDs seen
.\"O (used only with newer RFC1725-compliant POP3 servers supporting the
.\"O UIDL command).
¥Û¥¹¥È¤ÈÁ°²ó¤ÎÆɤó¤À¥á¡¼¥ë¤Î¥á¥Ã¥»¡¼¥¸ ID ¤òÂбþ¤Å¤±¤ë
¥Õ¥¡¥¤¥ë¤Î¥Ç¥Õ¥©¥ë¥È¤Î°ÌÃÖ
(UIDL ¥³¥Þ¥ó¥É¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¡¢
RFC1725 ½àµò¤ÎºÇ¶á¤Î POP3 ¥µ¡¼¥Ð¤Ç¤·¤«»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó)¡£
.TP 5
~/.fetchmail.pid
.\"O lock file to help prevent concurrent runs (non-root mode).
¿½Å¼Â¹Ô¤òËɤ°¤¿¤á¤Î¥í¥Ã¥¯¥Õ¥¡¥¤¥ë (Èó root ¥â¡¼¥É¤Î¾ì¹ç)¡£
.TP 5
~/.netrc 
.\"O your FTP run control file, which (if present) will be searched for
.\"O passwords as a last resort before prompting for one interactively.
FTP ¤Î¼Â¹ÔÀ©¸æ¥Õ¥¡¥¤¥ë¡£(¤â¤·¤¢¤ë¤Ê¤é¤Ð) ÂÐÏÃŪ¤Ë¥Ñ¥¹¥ï¡¼¥É¤òµá¤á¤ëÁ°¤Ë¡¢
ºÇ½ªÅª¤Ë¥Ñ¥¹¥ï¡¼¥É¤¬¸¡º÷¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¤Ç¤¹¡£
.TP 5
/var/run/fetchmail.pid
.\"O lock file to help prevent concurrent runs (root mode, Linux systems).
¿½Å¼Â¹Ô¤òËɤ°¤¿¤á¤Î¥í¥Ã¥¯¥Õ¥¡¥¤¥ë (root ¥â¡¼¥É¡¢Linux ¤Î¾ì¹ç)¡£
.TP 5
/etc/fetchmail.pid
.\"O lock file to help prevent concurrent runs (root mode, systems without /var/run).
¿½Å¼Â¹Ô¤òËɤ°¤¿¤á¤Î¥í¥Ã¥¯¥Õ¥¡¥¤¥ë
(root ¥â¡¼¥É¡¢/var/run ¤¬Ìµ¤¤¥·¥¹¥Æ¥à¤Î¾ì¹ç)¡£

.\"O .SH ENVIRONMENT
.SH ´Ä¶­ÊÑ¿ô
.\"O If the FETCHMAILUSER variable is set, it is used as the name of the
.\"O calling user (default local name) for purposes such as mailing error
.\"O notifications.  Otherwise, if either the LOGNAME or USER variable is
.\"O correctly set (e.g. the corresponding UID matches the session user ID)
.\"O then that name is used as the default local name.  Otherwise
.\"O \fBgetpwuid\fR(3) must be able to retrieve a password entry for the
.\"O session ID (this elaborate logic is designed to handle the case of
.\"O multiple names per userid gracefully).
´Ä¶­ÊÑ¿ô FETCHMAILUSER ¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢
¥¨¥é¡¼ÄÌÃΤò¥á¡¼¥ë¤ÇÃΤ餻¤ë¤¿¤á¤Î¥æ¡¼¥¶Ì¾¤È¤·¤Æ»È¤ï¤ì¤Þ¤¹
(¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥í¡¼¥«¥ë̾¤¬»È¤ï¤ì¤Þ¤¹)¡£
¤³¤Î´Ä¶­ÊÑ¿ô¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢
´Ä¶­ÊÑ¿ô LOGNAME ¤« USER ¤ÎÃͤ¬Àµ¤·¤¯ÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð 
(Î㤨¤Ð¡¢¤³¤ÎÃͤËÂбþ¤¹¤ë UID ¤¬¥»¥Ã¥·¥ç¥ó¤Î¥æ¡¼¥¶ ID ¤Ë°ìÃפ¹¤ë)¡¢
¤½¤Î̾Á°¤¬¥Ç¥Õ¥©¥ë¥È¤Î¥í¡¼¥«¥ë̾¤È¤·¤Æ»È¤ï¤ì¤Þ¤¹¡£
¤³¤ì¤é¤Î´Ä¶­ÊÑ¿ô¤âÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢
\fBgetpwuid\fR(3) ¤¬¥»¥Ã¥·¥ç¥ó ID ¤ËÂФ¹¤ë
¥Ñ¥¹¥ï¡¼¥É¥¨¥ó¥È¥ê¤ò¼èÆÀ¤Ç¤­¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó
(¤³¤Î¤è¤¦¤Ê¼ê¤Î¹þ¤ó¤À¥í¥¸¥Ã¥¯¤Ï¡¢
1 ¤Ä¤Î¥æ¡¼¥¶ ID ¤ËÊ£¿ô¤Î¥æ¡¼¥¶Ì¾¤¬Âбþ¤¹¤ë¾ì¹ç¤ò
¤¦¤Þ¤¯°·¤¦¤¿¤á¤ËÍÑ°Õ¤µ¤ì¤Æ¤¤¤Þ¤¹)¡£

.\"O If the environment variable FETCHMAILHOME is set to a valid and
.\"O existing directory name, the .fetchmailrc and .fetchids and
.\"O \&.fetchmail.pid files are put there instead of in the invoking user's
.\"O home directory (and lose the leading dots on theirt names).  The
.\"O \&.netrc file is looked for in the the invoking user's home directory
.\"O regardless of FETCHMAILHOME's setting.
´Ä¶­ÊÑ¿ô FETCHMAILHOME ¤¬
¼ÂºÝ¤Ë¸ºß¤¹¤ëÀµ¤·¤¤¥Ç¥£¥ì¥¯¥È¥ê̾¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢
¥Õ¥¡¥¤¥ë .fetchmailrc, .fetchids, .fetchmail.pid ¤Ï¡¢
µ¯Æ°¤·¤¿¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤Ï¤Ê¤¯¡¢
¤³¤Î´Ä¶­ÊÑ¿ô¤Ç»ØÄꤷ¤¿¥Ç¥£¥ì¥¯¥È¥ê¤ËÃÖ¤«¤ì¤Þ¤¹
(¥Õ¥¡¥¤¥ë̾¤ÎÀèƬ¤Ë¤¢¤ë¥É¥Ã¥È¤Ï¼è¤ê½ü¤«¤ì¤Þ¤¹)¡£
\&.netrc ¥Õ¥¡¥¤¥ë¤Ï¡¢FETCHMAILHOME ¤ÎÀßÄê¤Ë´Ø·¸¤Ê¤¯¡¢
µ¯Æ°¤·¤¿¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Ç¥í¥Ã¥¯¤µ¤ì¤Þ¤¹¡£

.\"O .SH SIGNALS
.SH ¥·¥°¥Ê¥ë
.\"O If a
.\"O .I fetchmail
.\"O daemon is running as root, SIGHUP wakes it up from its sleep phase and
.\"O forces a poll of all non-skipped servers (this is in accordance with
.\"O the usual conventions for system daemons).
.I fetchmail
¥Ç¡¼¥â¥ó¤¬ root ¸¢¸Â¤ÇÆ°ºî¤·¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
SIGHUP ¤Ë¤è¤ê¥¹¥ê¡¼¥×¾õÂÖ¤«¤é³Ð¤á¡¢
skip »ØÄê¤Ç¤Ê¤¤¥µ¡¼¥ÐÁ´¤Æ¤ËÂФ·¤Æ¥Ý¡¼¥ê¥ó¥°¤ò¹Ô¤¤¤Þ¤¹
(¤³¤ì¤Ï¥·¥¹¥Æ¥à¥Ç¡¼¥â¥ó¤ÎÉáÄ̤ÎÅÁÅý¤Ë½¾¤¦¤â¤Î¤Ç¤¹)¡£
.PP
.\"O If
.\"O .I fetchmail
.\"O is running in daemon mode as non-root, use SIGUSR1 to wake it (this is
.\"O so SIGHUP due to logout can retain the default action of killing it).
¥Ç¡¼¥â¥ó¥â¡¼¥É
.I fetchmail
¤¬ root ¸¢¸Â°Ê³°¤ÇÆ°ºî¤·¤Æ¤¤¤ë¾ì¹ç¡¢
¥Ç¡¼¥â¥ó¤òµ¯¤³¤¹¤Ë¤Ï SIGUSR1 ¤ò»È¤¤¤Þ¤¹
(logout ¤Ë¤è¤ë SIGHUP ¤¬¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤ò¤½¤Î¤Þ¤Þ»ý¤Á¡¢
fetchmail ¤ò kill ¤¹¤ë¤«¤â¤·¤ì¤Ê¤¤¤¿¤á¤Ç¤¹)¡£
.PP
.\"O Running
.\"O .I fetchmail
.\"O in foreground while a background fetchmail is running will do
.\"O whichever of these is appropriate to wake it up.
¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤Ç
.I fetchmail
¤¬Æ°ºî¤·¤Æ¤¤¤ë¤È¤­¤Ë¡¢¥Õ¥©¥¢¥°¥é¥¦¥ó¥É¤Ç
.I fetchmail
¤ò¼Â¹Ô¤¹¤ë¤È¡¢¾åµ­¤Î¤¦¤ÁŬÀڤʥǡ¼¥â¥ó¤¬µ¯¤³¤µ¤ì¤Þ¤¹¡£

.\"O .SH BUGS AND KNOWN PROBLEMS
.SH ¥Ð¥°¤È´ûÃΤÎÌäÂê
.\"O The mda and plugin options interact badly.  In order to collect error
.\"O status from the MDA, fetchmail has to change its normal signal
.\"O handling so that dead plugin processes don't get reaped until the end
.\"O of the poll cycle.  This can cause resource starvation if too many
.\"O zombies accumulate.  So either don't deliver to a MDA using plugins or
.\"O risk being overrun by an army of undead.
mda ¥ª¥×¥·¥ç¥ó¤È plugin ¥ª¥×¥·¥ç¥ó¤ÏÁêÀ­¤¬Îɤ¯¤¢¤ê¤Þ¤»¤ó¡£
MDA ¤«¤é¥¨¥é¡¼¾õÂÖ¤ò¼èÆÀ¤¹¤ë¤¿¤á¤Ë¤Ï¡¢
fetchmail ¤ÏÄ̾ï¤Î¥·¥°¥Ê¥ë½èÍý¤òÊѹ¹¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
¤³¤Î¤è¤¦¤Ë¤¹¤ë¤È¡¢¥Ý¡¼¥ê¥ó¥°¥µ¥¤¥¯¥ë¤¬½ª¤ë¤Þ¤Ç
»à¤ó¤À¥×¥é¥°¥¤¥ó¥×¥í¥»¥¹¤¬ÇË´þ¤µ¤ì¤Þ¤»¤ó¡£
¤½¤·¤Æ¡¢¥¾¥ó¥Ó¥×¥í¥»¥¹¤¬Èó¾ï¤Ë¤¿¤¯¤µ¤ó¤Ç¤­¤¿¾ì¹ç¤Ï
¥ê¥½¡¼¥¹¤Î¸Ï³é¤¬µ¯¤³¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
¥×¥é¥°¥¤¥ó¤ò»È¤Ã¤¿ MDA ¤Ø¤ÎÇÛÁ÷¤ò¹Ô¤ï¤Ê¤¤¤«¡¢
ÂçÎ̤Υ¾¥ó¥Ó¥×¥í¥»¥¹¤Ç°î¤ì¤ë¤«¤â¤·¤ì¤Ê¤¤¥ê¥¹¥¯¤òÉ餦¤«¤Î¤É¤Á¤é¤«¤Ë¤Ê¤ê¤Þ¤¹¡£
.PP
.\"O The RFC822 address parser used in multidrop mode chokes on some
.\"O @-addresses that are technically legal but bizarre.  Strange uses of
.\"O quoting and embedded comments are likely to confuse it.
¥Þ¥ë¥Á¥É¥í¥Ã¥×¥â¡¼¥É¤Ç»È¤ï¤ì¤Æ¤¤¤ë RFC822 ¥¢¥É¥ì¥¹¤Î¥Ñ¡¼¥¶¤Ï¡¢
µ»½ÑŪ¤Ë¤ÏÀµ¤·¤¤¤±¤ì¤É¤ª¤«¤·¤Ê @-¥¢¥É¥ì¥¹¤ÇµÍ¤Þ¤Ã¤Æ¤·¤Þ¤¦¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
¤Þ¤¿¡¢¥¯¥©¡¼¥È¤ÈËä¤á¹þ¤ß¥³¥á¥ó¥È¤Î»È¤¤Êý¤¬¤ª¤«¤·¤¤¤È¡¢
¥Ñ¡¼¥¶¤ÎÆ°ºî¤¬¤ª¤«¤·¤¯¤Ê¤ê¤ä¤¹¤¤¤Ç¤¹¡£
.PP
.\"O In a message with multiple envelope headers, only the last one
.\"O processed will be visible to fetchmail.  To get around this, use a
.\"O mailserver-side filter that consolidates the contents of all envelope
.\"O headers into a single one (procmail, mailagent, or maildrop can be
.\"O programmed to do this fairly easily).
¥á¥Ã¥»¡¼¥¸¤ËÊ£¿ô¤Î envelope ¥Ø¥Ã¥À¤¬¤¢¤ë¾ì¹ç¡¢
fetchmail ¤Ë¤ÏºÇ¸å¤Ë½èÍý¤µ¤ì¤¿¥Ø¥Ã¥À¤·¤«¸«¤¨¤Þ¤»¤ó¡£
¤³¤ì¤ò²óÈò¤¹¤ë¤Ë¤Ï¡¢
envelope ¥Ø¥Ã¥À¤ÎÆâÍÆÁ´¤Æ¤ò 1 ¤Ä¤Î¥Ø¥Ã¥À¤Ë¤Þ¤È¤á¤ë¥Õ¥£¥ë¥¿
(procmail, mailagent, maildrop ¤Ë¼ê½ç¤ò»Ø¼¨¤¹¤ì¤Ð¡¢
¤³¤ì¤Ï¤«¤Ê¤ê´Êñ¤Ë¹Ô¤¨¤Þ¤¹) ¤ò¥á¡¼¥ë¥µ¡¼¥Ð¦¤Ç»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
.PP
.\"O Use of some of these protocols requires that the program send
.\"O unencrypted passwords over the TCP/IP connection to the mailserver.
¥×¥í¥È¥³¥ë¤Î¤¦¤Á¤Î¤¤¤¯¤Ä¤«¤ò»È¤¦¾ì¹ç¤Ë¤Ï¡¢
¥×¥í¥°¥é¥à¤¬°Å¹æ²½¤µ¤ì¤Æ¤¤¤Ê¤¤¥Ñ¥¹¥ï¡¼¥É¤ò
¥á¡¼¥ë¥µ¡¼¥Ð¤Þ¤Ç TCP/IP Àܳ¾å¤ÇÁ÷¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
.\"O This creates a risk that name/password pairs might be snaffled with a
.\"O packet sniffer or more sophisticated monitoring software.  Under Linux
.\"O and FreeBSD, the --interface option can be used to restrict polling to
.\"O availability of a specific interface device with a specific local or
.\"O remote IP address, but snooping is still possible if (a) either host
.\"O has a network device that can be opened in promiscuous mode, or (b)
.\"O the intervening network link can be tapped.  
¤³¤ì¤Ï¡¢¥Ñ¥±¥Ã¥È¥¹¥Ë¥Õ¥¡ (packet sniffer) ¤ä
¤â¤Ã¤È¹âµ¡Ç½¤Ê´Æ»ë¥½¥Õ¥È¥¦¥§¥¢¤Ë¤è¤Ã¤Æ
̾Á°¤È¥Ñ¥¹¥ï¡¼¥É¤ÎÁȤòÅð¤Þ¤ì¤ë´í¸±À­¤Î¸µ¤È¤Ê¤ê¤Þ¤¹¡£
Linux ¤È FreeBSD ¤Î¾ì¹ç¡¢--interface ¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢
ÆÃÄê¤Î¥í¡¼¥«¥ë¤Þ¤¿¤Ï¥ê¥â¡¼¥È¤Î IP ¥¢¥É¥ì¥¹¤ò»ý¤Ä
ÆÃÄê¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹¥Ç¥Ð¥¤¥¹¤ËÂФ·¤Æ¤Î¤ß
¥Ý¡¼¥ê¥ó¥°¤¬²Äǽ¤Ç¤¢¤ë¤è¤¦¤ËÀ©¸Â¤Ç¤­¤Þ¤¹¤¬¡¢
¤½¤Î¾ì¹ç¤Ç¤â (a) ¤É¤Á¤é¤«¤Î¥Û¥¹¥È¤¬
̵º¹Ê̥⡼¥É (promiscuous mode) ¤Ç¥ª¡¼¥×¥ó¤Ç¤­¤ë
¥Í¥Ã¥È¥ï¡¼¥¯¥Ç¥Ð¥¤¥¹¤ò»ý¤Ã¤Æ¤¤¤ë¤«¡¢
(b) ´Ö¤Ë¤¢¤ë¥Í¥Ã¥È¥ï¡¼¥¯Àܳ¤¬ÅðÄ°²Äǽ¤Ç¤¢¤ì¤ÐÅðÄ°¤Ï²Äǽ¤Ç¤¹¡£
.\"O We recommend the use of
.\"O .IR ssh (1)
.\"O tunnelling to not only shroud your passwords but encrypt the entire
.\"O conversation.
¥Ñ¥¹¥ï¡¼¥É¤ò°Å¹æ²½¤¹¤ë¤À¤±¤Ç¤Ê¤¯¡¢Á´¤Æ¤ÎÄÌ¿®¤ò°Å¹æ²½¤¹¤ë¤¿¤á¤Ë¤â¡¢
.IR ssh (1)
¥È¥ó¥Í¥ê¥ó¥°¤Î»ÈÍѤò¤ª´«¤á¤·¤Þ¤¹¡£
.PP
.\"O Use of the %F or %T escapes in an mda option could open a security
.\"O hole, because they pass text manipulable by an attacker to a shell
.\"O command.  Potential shell characters are replaced by `_' before
.\"O execution.  The hole is further reduced by the fact that fetchmail
.\"O temporarily discards any suid privileges it may have while running the
.\"O MDA.  For maximum safety, however, don't use an mda command containing
.\"O %F or %T when fetchmail is run from the root account itself.
mda ¥ª¥×¥·¥ç¥ó¤Ç %F, %T ¥¨¥¹¥±¡¼¥×¤ò»È¤¦¤È¥»¥­¥å¥ê¥Æ¥£¥Û¡¼¥ë¤¬¤Ç¤­¤Þ¤¹¡£
¤Ê¤¼¤Ê¤é¡¢¤³¤ì¤é¤Î¥¨¥¹¥±¡¼¥×¤Ï¹¶·â¼Ô¤¬Áàºî¤Ç¤­¤ë¥Æ¥­¥¹¥È¤ò
¥·¥§¥ë¥³¥Þ¥ó¥É¤ËÅϤ¹¤«¤é¤Ç¤¹¡£
¥·¥§¥ëʸ»ú¤Ë¤Ê¤ë²ÄǽÀ­¤¬¤¢¤ë¤â¤Î¤Ï¡¢¼Â¹Ô¤ÎÁ°¤Ë `_' ¤ËÃÖ´¹¤µ¤ì¤Þ¤¹¡£
fetchmail ¤Ï MDA ¤ò¼Â¹Ô¤·¤Æ¤¤¤ë´Ö¡¢
SUID ¤Ë¤è¤êÆÀ¤ë¤³¤È¤¬¤Ç¤­¤¿¸¢¸Â¤ò°ì»þŪ¤ËÁ´¤ÆÇË´þ¤¹¤ë¤Î¤Ç¡¢
¤³¤Î¥»¥­¥å¥ê¥Æ¥£¥Û¡¼¥ë¤Ï¤«¤Ê¤ê¾®¤µ¤¯¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
¤·¤«¤·¡¢¤Ç¤­¤ë¤À¤±°ÂÁ´¤Ë¤¹¤ë¤¿¤á¤Ë¡¢
fetchmail ¤òroot ¤Î¥¢¥«¥¦¥ó¥È¤«¤é¼Â¹Ô¤¹¤ë¤È¤­¤Ë¤Ï¡¢
%F, %T ¤ò´Þ¤àmda ¥³¥Þ¥ó¥É¤ò»È¤Ã¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
.PP
.\"O Fetchmail's method of sending bouncemail and spam bounces requires that
.\"O port 25 of localhost be available for sending mail via SMTP.
fetchmail ¤Ë¤ª¤±¤ë bouncemail ¤È spambounce ¤Î½Ð¤·Êý¤Ç¤Ï¡¢
¥í¡¼¥«¥ë¥Û¥¹¥È¤Î 25 È֥ݡ¼¥È¤Ç SMTP ·Ðͳ¤Î¥á¡¼¥ë¤¬Á÷¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.PP
.\"O If you modify a
.\"O .I ~/.fetchmailrc
.\"O while a background instance is running and break the syntax, the
.\"O background instance will die silently.  Unfortunately, it can't 
.\"O die noisily because we don't yet know whether syslog should be enabled.
¤³¤Î¥×¥í¥»¥¹¤ò¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤Ç¼Â¹Ô¤·¤Æ¤¤¤ë»þ¤Ë
.I ~/.fetchmailrc
¤ò½¤Àµ¤·¡¢Ê¸Ë¡¤ò´Ö°ã¤Ã¤Æ¤·¤Þ¤¦¤È¡¢
¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤Î¥×¥í¥»¥¹¤Ï²¿¤â¸À¤ï¤º¤Ë½ªÎ»¤·¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
°­¤¤¤³¤È¤Ë¡¢¤³¤Î¥×¥í¥°¥é¥à¤Ï²¿¤«¤ò½ñ¤­½Ð¤·¤Æ½ªÎ»¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£
¤Ê¤¼¤Ê¤é¡¢syslog ¤òÍ­¸ú¤Ë¤¹¤Ù¤­Èݤ«¤¬¡¢¤Þ¤Àʬ¤«¤é¤Ê¤¤¤«¤é¤Ç¤¹¡£
.PP
.\"O The -f - option (reading a configuration from stdin) is incompatible
.\"O with the plugin option.
(ÀßÄê¤òɸ½àÆþÎϤ«¤éÆɤ߹þ¤à) -f - ¥ª¥×¥·¥ç¥ó¤Ï¡¢
¥×¥é¥°¥¤¥ó¥ª¥×¥·¥ç¥ó¤È¤Ï¸ß´¹À­¤¬¤¢¤ê¤Þ¤»¤ó¡£
.PP
.\"O The UIDL code is generally flaky and tends to lose its state on errors
.\"O and line drops (so that old messages are re-seen).  If this happens to
.\"O you, switch to IMAP4.
UIDL ¥³¡¼¥É¤Ï°ìÈÌŪ¤Ë¤¢¤Þ¤êÅö¤Æ¤Ë¤Ê¤é¤Ê¤¤¤â¤Î¤Ç¡¢
¹Ô¤òÈô¤Ð¤·¤¿¾ì¹ç¤ä¥¨¥é¡¼¤Î¾ì¹ç¤Ë¡¢¥³¡¼¥É¤Î¾õÂÖ¤ò¼º¤¤¤ä¤¹¤¤·¹¸þ¤¬¤¢¤ê¤Þ¤¹
(¤½¤Î¤¿¤á¡¢¸Å¤¤¥á¥Ã¥»¡¼¥¸¤¬ºÆÅÙ±ÜÍ÷¤µ¤ì¤Æ¤·¤Þ¤¤¤Þ¤¹)¡£
¤³¤Î¤è¤¦¤Ê¾ì¹ç¤Ï¡¢IMAP4 ¤Ë¾è¤ê´¹¤¨¤Æ²¼¤µ¤¤¡£
.PP
.\"O The `principal' option only handles Kerberos IV, not V.
`principal' ¥ª¥×¥·¥ç¥ó¤Ï Kerberos IV ¤·¤«°·¤ï¤º¡¢
Kerberos V ¤Ï°·¤¤¤Þ¤»¤ó¡£
.PP
.\"O Send comments, bug reports, gripes, and the like to the
.\"O fetchmail-friends list <fetchmail-friends@lists.ccil.org>.  An HTML FAQ is
.\"O available at the fetchmail home page; surf to
.\"O http://www.tuxedo.org/~esr/fetchmail or do a WWW search for pages with
.\"O `fetchmail' in their titles.
¥³¥á¥ó¥È¡¢¥Ð¥°Êó¹ð¡¢¶ì¾ð¤ÎÎà¤Ï¡¢fetchmail-friends ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È
<fetchmail-friends@lists.ccil.org> ¤ËÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
HTML ÈǤΠFAQ ¤¬ fetchmail ¤Î¥Û¡¼¥à¥Ú¡¼¥¸¤Ë¤¢¤ê¤Þ¤¹¡£
http://www.tuxedo.org/~esr/fetchmail ¤Ø¹Ô¤¯¤«¡¢
`fetchmail' ´ØÏ¢¤Î¥Ú¡¼¥¸¤ò WWW ¤Ç¸¡º÷¤·¤Æ¤¯¤À¤µ¤¤¡£

.\"O .SH AUTHOR
.SH Ãø¼Ô
.\"O Eric S. Raymond <esr@snark.thyrsus.com>.  Too many other people to
.\"O name here have contributed code and patches. 
.\"O This program is descended from and replaces 
.\"O .IR popclient , 
.\"O by Carl Harris <ceharris@mal.com>; the internals have become quite different, 
.\"O but some of its interface design is directly traceable to that
.\"O ancestral program.
Eric S. Raymond <esr@snark.thyrsus.com>¡£
¤³¤³¤Ç¤Ïµó¤²¤é¤ì¤Ê¤¤¤Û¤É¿¤¯¤ÎÊý¡¹¤¬¥³¡¼¥É¤ä¥Ñ¥Ã¥Á¤òÄ󶡤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£
¤³¤Î¥×¥í¥°¥é¥à¤Ï Carl Harris <ceharris@mal.com> ¤µ¤óºî¤Î
.IR popclient
¤ò´ð¤Ë¤·¤Æ¤ª¤ê¡¢¤³¤ì¤òÃÖ¤­´¹¤¨¤ë¤â¤Î¤Ç¤¹¡£
ÆâÉôŪ¤Ë¤Ï¤Þ¤Ã¤¿¤¯°Û¤Ê¤ë¤â¤Î¤Ë¤Ê¤ê¤Þ¤·¤¿¤¬¡¢
¥¤¥ó¥¿¥Õ¥§¡¼¥¹À߷פΰìÉô¤Ë¤Ä¤¤¤Æ¤Ï¡¢
¤³¤Î¤´ÀèÁÄÍͤΤâ¤Î¤ò¤½¤Î¤Þ¤Þ°ú¤­·Ñ¤¤¤Ç¤¤¤Þ¤¹¡£

.\"O .SH SEE ALSO
.SH ´ØÏ¢¹àÌÜ
mutt(1), elm(1), mail(1), sendmail(8), popd(8), imapd(8), netrc(5)
.\"O .SH APPLICABLE STANDARDS
.SH ½àµò¤·¤Æ¤¤¤ëɸ½àµ¬Ìó
.TP 5
SMTP/ESMTP:
RFC 821, RFC2821, RFC 1869, RFC 1652, RFC 1870, RFC1983, RFC 1985
.TP 5
mail:
RFC 822, RFC2822, RFC 1123, RFC 1892, RFC 1894
.TP 5
POP2:
RFC 937
.TP 5
POP3:
RFC 1081, RFC 1225, RFC 1460, RFC 1725, RFC1734, RFC 1939, RFC 1957,
RFC2195, RFC 2449
.TP 5
APOP:
RFC 1460, RFC 1725, RFC 1939
.TP 5
RPOP:
RFC 1081, RFC 1225
.TP 5
IMAP2/IMAP2BIS:
RFC 1176, RFC 1732
.TP 5
IMAP4/IMAP4rev1:
RFC 1730, RFC 1731, RFC 1732, RFC 2060, RFC 2061, RFC 2195, RFC 2177,
RFC 2683
.TP 5
ETRN:
RFC 1985
.TP 5
ODMR/ATRN:
RFC 2645
.TP 5
OTP:
RFC 1938
.TP 5
LMTP:
RFC 2033
.TP 5
GSSAPI:
RFC 1508