blob: b7d0a9451d5d6576382d0fab9c9103b31b83cf4d (
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
|
# 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
# server
# protocol (or proto)
# username (or user)
# is
# remotefolder (or remote)
# password (or pass)
# mailbox
# smtphost (or smtp)
# mda
# keep
# flush
# fetchall
# rewrite
# skip
# nokeep
# noflush
# nofetchall
# norewrite
# noskip
# port
#
# Legal protocol identifiers are
# pop2 (or POP2)
# pop3 (or POP3)
# imap (or IMAP)
# apop (or APOP)
# rpop (or RPOP)
#
# Basic format is
# server SERVERNAME protocol PROTOCOL username NAME password PASSWORD
# Example:
#
server pop.provider.net protocol pop3 username jsmith password secret1
# Or, using some abbreviations:
#
server pop.provider.net proto pop3 user jsmith password secret1
# Multiple servers may be listed
#
server pop.provider.net proto pop3 user jsmith password secret1
server other.provider.net proto pop2 user John.Smith password My^Hat
# Other possibilities (note use of \ to escape newline -- this is all
# one server definition.
server pop.provider.net \
proto pop3 \
user jsmith \
pass secret1
|
