blob: 6464f2a7ff51f758d2bf5ab998b9bb366f63b458 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
# fetchmail control file sample
#
# This file (or one of your own creation, rather) should be located
# in your home directory with the name .fetchmailrc. Permissions on this
# file may be no greater than -rw-------, or fetchmail will refuse to
# use it.
#
# To see what effect your ~/.fetchmailrc file has, do
#
# fetchmail --version
#
# This will display the fetchmail version number and an explanation
# in English of what the currently set options and defaults mean.
#
# Comments begin with a '#' and extend through the end of the line.
# Blank lines between server entries are ignored.
# Keywords and identifiers are case sensitive.
# When there is a conflict between the command-line arguments and the
# arguments in this file, the command-line arguments take precedence.
#
# Legal keywords are
# poll -- must be followed by a mailserver name
# skip -- must be followed by a mailserver name
# protocol (or proto) -- must be followed by a protocol ID
# port -- must be followed by a TCP/IP port number
# authenticate (or auth) -- must be followed by an authentication type
# timeout -- must be followed by a numeric timeout value
# envelope -- must be followed by an envelope header name
# aka -- must be followed by one or more server aliases
# localdomains -- must be followed by one or more domain names
# interface -- must be followed by device/IP address/mask
# monitor -- must be followed by IP address
#
# username (or user) -- must be followed by a name
# is -- must be followed by one or more names
# remotefolder (or remote) -- must be followed by a filename
# password (or pass) -- must be followed by a password string
# smtphost (or smtp) -- must be followed by a host name
# mda -- must be followed by an MDA command string
# preconnect (or pre) -- must be followed by an initialization command
#
# keep
# flush
# fetchall
# rewrite
# dns
# no keep
# no flush
# no fetchall
# no rewrite
# no dns
# limit -- must be followed by numeric size limit
# fetchlimit -- must be followed by numeric msg fetch limit
# batchlimit -- must be followed by numeric SMTP batch limit
#
# Legal protocol identifiers are
# pop2 (or POP2)
# pop3 (or POP3)
# imap (or IMAP)
# apop (or APOP)
# rpop (or RPOP)
# kpop (or KPOP)
#
# Legal authentication types are
# login
# kerberos
#
# Legal global option statements are
#
# set logfile = -- must be followed by a string
#
# The noise keywords `and', `with', `has', `wants', and `options' are ignored
# anywhere in an entry; they can be used to make it resemble English. The
# punctuation characters `,' `:' `;' are also ignored.
#
# The run control file format is fully described (with more examples) on the
# fetchmail manual page.
#
# This is what the developer's .fetchmailrc looks like:
defaults
interface "sl0/10.0.2.15" # SLIRP standard address
user esr is esr fetchmail-friends magic-numbers here
fetchall
# Use this for production
poll locke.ccil.org with protocol APOP:
password my_apop_secret;
# Use this to test IMAP
skip locke protocol IMAP:
password my_remote_password;
# Use this to test against POP2 using a local server
skip localhost protocol pop2:
password my_local_password;
|
