problem mit email nach upgrade

[kurgans]

hallo

weiss jemand warum dieser Fehler nach einem Upgrade entsteht?

Apr 27 11:26:34 www couriertcpd: authdaemon: s_connect() failed: Connection refused
Apr 27 11:26:34 www couriertcpd: [Hint: perhaps authdaemond is not running?]
Apr 27 11:26:34 www couriertcpd: authentication error: Connection refused

die "Daemons" laufen einwandfrei im System

Stopping SASL Authentication Daemon: saslauthd.
Starting SASL Authentication Daemon: saslauthd.
Stopping Courier authentication services: authdaemond.
Starting Courier authentication services: authdaemond.

die Ports sind auf Listen

tcp6 0 0 :::110 :::* LISTEN
tcp6 0 0 :::143 :::* LISTEN
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 :::21 :::* LISTEN
tcp6 0 0 :::53 :::* LISTEN

aber ich bekomme ein error beim versenden von Emails und beim Eingang ins Webmail

Danke im voraus

Antonio

[rbtux]

deine daemons lauschen laut deiner aussage nur an ipv6 ist das gewollt?

[kurgans]

die tcp6 configuration wurde vom upgrade erstellt, wie kann ich die daemon ändern damit ein anderes kommunikationsprotokoll funktioniert?

Ports sind auf Listen
tcp 0 0 http://www.bongostudio.es:60000 *:* LISTEN
tcp 0 0 http://www.bongostudio.es:10025 *:* LISTEN
tcp 0 0 *:mysql *:* LISTEN
tcp 0 0 *:submission *:* LISTEN
tcp 0 0 http://www.bongostudio.es:12525 *:* LISTEN
tcp 0 0 *:sunrpc *:* LISTEN
tcp 0 0 *:ssmtp *:* LISTEN
tcp 0 0 *:auth *:* LISTEN
tcp 0 0 http://www.bongostudio.es.l:9876 *:* LISTEN
tcp 0 0 http://www.bongostudio.es:domain *:* LISTEN
tcp 0 0 http://www.bongostudio.es:domain *:* LISTEN
tcp 0 0 *:smtp *:* LISTEN
tcp 0 0 http://www.bongostudio.es.:953 *:* LISTEN
tcp 0 0 *:46461 *:* LISTEN
tcp6 0 0 [::]:pop3 [::]:* LISTEN
tcp6 0 0 [::]:imap2 [::]:* LISTEN
tcp6 0 0 [::]:www [::]:* LISTEN
tcp6 0 0 [::]:domain [::]:* LISTEN
tcp6 0 0 [::]:ftp [::]:* LISTEN
tcp6 0 0 [::]:ssh [::]:* LISTEN
tcp6 0 0 ip6-localhost:953 [::]:* LISTEN

getnameinfo failed
getnameinfo failed

[hxbro]

Sorry, this isn't in german

I had a problem with courier and not logging in, I had to add the following to the end of pop3d and imapd config files:

##NAME: MAILDIRPATH:0
#
# MAILDIRPATH - directory name of the maildir directory.
#
MAILDIRPATH=Maildir

[joximu]

@all upgraders:
look and take for the *original* (from distribution, not from ispcp) imapd and pop3d files - and also authdaemonrc, where only one line has to be changed/expanded to
authmodulelist="authuserdb authpam";

/J

[kurgans]

I it, and feel it to post a problem hear that is not of the ispcp,
but when I always have some problem hear receipt helps.

THANK YOU FOR YOUR HELP AND PATIENCE

[kurgans]

Sorry don´t work, You can say something to me but that to be able to make Thanks

VERSION: $Id: authdaemonrc,v 1.3 2003/08/08 14:12:58 lisp Exp $
#
# Copyright 2000-2001 Double Precision, Inc. See COPYING for
# distribution information.
#
# authdaemonrc created from authdaemonrc.dist by sysconftool
#
# Do not alter lines that begin with ##, they are used when upgrading
# this configuration.
#
# This file configures authdaemond, the resident authentication daemon.
#
# Comments in this file are ignored. Although this file is intended to
# be sourced as a shell script, authdaemond parses it manually, so
# the acceptable syntax is a bit limited. Multiline variable contents,
# with the \ continuation character, are not allowed. Everything must
# fit on one line. Do not use any additional whitespace for indentation,
# or anything else.

##NAME: authmodulelist:0
#
# The authentication modules that are linked into authdaemond. The
# default list is installed. You may selectively disable modules simply
# by removing them from the following list. The available modules you
# can use are: authcustom authcram authuserdb authldap authpgsql authmysql authpam

authmodulelist="authuserdb authpam";

##NAME: authmodulelistorig:1
#
# This setting is used by Courier's webadmin module, and should be left
# alone

authmodulelistorig="authcustom authcram authuserdb authldap authpgsql authmysql authpam"

##NAME: daemons:0
#
# The number of daemon processes that are started. authdaemon is typically
# installed where authentication modules are relatively expensive: such
# as authldap, or authmysql, so it's better to have a number of them running.
# PLEASE NOTE: Some platforms may experience a problem if there's more than
# one daemon. Specifically, SystemV derived platforms that use TLI with
# socket emulation. I'm suspicious of TLI's ability to handle multiple
# processes accepting connections on the same filesystem domain socket.
#
# You may need to increase daemons if as your system load increases. Symptoms
# include sporadic authentication failures. If you start getting
# authentication failures, increase daemons. However, the default of 5
# SHOULD be sufficient. Bumping up daemon count is only a short-term
# solution. The permanent solution is to add more resources: RAM, faster
# disks, faster CPUs...

daemons=5

##NAME: version:0
#
# When you have multiple versions of authdaemond.* installed, authdaemond
# just picks the first one it finds. Set "version" to override that.
# For example: version=authdaemond.plain

version=""

##NAME: authdaemonvar:0
#
# authdaemonvar is here, but is not used directly by authdaemond. It's
# used by various configuration and build scripts, so don't touch it!

authdaemonvar=/var/run/courier/authdaemon

[joximu]

Hi

which services are you trying to run or which services are you ruinning?

eg. a special sasl service like saslauthd is not needed with ispCP.

/J

[kurgans]

Ich habe gesehen dass mein problem im Archiv Linux host sein könnte

# 'hosts' file configuration.

127.0.0.1 bongostudio.es.local localhost
89.185.255.29 bongostudio.es isp
::ffff:208.53.147.172 bongostudio.es isp
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

ich habe vergessen eine IP zu ändern die das Protokoll IPV6 zuweist. Ich werde heute Nacht den Server neu starten um ein upgrade zu machen. Dann werde ich sehen ob das Problem behoben wurde.

[joximu]

ja, da scheint was nicht zu stimmen...

vielleicht nimmst du dir das nächste mal noch das Kapitel full-qualified-Hostname vor... :-)