ulturasepp
Goto Top

Fetchmail - wo liegen meine abgeholten Mails?

System: Suse Linux 10.0

In der Logdatei /var/log/fetchmail sehe ich gerade dass fetchmail Emails für einige Konten abgeholt hat.
Die Mails liegen aber nicht im Ordner /var/mail. Es kann sein dass mit Postfix und QPopper etwas nicht stimmt, denn bei intakter Konfiguration lagen die Mails immer in einer Datei in /var/mail. Ich finde sie nicht!

In der fecthmailrc habe ich die Einträge in dieser Art:

poll popserver.de with proto pop3
user '12345' with password 'abcdef' there is 'linuxuser' here

Der User ist angelegt und aktiv!

Aber der Ordner /var/mail ist leer?!?

Werden solche Mails an Postmaster weitergeleitet oder wo sind die hin?

Wo könnten sie sein?

Danke im Voraus

Content-Key: 34120

Url: https://administrator.de/contentid/34120

Ausgedruckt am: 28.03.2024 um 11:03 Uhr

Mitglied: BartSimpson
BartSimpson 13.06.2006 um 11:24:57 Uhr
Goto Top
schau mal nach ob es /var/spool/mail gibt.
PS auch deine config datei von fetchmal währe nicht schlecht!!
Mitglied: Ulturasepp
Ulturasepp 13.06.2006 um 13:44:11 Uhr
Goto Top
Ja /var/spool/mail gibt es. Die beiden sind per Link miteinander verbunden.

Ich habe nur 1 Configdatei gefunden und poste das einfach mal:

/etc/sysconfig/fetchmail

## Path:        Network/Mail/Fetchmail
## Description: Fetchmail init script options
## ServiceRestart: fetchmail
## Type:        integer
## Default:     600
#
# Polling interval in seconds for daemon mode. Mails are regularly
# fetched in this interval.
#
FETCHMAIL_POLLING_INTERVAL=60

## Type:        yesno
## Default:     yes
#
# The default is to retrieve all messages on server. If you want to
# retrieve only new messages and keep old (seen) messages, disable
# this option.
#
FETCHMAIL_FETCHALL=yes

## Type:        yesno
## Default:     no
#
# Fetchmail logs by default all retrieved or kept messages. If you do
# not want to log every single message fetchmail downloads or keeps on
# the server every time it polls, enable this option.
#
FETCHMAIL_SILENT=no

## Type:        string
## Default:     ""  
#
# Any additional fetchmail options. See fetchmail(1) manual page for
# more information.
#
FETCHMAIL_EXPERT_OPTIONS=
Mitglied: BartSimpson
BartSimpson 13.06.2006 um 13:58:32 Uhr
Goto Top
das hilft nicht weiter.
Dann schauen mal die cronjobs durch. Auch die für die user unter /var/XX(wo auch immer Susse die hier ablegt)
Mitglied: Ulturasepp
Ulturasepp 13.06.2006 um 14:27:55 Uhr
Goto Top
Finds nicht - weiss auch nicht genau nach was ich suchen soll!
Kann es irgendwas mit qpopper zu tun haben? Denn der lief vorhin nicht richtig!
Das hier hätte ich noch in Sachen Fetchmail-Settings:

#! /bin/sh
# Copyright (c) 1995-2002 SuSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Stanislav Brabec <sbrabec@suse.cz>
#
# /etc/init.d/fetchmail
#
### BEGIN INIT INFO
# Provides:          fetchmail
# Required-Start:    $syslog $network sendmail
# X-UnitedLinux-Should-Start:
# Required-Stop:     $syslog $network sendmail
# X-UnitedLinux-Should-Stop:
# Default-Start:     3 5
# Default-Stop:      0 1 2 6
# Short-Description: Fetch mails for configured users
# Description:       Start fetchmail as root and fetch mails for configured users.
#       You must create configuration file /etc/fetchmailrc first.
### END INIT INFO
#


# Check for missing binaries (stale symlinks should not happen)
# Note: Special treatment of stop for LSB conformance
FETCHMAIL_BIN=/usr/bin/fetchmail
test -x $FETCHMAIL_BIN || { echo "$FETCHMAIL_BIN not installed";  
        if [ "$1" = "stop" ]; then exit 0;  
        else exit 5; fi; }

# Check for existence of needed config file and read it
FETCHMAIL_CONFIG=/etc/sysconfig/fetchmail
FETCHMAIL_RC=/etc/fetchmailrc
test -r $FETCHMAIL_CONFIG || { echo "$FETCHMAIL_CONFIG not existing";  
        if [ "$1" = "stop" ]; then exit 0;  
        else exit 6; fi; }
test -r $FETCHMAIL_RC || { echo "$FETCHMAIL_RC not existing";  
        if [ "$1" = "stop" ]; then exit 0;  
        else exit 6; fi; }

# Read config
FETCHMAIL_POLLING_INTERVAL=60
FETCHMAIL_FETCHALL=yes
FETCHMAIL_FETCHALL_OPTION=
FETCHMAIL_SILENT=no
FETCHMAIL_SILENT_OPTION=
FETCHMAIL_EXPERT_OPTIONS=
. $FETCHMAIL_CONFIG
if [ $FETCHMAIL_FETCHALL = "yes" ] ; then  
    FETCHMAIL_FETCHALL_OPTION=" -a"  
fi
if [ $FETCHMAIL_SILENT = "yes" ] ; then  
    FETCHMAIL_SILENT_OPTION=" -s"  
fi

# Shell functions sourced from /etc/rc.status:
#      rc_check         check and set local and overall rc status
#      rc_status        check and set local and overall rc status
#      rc_status -v     be verbose in local rc status and clear it afterwards
#      rc_status -v -r  ditto and clear both the local and overall rc status
#      rc_status -s     display "skipped" and exit with status 3  
#      rc_status -u     display "unused" and exit with status 3  
#      rc_failed        set local and overall rc status to failed
#      rc_failed <num>  set local and overall rc status to <num>
#      rc_reset         clear both the local and overall rc status
#      rc_exit          exit appropriate to overall rc status
#      rc_active        checks whether a service is activated by symlinks
#      rc_splash arg    sets the boot splash screen to arg (if active)
. /etc/rc.status

# Reset status of this service
rc_reset

# Return values acc. to LSB for all commands but status:
# 0       - success
# 1       - generic or unspecified error
# 2       - invalid or excess argument(s)
# 3       - unimplemented feature (e.g. "reload")  
# 4       - user had insufficient privileges
# 5       - program is not installed
# 6       - program is not configured
# 7       - program is not running
# 8--199  - reserved (8--99 LSB, 100--149 distrib, 150--199 appl)
#
# Note that starting an already running service, stopping
# or restarting a not-running service as well as the restart
# with force-reload (in case signaling is not supported) are
# considered a success.

case "$1" in  
    start)
        echo -n "Starting fetchmail"  
        ## Start daemon with startproc(8). If this fails
        ## the return value is set appropriately by startproc.
        startproc $FETCHMAIL_BIN -d $FETCHMAIL_POLLING_INTERVAL$FETCHMAIL_FETCHALL_OPTION$FETCHMAIL_SILENT_OPTION $FETCHMAIL_EXPERT_OPTIONS -f $FETCHMAIL_RC -L /var/log/fetchmail 2>&1

        # Remember status and be verbose
        rc_status -v
        ;;
    stop)
        echo -n "Shutting down fetchmail"  
        ## Stop daemon with killproc(8) and if this fails
        ## killproc sets the return value according to LSB.

        killproc -TERM $FETCHMAIL_BIN

        # Remember status and be verbose
        rc_status -v
        ;;
    try-restart|condrestart)
        ## Do a restart only if the service was active before.
        ## Note: try-restart is now part of LSB (as of 1.9).
        ## RH has a similar command named condrestart.
        if test "$1" = "condrestart"; then  
                echo "${attn} Use try-restart ${done}(LSB)${attn} rather than condrestart ${warn}(RH)${norm}"  
        fi
$0 status
        if test $? = 0; then
                $0 restart
        else
                rc_reset        # Not running is not a failure.
        fi
        # Remember status and be quiet
        rc_status
        ;;
    restart)
        ## Stop the service and regardless of whether it was
        ## running or not, start it again.
        $0 stop
        $0 start

        # Remember status and be quiet
        rc_status
        ;;
    force-reload)
        ## Signal the daemon to reload its config. Most daemons
        ## do this on signal 1 (SIGHUP).
        ## If it does not support it, restart.

        echo -n "Reload service fetchmail"  
        ## if it supports it:
        killproc -HUP $FETCHMAIL_BIN
        #touch /var/run/fetchmail.pid
        rc_status -v

        ## Otherwise:
        #$0 stop  &&  $0 start
        #rc_status
        ;;
    reload)
        ## Like force-reload, but if daemon does not support
        ## signaling, do nothing (!)

        # If it supports signaling:
        echo -n "Reload service fetchmail"  
        killproc -HUP $FETCHMAIL_BIN
        #touch /var/run/fetchmail.pid
        rc_status -v

        ## Otherwise if it does not support reload:
        #rc_failed 3
        #rc_status -v
        ;;
    status)
        echo -n "Checking for service fetchmail"  
        ## Check status with checkproc(8), if process is running
        ## checkproc will return with exit status 0.

        # Return value is slightly different for the status command:
        # 0 - service up and running
        # 1 - service dead, but /var/run/  pid  file exists
        # 2 - service dead, but /var/lock/ lock file exists
        # 3 - service not running (unused)
        # 4 - service status unknown :-(
        # 5--199 reserved (5--99 LSB, 100--149 distro, 150--199 appl.)

        # NOTE: checkproc returns LSB compliant status values.
        checkproc $FETCHMAIL_BIN
        # NOTE: rc_status knows that we called this init script with
        # "status" option and adapts its messages accordingly.  
        rc_status -v
        ;;
    probe)
        ## Optional: Probe for the necessity of a reload, print out the
        ## argument to this init script which is required for a reload.
        ## Note: probe is not (yet) part of LSB (as of 1.9)

        test $FETCHMAIL_CONFIG -nt /var/run/fetchmail.pid || test $FETCHMAIL_RC -nt /var/run/fetchmail.pid && echo reload
        ;;
    *)
        echo "Usage: $0 {start|stop|status|try-restart|restart|force-reload|reload}"  
        exit 1
        ;;
esac
rc_exit