aboutsummaryrefslogtreecommitdiffstats
path: root/contrib/fetchmail.logrotate
blob: f8b0f3fbc4bac61975ebd2541f1fce7b613a1fdf (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
# fetchmail.logrotate
#
# This is an example logrotate configuration file, editing required
# before use. It is useful if you have fetchmail logging to a separate
# file, /var/log/fetchmail as shown below.
#
# This file has been written for Debian Linux systems.
#
# Other systems will probably require adjustments, such as: how
# often to rotate, how many files to retain, how to name them, if
# compression is desired, which user and group the file should be
# created with, and where the .pid file is. Check the logrotate
# documentation for details.
#                                        --Matthias Andree, 2007-01-14
# ----------------------------------------------------------------------
# The following license applies to the remainder of this file:
#
# Copyright (c) 2007 Daniel Leidert <daniel.leidert@wgdd.de>
#
# Permission is hereby granted, free of charge, to any person obtaining
# a copy of this software and associated documentation files (the
# "Software"), to deal in the Software without restriction, including
# without limitation the rights to use, copy, modify, merge, publish,
# distribute, sublicense, and/or sell copies of the Software, and to
# permit persons to whom the Software is furnished to do so, subject to
# the following conditions:
#
# The above copyright notice and this permission notice shall be
# included in all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
# EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
# IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
# CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
# TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
# SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

/var/log/fetchmail {
    weekly
    rotate 5
    compress
    missingok
    notifempty
    create 640 fetchmail root
    sharedscripts
    postrotate
        if [ -f /var/run/fetchmail/fetchmail.pid ]; then \
            if [ -x /usr/sbin/invoke-rc.d ]; then \
                invoke-rc.d fetchmail restart > /dev/null; \
            else \
                /etc/init.d/fetchmail restart > /dev/null; \
            fi; \
        fi;
    endscript
}
l library path* where configure will find them. Then configure with --enable-OPIE, and fetchmail build process will detect them and compile appropriately. Note: there is no point in doing this unless your server is OTP-enabled. To test this, telnet to the server port and give it a valid USER id. If the OK response includes the string "otp-", you should install OPIE. You need version 2.32 or better. The OPIE library sources are available at ftp://ftp.inner.net/pub/opie. 2. 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 `configure --help' for more. POP2 support is no longer compiled in by default, as POP2 is way obsolete and there don't seem to be any live servers for it anymore. You can configure it back in if you want with `configure --enable-POP2', but leaving it out cuts the executable's size slightly. Support for CompuServe's RPA authentication method (rather similar to APOP) is available but also not included in the standard build. You can compile it in with `configure --enable-RPA'. Specifying --with-kerberos=DIR will tell the fetchmail build process to look in DIR for Kerberos support. Configure normally looks in /usr/kerberos and /usr/athena; if you specify this option with an argument it will look in DIR first. Unfortunately, there doesn't seem to be good standardization of where Kerberos lives. If your configuration doesn't match one of the four that fetchmail's configure.in knows about, you may find you have to hand-hack the Makefile a bit. If you want to build for debugging, CFLAGS=-g LDFLAGS=" " ./configure will do that. 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. 3. MAKE You may find you need flex at version 2.5.3 or greater to build fetchmail. The stock lex distributed with some versions of Linux does not work -- it yields a parser which core-dumps on syntax errors. You can get flex at the GNU ftp site, ftp://prep.ai.mit.edu/pub/gnu. Run make This should compile fetchmail for your system. If fetchmail fails to build properly, see the FAQ section B on build-time problems. 4. 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. You can use the configure options --bindir and --mandir to change these. NOTE: If you are using an MTA other than sendmail (such as qmail, exim, or smail), see the FAQ (section T) for discussion of any special configuration steps that may be necessary. 5. SET UP A RUN CONTROL FILE See the man page and the file sample.rcfile for a description of how to configure your individual preferences. If you're upgrading from popclient, see question F4 in the FAQ file. 6. 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 server, your local delivery configuration or your port 25 listener. Also, beware of aliases that direct your local mail back to the server host! This software is known to work with the qpop/popper series of freeware POP3 servers; also with the IMAP2bis and IMAP4 servers that are distributed with Pine from the University of Washington; also with the Cyrus IMAP server from CMU. This covers all the servers normally hosted on Linux and *BSD systems. It also works with Microsoft Exchange, despite the fact that Microsoft Exchange is extremely broken (returns incorrect message lengths in LIST responses). 7. REPORTING BUGS You should read the FAQ file question G3 before reporting a bug. 8. USE IT Once you've verified your configuration, you can start fetchmail to run in background and forget about it. Enjoy!