1 # fetchmail control file sample
3 # This file (or one of your own creation, rather) should be located
4 # in your home directory with the name .fetchmailrc. Permissions on this
5 # file may be no greater than -rw-------, or fetchmail will refuse to
8 # To see what effect your ~/.fetchmailrc file has, do
12 # This will display the fetchmail version number and an explanation
13 # in English of what the currently set options and defaults mean.
15 # Comments begin with a '#' and extend through the end of the line.
16 # Blank lines between server entries are ignored.
17 # Keywords and identifiers are case sensitive.
18 # When there is a conflict between the command-line arguments and the
19 # arguments in this file, the command-line arguments take precedence.
23 # protocol (or proto) -- nuat be followed by a protocol ID
25 # authenticate (or auth) -- must be followed by an authentication type
30 # remotefolder (or remote)
45 # Legal protocol identifiers are
52 # Legal authentication types are
57 # server SERVERNAME protocol PROTOCOL username NAME password PASSWORD
60 server pop.provider.net protocol pop3 username jsmith password secret1
62 # Or, using some abbreviations:
64 server pop.provider.net proto pop3 user jsmith password secret1
66 # Multiple servers may be listed
68 server pop.provider.net proto pop3 user jsmith password secret1
69 server other.provider.net proto pop2 user John.Smith password My^Hat
71 # Other possibilities (note optional use of \ to escape newline -- this is all
72 # one server definition.
73 server pop.provider.net \