Hola, he estado levantando un servidor para algunos clientes y he estado revisando sobre lo que necesito para dejar funcionando los correos tanto desde un cliente de correos como desde php, por el momento tengo instalado postfix y dovecot y nada mas y php anda de lujo (aunque todo cae al spam).
Lo que necesito es un poco de ayuda en cuanto a lo que es correos ya que no soy muy diestro en el tema, lo que si hice correctamente es instalar todos los demás servicios, mysql, httpd, php5, virtualhost, userdir, hice respaldos, migré archivos, les di sus permisos correspondientes a cada uno, los separé por usuario en el sistema, etc.
Estoy utilizando Centos 6.6.
Me han hablado muy bien de zimbra pero la verdad es que cada ves que veo a alguien intentando instalarlo y configurarlo siento que es todo un rompedero de cabeza (no tengo el certificado ssl), por eso opté por postfix y dovecot y lo instalé conforme a lo que conocía y funciona pero como voy agregando las cuentas nuevas?, tengo 3 dominios que apuntan al mismo servidor y un dominio principal que te da el proveedor de hosting asi que dejé configurado ese dominio, pero ahora necesito crear cuentas de correo para los tres dominios por separado y prevenir que se puedan enviar correos de forma anónima y esas cosas.
Alguna idea sobre donde encuentro información o alguien que me oriente un poco?
Necesitas configurar tu postfix para que use el sistema de autentificacion de Dovecot.
http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL
En cuanto a lo de los dominios, lo explican mas o menos aqui:
http://wiki2.dovecot.org/HowTo/VirtualUserFlatFilesPostfix
De hecho, esa pagina tambien es un howto de como configurarlo en conjunto con postfix y es para multiples dominios.
En cuanto a lo del certificado, yo te recomendaría que te compraras uno. Si el servicio lo andan usando en wifis ajenas seria muy facil sniffear el trafico de imap/pop3.
Edit: Otra Alternativa por si no quieres administrar multiples servidores de correo tanto de entrada como de salida:
http://www.zoho.com
Hasta tienen un panel de control para crear cuentas de ahí, aunque creo que cuesta.
Añade en los registros SPF del domnio (DNS) las ip's de los servidores de correo para evitar que lleguen a la carpeta de Spam.
Gracias, de verdad que han sido dos dias perdidos intentando hacer funcionar los registros mx con postfix, dovecot, postfixadmin y roundcube, al final terminé haciendome una cuenta en google apps para mi uso personal, el postfix y el postfixadmin andaban bien pero el dovecot nunca me funcionó para loguearme con las credenciales creadas por el postfix a pesar de que a ambos les puse los mismos tipos de registros y autenticaciones.
Mas adelante yo creo que utilizaré algún servicio externo no porque me complicó instalar todo sino porque me di cuenta el trabajo que hay que tener despues para poder mantener todo y que todo funcione bien, entre el spam, crear filtros, elegir antivirus, el certificado, problemas de seguridad, etc etc, yo creo que me sale mas rentable utilizar un servicio externo a pagarle a alguien que se encargue de mantener el servidor de correos. Cuando salga un trabajo mas grande ahi tocará hacerlo si o si, mientras tanto bucearé en el mar de internet aver si logro dejar todo impecable.
Cita de: WHK en 28 Enero 2015, 02:58 AM
Gracias, de verdad que han sido dos dias perdidos intentando hacer funcionar los registros mx con postfix, dovecot, postfixadmin y roundcube, al final terminé haciendome una cuenta en google apps para mi uso personal, el postfix y el postfixadmin andaban bien pero el dovecot nunca me funcionó para loguearme con las credenciales creadas por el postfix a pesar de que a ambos les puse los mismos tipos de registros y autenticaciones.
Mas adelante yo creo que utilizaré algún servicio externo no porque me complicó instalar todo sino porque me di cuenta el trabajo que hay que tener despues para poder mantener todo y que todo funcione bien, entre el spam, crear filtros, elegir antivirus, el certificado, problemas de seguridad, etc etc, yo creo que me sale mas rentable utilizar un servicio externo a pagarle a alguien que se encargue de mantener el servidor de correos. Cuando salga un trabajo mas grande ahi tocará hacerlo si o si, mientras tanto bucearé en el mar de internet aver si logro dejar todo impecable.
Si ya estas pagando por una cuenta de pago de Google Apps entonces quizas sea lo mejor. Hasta ahora me ha gustado mucho Zoho, ofrecen un servicio premium de 24$ al año y es multi dominio con 10GB por cuenta de usuario. Si no te interesa pagar una cuenta de google apps o premium de zoho, deberias poder crearte 3 cuentas individuales en zoho para cada dominio. En teoría deberias poder agregar varias cuentas de correo por dominio pero es algo que todavia no he probado.
Si, de hecho ayer estuve mirando y se ve que tiene muy buenas soluciones, por ejemplo tiene un ERP muy bueno aunque estoy intentando cotizar con bitbucket, jira y sus productos asociados que ya llevo tiempo usando y son muy buenos.
Finalmente decidí intentar nuevamente siguiendo este blog:
http://www.alcancelibre.org/staticpages/index.php/como-postfix-tls-y-auth
Y me ha funcionado mucho mejor que los demas intentos, por lo menos acá te explica todo con lujo y detalle en español, tiene algunos errores en algunas lineas de código pero nada que no se pueda solucionar, ahora que funciona todo bien y me conecta todo bien debo aprender a crear las cuentas de correo xD ya que por usuario y clave del sistema operativo no funciona no se porque, pero por lo menos conecta y todo.
Me di cuenta que zimbra está diseñado al igual que iredmail para instalarse en un servidor sin ningun otro tipo de servicio, o sea corriendo solo, aunque igual se supone que se pueden tener servicios paralelos pero me ha costado un mundo hacerlos funcionar por lo cual veo muy poco probable que los use, por último roundcube lo puedo montar como cualquier otra pagina.
Cita de: WHK en 28 Enero 2015, 16:39 PM
Y me ha funcionado mucho mejor que los demas intentos, por lo menos acá te explica todo con lujo y detalle en español, tiene algunos errores en algunas lineas de código pero nada que no se pueda solucionar, ahora que funciona todo bien y me conecta todo bien debo aprender a crear las cuentas de correo xD ya que por usuario y clave del sistema operativo no funciona no se porque, pero por lo menos conecta y todo.
Depende de la configuración de Dovecot:
http://wiki2.dovecot.org/HowTo/VirtualUserFlatFilesPostfix#Authentication_Databases
Siguen reglas similares al passwd del sistema, pero igual y tienes otro archivo que no es del sistema.
si, lo mejor es usar Google Apps, para Universidades e Institutos es completamente gratuito. Para ONG's hay decuento, para empresas toca pagar.
Pero te aseguro que te ahorras miles de problemas tal y como comentas, problemas de spam, filtros, espacio, configuración, mantenimiento.
A mi me tocó migrar un servidor de correo imap con Cyrus a Google Apps y Google facilita herramientas para hacer la migración.
Migración correo a Google Apps
http://blog.elhacker.net/2013/04/migracion-correo-e-mails-buzones-google-apps-gmail..html
Por lo menos a empresas medianas y pequeñas puedo darles soporte con google apps y cobrarles cuando necesiten espacio adicionale, el problema es que hay empresas grandes que no quieren que sus correos se vayan a otro servidor por temas de privacidad de datos, asi que en ese casi si o si necesitaré tener todo bien configurado mas a alguien para que les haga el soporte, por ahora no ha pasado tal caso xD asi que no me preocupo pero si debo migrar a dos personas con paginas personales y no puedo cobrarles por google apps.
Seguí un par de instrucciones via youtube xD y ahora si anda todo de lujo, el unico problema es que ahora no permite enviar correos que esten fuera del dominio del servidor, por ejemplo de una cuenta a uno de gmail, dice error relay acces denied, ya averigué y talves sea por un tema de registros mx y todo eso, asi que haré pruebas con un dominio real para ver que tal funciona y si todo sale bien hare un pdf con todos los pasos y configuraciones que tube que hacer para dejar andando correctamente el servidor de correos ya que hay poco y nada de información en español.
Edito:
CitarHubo un error mientras se enviaba el correo: El servidor de correo respondió: 5.7.1 <xxx@gmail.com>: Relay access denied. Revise el destinatario xxx@gmail.com e inténtelo nuevamente.
D:
¿Estas tratando de enviar un correo a gmail?
Debe ser un error de postfix, checa el log:
sudo tail /var/log/mail
#o
sudo tail /var/log/maillog
Citar: Relay access denied.
Normal que no te deje, mejor que no tengas el relay abierto. Prueba autenticandote. Relay es sin contraseña.
[root@server ~]# tail /var/log/maillog
Jan 28 20:11:08 server postfix/smtpd[5150]: disconnect from 181-161-155-199.baf.movistar.cl[181.161.155.199]
Jan 28 20:11:19 server postfix/smtpd[5150]: connect from 181-161-155-199.baf.movistar.cl[181.161.155.199]
Jan 28 20:11:19 server postfix/smtpd[5150]: NOQUEUE: reject: RCPT from 181-161-155-199.baf.movistar.cl[181.161.155.199]: 554 5.7.1 <mi_correo@gmail.com>: Relay access denied; from=<usuario_legitimo@dominio.cl> to=<mi_correo@gmail.com> proto=ESMTP helo=<[192.168.1.43]>
Jan 28 20:11:22 server postfix/smtpd[5150]: disconnect from 181-161-155-199.baf.movistar.cl[181.161.155.199]
Jan 28 20:13:37 server postfix/postfix-script[5176]: stopping the Postfix mail system
Jan 28 20:13:37 server postfix/master[5146]: terminating on signal 15
Jan 28 20:13:42 server dovecot: master: Warning: Killed with signal 15 (by pid=5185 uid=0 code=kill)
Jan 28 20:13:42 server dovecot: imap: Server shutting down. bytes=239/1128
Jan 28 20:13:42 server dovecot: imap: Server shutting down. bytes=120/464
Jan 28 20:13:42 server dovecot: imap: Server shutting down. bytes=509/2325
[root@server ~]#
Los ultimos logs es porque apagué el servicio mientras tanto.
Cita de: WHK en 30 Enero 2015, 16:13 PM
[root@server ~]# tail /var/log/maillog
Jan 28 20:11:08 server postfix/smtpd[5150]: disconnect from 181-161-155-199.baf.movistar.cl[181.161.155.199]
Jan 28 20:11:19 server postfix/smtpd[5150]: connect from 181-161-155-199.baf.movistar.cl[181.161.155.199]
Jan 28 20:11:19 server postfix/smtpd[5150]: NOQUEUE: reject: RCPT from 181-161-155-199.baf.movistar.cl[181.161.155.199]: 554 5.7.1 <mi_correo@gmail.com>: Relay access denied; from=<usuario_legitimo@dominio.cl> to=<mi_correo@gmail.com> proto=ESMTP helo=<[192.168.1.43]>
Jan 28 20:11:22 server postfix/smtpd[5150]: disconnect from 181-161-155-199.baf.movistar.cl[181.161.155.199]
Jan 28 20:13:37 server postfix/postfix-script[5176]: stopping the Postfix mail system
Jan 28 20:13:37 server postfix/master[5146]: terminating on signal 15
Jan 28 20:13:42 server dovecot: master: Warning: Killed with signal 15 (by pid=5185 uid=0 code=kill)
Jan 28 20:13:42 server dovecot: imap: Server shutting down. bytes=239/1128
Jan 28 20:13:42 server dovecot: imap: Server shutting down. bytes=120/464
Jan 28 20:13:42 server dovecot: imap: Server shutting down. bytes=509/2325
[root@server ~]#
Los ultimos logs es porque apagué el servicio mientras tanto.
Postfix no te esta permitiendo hacer de relay para dominio.cl creo yo. En: /etc/postfix/main.cf
mydestination = $myhostname, $mydomain, localhost.localdomain, localhostSi ese dominio no es el principal tienes que asegurarte que este ahi tambien.
mydestination = $myhostname, $mydomain, localhost.localdomain, localhost, dominio.clSi tu dominio esta en la lista de mydestination (que pasa a relay_domains) entonces algo esta mal con las restriciones de relay de postfix o la autentificacion con Devocot. Checa los logs de devocot, al parecer incluyen atentos de autentificación.
Los logs los puedes obtener de:
doveadm log findSi te muestra varios logs, busca en el de err, debug y quizas info. Realmente no estoy seguro en cual este haciendo el log de las auths.
CitarNormal que no te deje, mejor que no tengas el relay abierto. Prueba autenticandote. Relay es sin contraseña.
Como es eso? o sea el postfix no es el relay? debo autentificarme en un relay? mi no entender.
myhostname = mail.dominio.cl
mydomain = dominio.cl
...
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
[root@server postfix]# doveadm log find
Looking for log files from /var/log
Debug: /var/log/maillog
Info: /var/log/maillog
Info: /var/log/messages
Warning: /var/log/maillog
Warning: /var/log/messages
Error: /var/log/maillog
Error: /var/log/messages
Fatal: /var/log/maillog
Fatal: /var/log/messages
[root@server postfix]#
Es un Centos 6.
Cita de: WHK en 30 Enero 2015, 19:33 PM
Como es eso? o sea el postfix no es el relay? debo autentificarme en un relay? mi no entender.
myhostname = mail.dominio.cl
mydomain = dominio.cl
...
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
[root@server postfix]# doveadm log find
Looking for log files from /var/log
Debug: /var/log/maillog
Info: /var/log/maillog
Info: /var/log/messages
Warning: /var/log/maillog
Warning: /var/log/messages
Error: /var/log/maillog
Error: /var/log/messages
Fatal: /var/log/maillog
Fatal: /var/log/messages
[root@server postfix]#
Es un Centos 6.
Bueno, puedes revisar en /var/log/messages (aunque hay mucha info de otros lados tambien). Debes buscar por los mensajes de auth. Me parece que empiezan con auth o contienen: 'client in: AUTH'. I.e. una busqueda:
grep -i auth /var/log/messages
#tambien pueden estar en /var/log/maillog
grep -i auth /var/log/maillogAsegurate tambien que Dovecot tambien este configurado para imprimir la informacion de autentificacion. En el dovecot.conf:
# Authentication configuration:
auth_verbose = yes
# Si es posible usar:
auth_debug = yesTodo esto para descartar que no sea un error de autentificacion de postfix.
En messages:
Jan 30 20:41:10 server dovecot: imap-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: imap-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: imap-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: imap-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:11 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:11 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:11 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
En maillog:
Jan 30 20:41:10 server dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so
Jan 30 20:41:10 server dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so
Jan 30 20:41:10 server dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libmech_gssapi.so
Jan 30 20:41:10 server dovecot: auth: Debug: auth client connected (pid=8176)
Jan 30 20:41:10 server dovecot: auth: Debug: auth client connected (pid=8178)
Jan 30 20:41:10 server dovecot: auth: Debug: auth client connected (pid=8180)
Jan 30 20:41:10 server dovecot: auth: Debug: auth client connected (pid=8182)
Jan 30 20:41:10 server dovecot: auth: Debug: auth client connected (pid=8184)
Jan 30 20:41:10 server dovecot: auth: Debug: auth client connected (pid=8185)
Jan 30 20:41:10 server dovecot: auth: Debug: auth client connected (pid=8186)
Jan 30 20:41:10 server dovecot: auth: Debug: auth client connected (pid=8187)
Jan 30 20:41:10 server dovecot: auth: Debug: auth client connected (pid=8188)
Jan 30 20:41:10 server dovecot: auth: Debug: auth client connected (pid=8190)
Jan 30 20:41:10 server dovecot: imap-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: imap-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: imap-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: imap-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:11 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:11 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:11 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:18 server dovecot: auth: Debug: auth client connected (pid=8193)
Jan 30 20:41:19 server dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011lip=94.23.217.40#011rip=181.161.182.16#011lport=143#011rport=55432
Jan 30 20:41:19 server dovecot: auth: Debug: client out: CONT#0111#011
Jan 30 20:41:20 server dovecot: auth: Debug: client in: CONT<hidden>
Jan 30 20:41:20 server dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth
Jan 30 20:41:20 server dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so
Jan 30 20:41:20 server dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so
Jan 30 20:41:20 server dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libmech_gssapi.so
Jan 30 20:41:20 server dovecot: auth: Debug: pam(usuario_legitimo,181.161.182.16): lookup service=dovecot
Jan 30 20:41:20 server dovecot: auth: Debug: pam(usuario_legitimo,181.161.182.16): #1/1 style=1 msg=Password:
Jan 30 20:41:20 server dovecot: auth: Debug: client out: OK#0111#011user=usuario_legitimo
Jan 30 20:41:20 server dovecot: auth: Debug: master in: REQUEST#0114087218177#0118193#0111#0112f1cecbebd09da181e7bd0d6cd51a509
Jan 30 20:41:20 server dovecot: auth: Debug: passwd(usuario_legitimo,181.161.182.16): lookup
Jan 30 20:41:20 server dovecot: auth: Debug: master out: USER#0114087218177#011usuario_legitimo#011system_groups_user=usuario_legitimo#011uid=501#011gid=501#011home=/home/usuario_legitimo
Jan 30 20:41:23 server dovecot: auth: Debug: auth client connected (pid=8197)
Jan 30 20:41:24 server dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011lip=94.23.217.40#011rip=181.161.182.16#011lport=143#011rport=55434
Jan 30 20:41:24 server dovecot: auth: Debug: client out: CONT#0111#011
Jan 30 20:41:25 server dovecot: auth: Debug: client in: CONT<hidden>
Jan 30 20:41:25 server dovecot: auth: Debug: pam(usuario_legitimo,181.161.182.16): lookup service=dovecot
Jan 30 20:41:25 server dovecot: auth: Debug: pam(usuario_legitimo,181.161.182.16): #1/1 style=1 msg=Password:
Jan 30 20:41:25 server dovecot: auth: Debug: client out: OK#0111#011user=usuario_legitimo
Jan 30 20:41:25 server dovecot: auth: Debug: master in: REQUEST#0113893624833#0118197#0111#011bad5ebfc5a794934d5bdda76a0a955f1
Jan 30 20:41:25 server dovecot: auth: Debug: passwd(usuario_legitimo,181.161.182.16): lookup
Jan 30 20:41:25 server dovecot: auth: Debug: master out: USER#0113893624833#011usuario_legitimo#011system_groups_user=usuario_legitimo#011uid=501#011gid=501#011home=/home/usuario_legitimo
94.23.217.40 es la ip dels ervidor y estoy probando con el dominio de prueba elpalermo.cl
Ojo, esa prueba la hice en una conexión ssl sin el certificado (ya que no lo tengo comprado) pero si está generado y acepté en el thunderbird que sea sitio de confianza.
El tema es que mas que las alertas es que simplemente funcione y funcione bien, asi cuando quede andando podré comprar el certificado y replicarlo en los otros servidores.
No parece ser un error de autentificación:
Jan 30 20:41:25 server dovecot: auth: Debug: client out: OK#0111#011user=usuario_legitimo
El mensaje es OK asi que postfix debe estar autentificado correctamente. Estas usando PAM para autentificar tus usuarios, no estoy seguro si haya un mensaje en los logs de PAM (para ver si hay algo mal ahi).
Todo apunta de nuevo a postfix.
Si quitas la opcion de reject_unauth_destination de smtpd_recipient_restrictions en tu /etc/postfix/main.cf, ¿Te llega el correo?
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks
Edit: Despues de la prueba vuelve a poner el reject_unauth_destination de vuelta. Es solo una prueba y no quieres ser un open relay. Ni que te hagan blacklist por ser un open relay
2nd Edit: Olvida lo anterior. Tal parece que ahora en el /etc/postfix/main.cf se utiliza smtpd_relay_restrictions en lugar de smtp_recipient_restrictions.
smtpd_relay_restrictions =
permit_mynetworks
permit_sasl_authenticated
defer_unauth_destination
https://superuser.com/questions/664516/noqueue-reject-relay-access-denied
Habia visto el tema antes pero no habia caido en cuenta que el tutorial que citaste usa smtpd_recipient_restrictions.
Si, ya lo tengo así, creeme que ya he pasado por todos esos blogs xd
[root@drawcoders dovecot]# cat /etc/postfix/main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
#
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
#
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
#
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
#
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
#
queue_directory = /var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
#
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
#
daemon_directory = /usr/libexec/postfix
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
#
data_directory = /var/lib/postfix
# QUEUE AND PROCESS OWNERSHIP
#
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
#
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
#
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
myhostname = mail.elpalermo.cl
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#
#mydomain = domain.tld
mydomain = elpalermo.cl
# SENDING MAIL
#
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# user@that.users.mailhost.
#
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#
#myorigin = $myhostname
myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
#
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
#
# Note: you need to stop/start Postfix when this parameter changes.
#
inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
#inet_interfaces = localhost
# Enable IPv4, and IPv6 if supported
inet_protocols = ipv4
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
#
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
#
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
#
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
#
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
#
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
#
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
#
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
#
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#
#mydestination = $myhostname, localhost.$mydomain, localhost
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = mail.elpalermo.cl, localhost.elpalermo.cl, localhost, elpalermo.cl, mail.drawcoders.cl, drawcoders.cl, localhost.drawcoders.cl
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
#
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
#
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
#
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
#
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
#
# - You redefine the local delivery agent in master.cf.
#
# - You redefine the "local_transport" setting in main.cf.
#
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
#
# Details are described in the LOCAL_RECIPIENT_README file.
#
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a user@domain.tld address.
#
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
#
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
#
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
#
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
#
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
#
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
#
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
#
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#
#mynetworks_style = class
#mynetworks_style = subnet
mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
#
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
#
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#
mynetworks = 94.23.217.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
#
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
#
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
#
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
#
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
#
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
#
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
#
# If you're connected via UUCP, see also the default_transport parameter.
#
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
#
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a user@domain.tld address.
#
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
#
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
#
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
#
# Specify 0 to disable the feature. Valid delays are 0..10.
#
#in_flow_delay = 1s
# ADDRESS REWRITING
#
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
#
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
#
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
#
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
#
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
#
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
#
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
#
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#
#alias_maps = dbm:/etc/aliases
alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
#
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#
#recipient_delimiter = +
# DELIVERY TO MAILBOX
#
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
#
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
#
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
#
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
#
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#
#mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
# If using the cyrus-imapd IMAP server deliver local mail to the IMAP
# server using LMTP (Local Mail Transport Protocol), this is prefered
# over the older cyrus deliver program by setting the
# mailbox_transport as below:
#
# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
#
# The efficiency of LMTP delivery for cyrus-imapd can be enhanced via
# these settings.
#
# local_destination_recipient_limit = 300
# local_destination_concurrency_limit = 5
#
# Of course you should adjust these settings as appropriate for the
# capacity of the hardware you are using. The recipient limit setting
# can be used to take advantage of the single instance message store
# capability of Cyrus. The concurrency limit can be used to control
# how many simultaneous LMTP sessions will be permitted to the Cyrus
# message store.
#
# To use the old cyrus deliver program you have to set:
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#
#fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
#
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
#
# luser_relay works only for the default Postfix local delivery agent.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#
#luser_relay = $user@other.host
#luser_relay = $local@other.host
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
#
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
#
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
#
# For details, see "man header_checks".
#
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
#
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
#
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
#
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
#
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
#
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
#
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
#
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
#
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
#
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
#
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
#
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
#
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
#
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
#
# The following parameters are used when installing a new Postfix version.
#
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
#
sendmail_path = /usr/sbin/sendmail.postfix
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
#
newaliases_path = /usr/bin/newaliases.postfix
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
#
mailq_path = /usr/bin/mailq.postfix
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
#
setgid_group = postdrop
# html_directory: The location of the Postfix HTML documentation.
#
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
#
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
#
sample_directory = /usr/share/doc/postfix-2.6.6/samples
# readme_directory: The location of the Postfix README files.
#
readme_directory = /usr/share/doc/postfix-2.6.6/README_FILES
smtpd_reject_unlisted_sender = no
smtpd_data_restrictions = reject_unauth_pipelining
address_verify_poll_delay = 3s
message_size_limit = 10240000
smtpd_relay_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination
smtp_helo_name = $myhostname
#smtpd_sender_restrictions = check_sender_access regexp:/etc/postfix/tag_as_originating.re
smtpd_client_restrictions = reject_unauth_pipelining
always_add_missing_headers = yes
#smtpd_recipient_restrictions = permit_sasl_authenticated
smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination
#smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks
De hecho esas ultimas lineas se las copié a un archivo de configuraciones de zimbra.
Creo que tienes que descomentar la linea de relay domains:
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
#
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
#
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
#
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
#
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#
#relay_domains = $mydestination
La ultima linea.
Ya lo descomenté, reinicié los servbicios y me sigue apareciendo el mismo mensaje cuando intento enviar un correo, pero por lo menos ahora si me estan llegando los correos desde gmail por ejemplo :D asi que es un avance xD eso si que desde el thunderbird aparece la bandeja en blanco y no aparece ningún problema de autenticación, y entro desde el ssh desde el comando mail -u usuario y si veo correctamente el correo llegado, raro no?.
[root@drawcoders postfix]# tail /var/log/maillog
Jan 31 16:49:54 drawcoders postfix/smtpd[8558]: connect from mail-qg0-f44.google.com[209.85.192.44]
Jan 31 16:49:54 drawcoders postfix/smtpd[8558]: 38C84CD3FE: client=mail-qg0-f44.google.com[209.85.192.44]
Jan 31 16:49:54 drawcoders postfix/cleanup[8567]: 38C84CD3FE: message-id=<54CCF991.7080604@gmail.com>
Jan 31 16:49:54 drawcoders postfix/qmgr[8529]: 38C84CD3FE: from=<yan.uniko.102@gmail.com>, size=1870, nrcpt=1 (queue active)
Jan 31 16:49:54 drawcoders postfix/local[8569]: 38C84CD3FE: to=<cuenta_real@elpalermo.cl>, relay=local, delay=0.33, delays=0.28/0/0/0.04, dsn=2.0.0, status=sent (delivered to mailbox)
Jan 31 16:49:54 drawcoders postfix/qmgr[8529]: 38C84CD3FE: removed
Jan 31 16:49:54 drawcoders postfix/smtpd[8558]: disconnect from mail-qg0-f44.google.com[209.85.192.44]
Jan 31 16:53:14 drawcoders postfix/anvil[8560]: statistics: max connection rate 1/60s for (smtp:186.79.174.106) at Jan 31 16:48:55
Jan 31 16:53:14 drawcoders postfix/anvil[8560]: statistics: max connection count 1 for (smtp:186.79.174.106) at Jan 31 16:48:55
Jan 31 16:53:14 drawcoders postfix/anvil[8560]: statistics: max cache size 2 at Jan 31 16:49:54
[root@drawcoders postfix]# tail /var/log/messages
Jan 31 16:49:54 drawcoders postfix/smtpd[8558]: connect from mail-qg0-f44.google.com[209.85.192.44]
Jan 31 16:49:54 drawcoders postfix/smtpd[8558]: 38C84CD3FE: client=mail-qg0-f44.google.com[209.85.192.44]
Jan 31 16:49:54 drawcoders postfix/cleanup[8567]: 38C84CD3FE: message-id=<54CCF991.7080604@gmail.com>
Jan 31 16:49:54 drawcoders postfix/qmgr[8529]: 38C84CD3FE: from=<yan.uniko.102@gmail.com>, size=1870, nrcpt=1 (queue active)
Jan 31 16:49:54 drawcoders postfix/local[8569]: 38C84CD3FE: to=<cuenta_real@elpalermo.cl>, relay=local, delay=0.33, delays=0.28/0/0/0.04, dsn=2.0.0, status=sent (delivered to mailbox)
Jan 31 16:49:54 drawcoders postfix/qmgr[8529]: 38C84CD3FE: removed
Jan 31 16:49:54 drawcoders postfix/smtpd[8558]: disconnect from mail-qg0-f44.google.com[209.85.192.44]
Jan 31 16:53:14 drawcoders postfix/anvil[8560]: statistics: max connection rate 1/60s for (smtp:186.79.174.106) at Jan 31 16:48:55
Jan 31 16:53:14 drawcoders postfix/anvil[8560]: statistics: max connection count 1 for (smtp:186.79.174.106) at Jan 31 16:48:55
Jan 31 16:53:14 drawcoders postfix/anvil[8560]: statistics: max cache size 2 at Jan 31 16:49:54
[root@drawcoders postfix]#
Tiene algo de sentido que ahora te lleguen los correos, aunque no estoy seguro porque no te llegan los correos a tu thunderbird. Revisa el mailbox de dovecot, depende de tu configuración en dovecot.conf. Para lo del relay acess denied, prueba comentar smtp d_recipient_ restrictions.
No tengo declarado esa variable:
[root@drawcoders postfix]# cat /etc/dovecot/dovecot.conf
## Dovecot configuration file
# If you're in a hurry, see http://wiki.dovecot.org/QuickConfiguration
# "doveconf -n" command gives a clean output of the changed settings. Use it
# instead of copy&pasting files when posting to the Dovecot mailing list.
# '#' character and everything after it is treated as comments. Extra spaces
# and tabs are ignored. If you want to use either of these explicitly, put the
# value inside quotes, eg.: key = "# char and trailing whitespace "
# Default values are shown for each setting, it's not required to uncomment
# those. These are exceptions to this though: No sections (e.g. namespace {})
# or plugin settings are added by default, they're listed only as examples.
# Paths are also just examples with the real defaults being based on configure
# options. The paths listed here are for configure --prefix=/usr
# --sysconfdir=/etc --localstatedir=/var
# Protocols we want to be serving.
protocols = imap pop3 lmtp
# A comma separated list of IPs or hosts where to listen in for connections.
# "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces.
# If you want to specify non-default ports or anything more complex,
# edit conf.d/master.conf.
#listen = *, ::
listen = *
# Base directory where to store runtime data.
#base_dir = /var/run/dovecot/
# Greeting message for clients.
#login_greeting = Dovecot ready.
# Space separated list of trusted network ranges. Connections from these
# IPs are allowed to override their IP addresses and ports (for logging and
# for authentication checks). disable_plaintext_auth is also ignored for
# these networks. Typically you'd specify your IMAP proxy servers here.
#login_trusted_networks =
# Sepace separated list of login access check sockets (e.g. tcpwrap)
#login_access_sockets =
# Show more verbose process titles (in ps). Currently shows user name and
# IP address. Useful for seeing who are actually using the IMAP processes
# (eg. shared mailboxes or if same uid is used for multiple accounts).
#verbose_proctitle = no
# Should all processes be killed when Dovecot master process shuts down.
# Setting this to "no" means that Dovecot can be upgraded without
# forcing existing client connections to close (although that could also be
# a problem if the upgrade is e.g. because of a security fix).
#shutdown_clients = yes
# If non-zero, run mail commands via this many connections to doveadm server,
# instead of running them directly in the same process.
#doveadm_worker_count = 0
# UNIX socket or host:port used for connecting to doveadm server
#doveadm_socket_path = doveadm-server
##
## Dictionary server settings
##
# Dictionary can be used to store key=value lists. This is used by several
# plugins. The dictionary can be accessed either directly or though a
# dictionary server. The following dict block maps dictionary names to URIs
# when the server is used. These can then be referenced using URIs in format
# "proxy::<name>".
dict {
#quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
#expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext
}
# Most of the actual configuration gets included below. The filenames are
# first sorted by their ASCII value and parsed in that order. The 00-prefixes
# in filenames are intended to make it easier to understand the ordering.
!include conf.d/*.conf
# A config file can also tried to be included without giving an error if
# it's not found:
#!include_try /etc/dovecot/local.conf
# Authentication configuration:
auth_verbose = yes
# Si es posible usar:
auth_debug = yes
Perdon, estaba en /etc/devocot/conf.d/10-mail.conf y esta en la directiva mail_location. Si seguiste ese tutorial que pusiste en la primera pagina debes tener:
mail_location = mbox:~/mail:INBOX=/var/mail/%u
Lo que significa que en /var/mail debe haber una carpeta de tu usuario y dentro deberian estar los correos que has enviado. Si no estan es que nunca llegaron o los borraste al descargarlos (no estoy seguro si thunderbird haga eso). Si los correos estan los mas probable es que tu thunderbird (o cualquier otro MUA que estes usando) este mal configurado.
En cuanto a lo de smtpd_recipient_restrictions, no lo vas a encontrar en el dovecot.conf sino en tu main.cf y es realmente solo una prueba para ver si al comentar el parametro te deja enviar correos.
Trata tambien de enviar un correo de una cuenta de tu servidor a otra cuenta tambien alojada en tu servidor y revisa a ver que pasa.
Nop, ya hice todo eso y aun sigue apareciendo el mismo mensaje, reinicié los servicios y todo :( es raro eh, en fin, seguiré buscando aver que onda.
Cita de: WHK en 1 Febrero 2015, 16:47 PM
Nop, ya hice todo eso y aun sigue apareciendo el mismo mensaje, reinicié los servicios y todo :( es raro eh, en fin, seguiré buscando aver que onda.
¿Pero si tienes el correo en la carpeta de Dovecot? ¿Como estas enviando el correo desde tu thunderbird o directamente con sendmail desde el host?
Podria ser un error de autentificación, en los logs tienes:
Jan 30 20:41:10 server dovecot: imap-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40
Jan 30 20:41:10 server dovecot: pop3-login: Aborted login (no auth attempts): rip=181.161.182.16, lip=94.23.217.40Lo que me hace creer que tu cliente no esta tratando de autentificarse (una de las reglas de smtpd_relay_access es que permite mensajes autentificados), aunque despues se puede ver un login... asi que no estoy seguro.
Si los correos si te estan llegando a tu mailbox de dovecot pero tu thunderbird tampoco los puede ver, todo apunta a un problema del cliente.
Al final lo que hice fue instalar zimbra en un servidor limpiopero con apache en paralelo y le cambié los pueros por defecto a los servicios de zimbra y todo funciona correctamente :) ahora tendré que ver como ponerle el certificado y estamos listos :D pero por lo menos igual se puede entrar a leer y recibir correos.
Gracias por la ayuda, a pesar de que no pude aplicar nada de lo que me dijeron igual me sirvió para aprender mas sobre las configuraciones manuales de los servicios.