ERR POP EOF or I/O Error [popper.c:845]

Lord_Icon

Lord_Icon

Member
Scheint ja irgendwas mit Propper zu tun zu haben.

Aber in den Doks finde ich hier nix großes.

Ich poste mal saslfinger -s
Code: 
saslfinger - postfix Cyrus sasl configuration Fr 23. Mai 17:37:52 CEST 2008
version: 1.0.2
mode: server-side SMTP AUTH

-- basics --
Postfix: 2.4.5
System:
Welcome to openSUSE 10.3 (X86-64) - Kernel \r (\l).

-- smtpd is linked to --
        libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00002b0edc03d000)

-- active SMTP AUTH and TLS parameters for smtpd --
broken_sasl_auth_clients = yes
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem
smtpd_tls_ask_ccert = yes
smtpd_tls_cert_file = /etc/postfix/ssl/certs/postfixcert.pem
smtpd_tls_key_file = /etc/postfix/ssl/certs/postfixkey.pem
smtpd_tls_received_header = yes
smtpd_use_tls = no


-- listing of /usr/lib64/sasl2 --
insgesamt 232
drwxr-xr-x  2 root root  4096 12. Mär 18:28 .
drwxr-xr-x 38 root root 36864 17. Mai 21:15 ..
-rwxr-xr-x  1 root root 19008 21. Sep 2007  libanonymous.so
-rwxr-xr-x  1 root root 19008 21. Sep 2007  libanonymous.so.2
-rwxr-xr-x  1 root root 19008 21. Sep 2007  libanonymous.so.2.0.22
-rwxr-xr-x  1 root root 19032 21. Sep 2007  liblogin.so
-rwxr-xr-x  1 root root 19032 21. Sep 2007  liblogin.so.2
-rwxr-xr-x  1 root root 19032 21. Sep 2007  liblogin.so.2.0.22
-rwxr-xr-x  1 root root 23072 21. Sep 2007  libsasldb.so
-rwxr-xr-x  1 root root 23072 21. Sep 2007  libsasldb.so.2
-rwxr-xr-x  1 root root 23072 21. Sep 2007  libsasldb.so.2.0.22

-- listing of /etc/sasl2 --
insgesamt 12
drwxr-xr-x  2 root root 4096 12. Mär 18:30 .
drwxr-xr-x 70 root root 4096 23. Mai 12:20 ..
-rw-------  1 root root   49 19. Dez 13:30 smtpd.conf




-- content of /etc/sasl2/smtpd.conf --
pwcheck_method: saslauthd
mech_list: plain login


-- active services in /etc/postfix/master.cf --
# service type  private unpriv  chroot  wakeup  maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
smtp      inet  n       -       n       -       -       smtpd
pickup    fifo  n       -       n       60      1       pickup
cleanup   unix  n       -       n       -       0       cleanup
qmgr      fifo  n       -       n       300     1       qmgr
tlsmgr    unix  -       -       n       1000?   1       tlsmgr
rewrite   unix  -       -       n       -       -       trivial-rewrite
bounce    unix  -       -       n       -       0       bounce
defer     unix  -       -       n       -       0       bounce
trace     unix  -       -       n       -       0       bounce
verify    unix  -       -       n       -       1       verify
flush     unix  n       -       n       1000?   0       flush
proxymap  unix  -       -       n       -       -       proxymap
smtp      unix  -       -       n       -       -       smtp
relay     unix  -       -       n       -       -       smtp
        -o fallback_relay=
showq     unix  n       -       n       -       -       showq
error     unix  -       -       n       -       -       error
discard   unix  -       -       n       -       -       discard
local     unix  -       n       n       -       -       local
virtual   unix  -       n       n       -       -       virtual
lmtp      unix  -       -       n       -       -       lmtp
anvil     unix  -       -       n       -       1       anvil
scache    unix  -       -       n       -       1       scache
maildrop  unix  -       n       n       -       -       pipe
  flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
cyrus     unix  -       n       n       -       -       pipe
  user=cyrus argv=/usr/lib/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
uucp      unix  -       n       n       -       -       pipe
  flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
ifmail    unix  -       n       n       -       -       pipe
  flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
bsmtp     unix  -       n       n       -       -       pipe
  flags=Fq. user=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
procmail  unix  -       n       n       -       -       pipe
  flags=R user=nobody argv=/usr/bin/procmail -t -m /etc/procmailrc ${sender} ${recipient}
retry     unix  -       -       n       -       -       error

-- mechanisms on localhost --
250-AUTH LOGIN
250-AUTH=LOGIN


-- end of saslfinger output --
--------------------------------------------------------------------------------

Die Fehlermeldung in den Logs lautet im übrigen:

Code: 
May 23 17:17:16 Entwicklungssystem popper[24791]: (v4.0.8) Servicing request from "mailserver.entwickl*****rver.de" at 23.131.45.236 [pop_init.c:1239]
May 23 17:17:16 Entwicklungssystem popper[24791]: ks0176p1 at mailserver.entwickl*****rver.de (23.131.45.236): -ERR POP EOF or I/O Error [popper.c:845]
May 23 17:17:16 Entwicklungssystem popper[24791]: Stats: ks0176p1 0 0 2 6335 mailserver.entwickl*****rver.de 23.131.45.236 [pop_updt.c:301]
May 23 17:17:16 Entwicklungssystem popper[24791]: I/O error flushing output to client ks0176p1 at mailserver.entwickl*****rver.de [23.131.45.236]: Operation not permitted (1) [pop_send.c:693]
May 23 17:17:32 Entwicklungssystem popper[24792]: (v4.0.8) Servicing request from "mailserver.entwickl*****rver.de" at 23.131.45.236 [pop_init.c:1239]
May 23 17:17:33 Entwicklungssystem popper[24792]: Stats: ks0176p1 0 0 2 6335 mailserver.entwickl*****rver.de 23.131.45.236 [pop_updt.c:301]
 
nein. In diesen Posting schreibt man, das ein Viren Prog der Schuldige sei.

Eigendlich bin ich mir sicher, das garkeins läuft. Hab es dennoch nochmal überprüft = kein Virenprog.

Somit kann das nicht die Lösung sein.

Gibt es noch andere Ideen ?

Im Web hab ich mir mal Qpropers Website rausgesucht. Dort wird tatsälich u.a. was von diesen Fehler beschrieben.

What does the error message POP EOF or I/O error mean?
EOF or I/O error almost always means EOF. That is, the network connection with the client dropped unexpectedly.
At the point where this message is issued, Qpopper no longer knows if it was an EOF or an actual I/O error, and so it reports the error number just in case it really is an I/O error (which it almost never is). When it is just an EOF, the associated error is meaningless.


What are maillock errors?
A maillock error indicates a failure to obtain exclusive access to the mail spool. The error number indicates the nature of the problem. More details are usually found in the log.
Here are what the numbers mean:

1: The user name is too long
2: Qpopper was unable to create the dot-lockfile. Check the permissions on the spool directory, and also make sure the user is not over quota and the spool disk is not full.
3: Qpopper was unable to write its process ID into the lockfile. Check if the user is over quota or if the spool disk is full.
4: The spool was locked by another process; perhaps the delivery agent was adding new mail. If this persists, it indicates a problem.
5: Something else went wrong. Check the log for a more detailed error message.
6: Qpopper lost the lock in the middle of locking it. If this persists, it indicates a problem.
Click to expand...

Quota selbst nutze ich nicht. Drum kann ich von recht viel von den Fehlerquellen ausschließen.

Vielleicht kann jm. mal mit mir die 6 Fehlermeldungen durchgehen.
Punkt 1 kann ich abhacken. ks0176p1 = is auf keinen fall zu lang.
Punkt 2: "unable to create the dot-lockfile". Da steht ja, das ich die Zugriffsrechte prüfen soll
Code: 
drwxr-xr-x 11 root  root  4096 26. Mär 14:44 spool
Es steht aber nicht da, was für rechte dieser Ordner benötigt. Weiß hier einer mehr. Oder muß der Benutzername geändert werden. Aber ob dann Postfix da noch zugreifen kann :confused:
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top