Mis saludos;
siguen los problemas con postfix :-(
Estoy configurando un servidor Postfix (3.10.1) en un contenedor CentOS7 de
Proxmox 4. Mi idea es configurarlo con SASL y TLS pero estoy presentando
problemas con la configuración del SASL. Cuando trato de enviar un correo no me
lo entrega y es por que el SASL. Según las trazas el mecanismo de
autenticación tiene problemas o no existe.
*************
Feb 26 09:14:36 gtmem postfix/smtpd[12939]: initializing the server-side TLS
engine
Feb 26 09:14:36 gtmem postfix/smtpd[12939]: connect from
rommel.gtm.onat.gov.cu[192.168.41.6]
Feb 26 09:14:36 gtmem postfix/smtpd[12939]: warning: SASL authentication
failure: Internal Error -4 in server.c near line 1757
Feb 26 09:14:36 gtmem postfix/smtpd[12939]: warning: SASL authentication
failure: Internal Error -4 in server.c near line 1757
Feb 26 09:14:36 gtmem postfix/smtpd[12939]: warning: SASL authentication
failure: Internal Error -4 in server.c near line 1757
Feb 26 09:14:36 gtmem postfix/smtpd[12939]: warning:
xsasl_cyrus_server_get_mechanism_list: no mechanism available
Feb 26 09:14:36 gtmem postfix/smtpd[12939]: fatal: no SASL authentication
mechanisms
Feb 26 09:14:37 gtmem postfix/master[11805]: warning: process
/usr/libexec/postfix/smtpd pid 12939 exit status 1
Feb 26 09:14:37 gtmem postfix/master[11805]: warning:
/usr/libexec/postfix/smtpd: bad command startup -- throttling
Feb 26 09:16:17 gtmem postfix/anvil[12940]: statistics: max connection rate
1/60s for (smtp:192.168.41.6) at Feb 26 09:14:36
Feb 26 09:16:17 gtmem postfix/anvil[12940]: statistics: max connection count 1
for (smtp:192.168.41.6) at Feb 26 09:14:36
Feb 26 09:16:17 gtmem postfix/anvil[12940]: statistics: max cache size 1 at Feb
26 09:14:36
*************
pero cuando miro:
**************
[root@gtmem sasl2]# cat /etc/sasl2/smtpd.conf
pwcheck_method: saslauthd
mech_list: plain login
**************
es decir, si existe y el servicio saslauthd está levantado y corriendo:
**************
[root@gtmem sasl2]# systemctl status saslauthd.service
saslauthd.service - SASL authentication daemon.
Loaded: loaded (/usr/lib/systemd/system/saslauthd.service; enabled)
Active: active (running) since vie 2016-02-26 09:15:42 EST; 1h 25min ago
Process: 12951 ExecStart=/usr/sbin/saslauthd -m $SOCKETDIR -a $MECH $FLAGS
(code=exited, status=0/SUCCESS)
Main PID: 12959 (saslauthd)
CGroup: /lxc/105/system.slice/saslauthd.service
├─12959 /usr/sbin/saslauthd -m /run/saslauthd -a pam
├─12960 /usr/sbin/saslauthd -m /run/saslauthd -a pam
├─12961 /usr/sbin/saslauthd -m /run/saslauthd -a pam
├─12962 /usr/sbin/saslauthd -m /run/saslauthd -a pam
└─12963 /usr/sbin/saslauthd -m /run/saslauthd -a pam
feb 26 09:15:42 gtmem.gtm.onat.gob.cu saslauthd[12959]: detach_tty :
master pid is: 12959
feb 26 09:15:42 gtmem.gtm.onat.gob.cu saslauthd[12959]: ipc_init :
listening on socket: /run/saslauthd/mux
feb 26 09:15:42 gtmem.gtm.onat.gob.cu systemd[1]: Started SASL authentication
daemon..
**************
La otra configuración que inflfuye en esta configuración es lo que hay en
/etc/sysconfig/saslauthd y lo tengo así:
**************
[root@gtmem sasl2]# cat /etc/sysconfig/saslauthd
# Directory in which to place saslauthd's listening socket, pid file, and so
# on. This directory must already exist.
SOCKETDIR=/run/saslauthd
# Mechanism to use when checking passwords. Run "saslauthd -v" to get a list
# of which mechanism your installation was compiled with the ablity to use.
MECH=pam
# Additional flags to pass to saslauthd on the command line. See saslauthd(8)
# for the list of accepted flags.
FLAGS=
**************
Que me falta? o que pudiera estar influyendo (en caso que no fuera por el
SASL) en que no trabaje correctamente el servicio de mensajería electrónica?
--
Rommel Rodriguez Toirac
Administrador de red ONAT Guantánamo
Teléfono (pizarra): 327444,326625,326376,327677,326576
Extensión: 120
______________________________________________________________________
Lista de correos del Grupo de Usuarios de Tecnologías Libres de Cuba.
Gutl-l@jovenclub.cu
https://listas.jovenclub.cu/cgi-bin/mailman/listinfo/gutl-l
