Re: Cyrus21-imap, Login error
--- Antonio <toni_olmos@telefonica.net> escribió:
> pedro lopez escribió:
> > --- pedro lopez <listero20042002@yahoo.es>
> escribió:
> >
> >
> >> creo que iba por mal camino.
> >>
> >> les resumo hasta aquí todo lo que he podido
> lograr,
> >> amigos, realmente necesito ayuda con esto, por
> >> mínima
> >> que pueda ser.
> >>
> >> instale los siguientes paquetes:
> >>
> >> apt-get install libsasl2 sasl2-bin
> libsasl2-modules
> >> apt-get install cyrus21-admin cyrus21-common
> >> cyrus21-doc cyrus21-imapd cyrus21-clients
> >>
> >> luego configure el sasl de esta forma y con estos
> >> usuarios:
> >>
> >> /etc/default/saslauthd
> >>
> >> START=yes
> >> MECHANISMS="sasldb"
> >>
> >> /etc/init.d/saslauthd start
> >>
> >> esta seria la salida del sasldblistusers2
> >>
> >> cyrus@svmail
> >> test@svmail
> >> test@mtt.ciao.com
> >>
> >> y en el cyradm el usuario test y todos los
> permisos
> >> con el mismo pass que en el sasl2.
> >>
> >> cuando trato de hacer imtest con este línea:
> >>
> >> $ imtest -a cyrus-w <contraseña> -m login
> localhost
> >>
> >> se provoca este error:
> >>
> >> L01 No Login failed: authentication failure
> >> Authentication failed. Generic failure
> >> Security strength factor:0
> >>
> A mi este error me lo da sólo cuando pongo mal la
> contraseña.
> >> y la salida del imap es esta:
> >>
> >> S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA
> LITERAL+
> >> MAILBOX-REFERRALS NAMESPACE UIDPLUS ID
> >> NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND
> SORT
> >> THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE
> >> ANNOTATEMORE
> >>
> >> ahora aquí esta el syslog:
> >>
> >> Apr 1 13:51:50 svmail cyrus/master[1041]: about
> to
> >> exec /usr/lib/cyrus/bin/imapd
> >> Apr 1 13:51:50 svmail cyrus/imap[1041]: executed
> >> Apr 1 13:51:50 svmail cyrus/imapd[1041]: accepted
> >> connection
> >> Apr 1 13:51:53 svmail cyrus/imapd[1041]:
> badlogin:
> >> localhost.localdomain[127.0.0.1] plaintext root
> >> SASL(-13): authentication failure: checkpass
> failed
> >>
> >> y este es el auth.log
> >>
> >> Apr 1 16:31:24 svmail saslauthd[956]: do_auth :
> auth
> >> failure: [user=root] [service=imap] [realm=]
> >> [mech=sasldb] [reason=Unknown]
> >>
> >> esto es todo lo que he podido sacar en claro
> hasta
> >> el
> >> momento, la configuración tls que había hablado
> en
> >> otros mail, es muy posterior a esto que me esta
> >> ocurriendo ahora, no logro conectarme por otra
> >> causa,
> >> y no doy con lo que es. por favor help.
> >>
> > Antonio.
> >
> > podrias comparar esto con lso tuyos, y decirme si
> > estan ok, estoy pensando que mi lio sea algo con
> los
> > permisos.
> >
> > svmail:# ls -lsa /var/run/saslauthd
> > total 12
> > 4 drwx--x--- 2 root sasl 4096 2006-04-01 13:24 .
> > 4 drwxr-xr-x 10 root root 4096 2006-04-01 13:24 ..
>
> > 0 srwxrwxrwx 1 root root 0 2006-04-01 13:24
> mux
> > 0 -rw------- 1 root root 0 2006-04-01 13:24
> > mux.accept
> > 4 -rw------- 1 root root 4 2006-04-01 13:24
> > saslauthd.pid
> >
> > svmail:# ls -lsa /etc/sasldb2
> > 12 -rw-rw---- 1 cyrus sasl 12288 2006-03-31 19:09
> > /etc/sasldb2
> >
> Lo tengo exactamente igual. Por donde vas, creo que
> solo has modificado
> dos archivos:
> /etc/cyrus.conf
> /etc/imapd.conf
>
> Que tal si pones su contenido? No se si ya lo abras
> hecho anteriormente,
> pero desde este ordenador no tengo acceso a los
> correos antiguos.
>
> Saludos.
sin problemas los pongo, si ya lo habia hecho, pero no
hay lios aqui van, y lo que dices del password tendria
sentido, pero el usuario cyrus, se logea sin ningun
problema en el cyradm. ademas use este comando de
pruebas del sasl
testsaslauthd -u [usuario] -p [pass]
y funciono perfectamente.
aqui van los dos archivos. incluyo tambien el
saslauthd
****************** saslauthd ********************
# This needs to be uncommented before saslauthd will
be run automatically
START=yes
# You must specify the authentication mechanisms you
wish to use.
# This defaults to "pam" for PAM support, but may also
include
# "shadow" or "sasldb", like this:
# MECHANISMS="pam shadow"
MECHANISMS="sasldb"
*********************************************
***************** imapd.conf ******************
# Debian Cyrus imapd.conf
# See imapd.conf(5) for more information and more
options
configdirectory: /var/lib/cyrus
partition-default: /var/spool/cyrus/mail
partition-news: /var/spool/cyrus/news
newsspool: /var/spool/news
altnamespace: no
unixhierarchysep: no
#munge8bit: no
lmtp_downcase_rcpt: yes
admins: cyrus
#lmtp_admins: postman
#mupdate_admins: mupdateman
#imap_admins: cyrus
#sieve_admins: cyrus
#proxyservers: cyrus
allowanonymouslogin: no
popminpoll: 1
autocreatequota: 0
umask: 027
#sendmail: /usr/sbin/sendmail
sieveusehomedir: false
sievedir: /var/spool/sieve
#mailnotifier: zephyr
#sievenotifier: zephyr
#dracinterval: 0
#drachost: localhost
hashimapspool: true
allowplaintext: yes
sasl_mech_list: PLAIN
#allowapop: no
sasl_minimum_layer: 0
#sasl_maximum_layer: 256
#loginrealms:
sasl_pwcheck_method: saslauthd
sasl_auxprop_plugin: sasldb
sasl_auto_transition: no
#tls_cert_file: /etc/ssl/certs/cyrus-global.pem
#tls_key_file: /etc/ssl/private/cyrus-global.key
#tls_imap_cert_file: /etc/ssl/certs/cyrus-imap.pem
#tls_imap_key_file: /etc/ssl/private/cyrus-imap.key
#tls_pop3_cert_file: /etc/ssl/certs/cyrus-pop3.pem
#tls_pop3_key_file: /etc/ssl/private/cyrus-pop3.key
#tls_lmtp_cert_file: /etc/ssl/certs/cyrus-lmtp.pem
#tls_lmtp_key_file: /etc/ssl/private/cyrus-lmtp.key
#tls_sieve_cert_file: /etc/ssl/certs/cyrus-sieve.pem
#tls_sieve_key_file: /etc/ssl/private/cyrus-sieve.key
#tls_ca_file: /etc/ssl/certs/cyrus-imapd-ca.pem
tls_ca_path: /etc/ssl/certs
tls_session_timeout: 1440
tls_cipher_list:
TLSv1:SSLv3:SSLv2:!NULL:!EXPORT:!DES:!LOW:@STRENGTH
#tls_require_cert: false
#tls_imap_require_cert: false
#tls_pop3_require_cert: false
#tls_lmtp_require_cert: false
#tls_sieve_require_cert: false
# mupdate_server
# mupdate_port
# mupdate_username
# mupdate_authname
# mupdate_realm
# mupdate_password
# mupdate_retry_delay
lmtpsocket: /var/run/cyrus/socket/lmtp
idlesocket: /var/run/cyrus/socket/idle
notifysocket: /var/run/cyrus/socket/notify
#debug_command: /usr/bin/gdb -batch -cd=/tmp -x
/usr/lib/cyrus/get-backtrace.gdb /usr/lib/cyrus/bin/%s
%d >/tmp/gdb-backtrace.cyrus.%1$s.%2$d <&- 2>&1 &
#debug_command: /usr/bin/strace -tt -o
/tmp/strace.cyrus.%s.%d -p %2$d <&- 2>&1 &
#debug_command: /usr/bin/ltrace -tt -n 2 -o
/tmp/ltrace.cyrus.%s.%d -p %2$d <&- 2>&1 &
************************************************
**************** cyrus.conf*********************
# Debian defaults for Cyrus IMAP server/cluster
implementation
# see cyrus.conf(5) for more information
#
# All the tcp services are tcpd-wrapped. see
hosts_access(5)
# $Id: cyrus.conf,v 1.16 2003/11/05 01:04:22 hmh Exp $
START {
# do not delete this entry!
recover cmd="/usr/sbin/ctl_cyrusdb -r"
# this is only necessary if using idled for IMAP IDLE
# this is NOT to be enabled right now in Debian
builds
#idled cmd="idled"
# this is useful on backend nodes of a Murder cluster
# it causes the backend to syncronize its mailbox
list with
# the mupdate master upon startup
#mupdatepush cmd="/usr/sbin/ctl_mboxlist -m"
# this is recommended if using duplicate delivery
suppression
delprune cmd="/usr/sbin/ctl_deliver -E 3"
# this is recommended if caching TLS sessions
tlsprune cmd="/usr/sbin/tls_prune"
}
# UNIX sockets start with a slash and are absolute
paths
# you can use a maxchild=# to limit the maximum number
of forks of a service
# you can use babysit=true and maxforkrate=# to keep
tight tabs on the service
# most services also accept -U (limit number of
reuses) and -T (timeout)
SERVICES {
# --- Normal cyrus spool, or Murder backends ---
# add or remove based on preferences
imap cmd="imapd -U 30" listen="imap" prefork=0
maxchild=100
#imaps cmd="imapd -s -U 30" listen="imaps" prefork=0
maxchild=100
#pop3 cmd="pop3d -U 30" listen="pop3" prefork=0
maxchild=50
#pop3s cmd="pop3d -s -U 30" listen="pop3s" prefork=0
maxchild=50
# At least one form of LMTP is required for delivery
# (you must keep the Unix socket name in sync with
imap.conf)
#lmtp cmd="lmtpd" listen="localhost:lmtp" prefork=0
maxchild=20
lmtpunix cmd="lmtpd"
listen="/var/run/cyrus/socket/lmtp" prefork=0
maxchild=20
# ----------------------------------------------
# useful if you need to give users remote access to
sieve
# by default, we limit this to localhost in Debian
sieve cmd="timsieved" listen="localhost:sieve"
prefork=0 maxchild=100
# this one is needed for the notification services
notify cmd="notifyd"
listen="/var/run/cyrus/socket/notify" proto="udp"
prefork=1
# --- Murder frontends -------------------------
# enable these and disable the matching services
above,
# except for sieve (which deals automatically with
Murder)
# mupdate database service - must prefork at least 1
# (mupdate slaves)
#mupdate cmd="mupdate" listen=3905 prefork=1
# (mupdate master, only one in the entire cluster)
#mupdate cmd="mupdate -m" listen=3905 prefork=1
# proxies that will connect to the backends
#imap cmd="proxyd" listen="imap" prefork=0
maxchild=100
#imaps cmd="proxyd -s" listen="imaps" prefork=0
maxchild=100
#pop3 cmd="pop3proxyd" listen="pop3" prefork=0
maxchild=50
#pop3s cmd="pop3proxyd -s" listen="pop3s" prefork=0
maxchild=50
#lmtp cmd="lmtpproxyd" listen="lmtp" prefork=1
maxchild=20
# ----------------------------------------------
}
EVENTS {
# this is required
checkpoint cmd="/usr/sbin/ctl_cyrusdb -c" period=30
# this is only necessary if using duplicate delivery
suppression
delprune cmd="/usr/sbin/ctl_deliver -E 3" at=0401
# this is only necessary if caching TLS sessions
tlsprune cmd="/usr/sbin/tls_prune" at=0401
}
*********************************************
>
>
> --
> To UNSUBSCRIBE, email to
> debian-user-spanish-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>
______________________________________________
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
Reply to: