aboutsummaryrefslogtreecommitdiffstats
path: root/INSTALL
blob: 133678c6bd8a5752fc8e5ca90a44a8d91234eb8e (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
		INSTALL Instructions for fetchmail

1. CONFIGURE

Installing fetchmail is easy.  From within this directory, type:

	./configure

The autoconfiguration script will spend a bit of time figuring out the
specifics of your system.  If you want to specify a particular compiler
(e.g. you have gcc but want to compile with cc), set the environment 
variable CC before you run configure.  

The configure script accepts certain standard configuration options.
These include --prefix, --exec-prefix, --bindir, --infodir, --mandir,
and --srcdir.  Do `config --help' for more.

If you're running QNX, edit the distributed Makefile directly.  The
QNX values for various macros are there but commented out; all you
have to do is uncomment them.

2. MAKE 

Next run

	make

This will compile fetchmail for your system.  Note that in order to
build it, you'll need either flex at version 2.5.3 org greater, or lex.

3. INSTALL

Lastly, become root and run

	make install

This will install fetchmail.  By default, fetchmail will be installed
in /usr/local/bin, with the man page in /usr/local/man/man1.  If you
wish to change these defaults, edit the Makefile AFTER you run
"configure" but BEFORE you run "make install."  You can easily choose
a prefix other than /usr/local, or you can choose completely different
directories for each item.

4. SET UP A RUN CONTROL FILE

See the man page or the file sample.rcfile for a description of how to
configure your individual preferences.

Note: if you have been using popclient (the ancestor of this program)
at version 3.0b6 or later, do this

(cd ~; mv ~/.poprc ~/.fetchmailrc)

in order to migrate.

5. TEST

I strongly recommend that your first fetchmail run use the -v and -k
options, in case there is something not quite right with your local
delivery configuration or your port 25 listener.  Also, beware
of aliases that direct your local mail back to the server host!

6. USE IT

Enjoy!