Hola...no se si me estoy poniendo pesado con esto, pero es que desde la
actualizaci�n no me funciona ni el envio ni la recepci�n de mensajes
(reecivirlos los recivo pero no puedo leerlos). Para empezar os pongo un
ejemplo de lo que ocurre cuando hago mailq
[EMAIL PROTECTED] (/home/ijalonso)$ mailq
# Me salen 84 mensajes como los ejemplos de abajo, desde el dia 15 que
# actualiz� #
m115vNY-000jvYL From: root (in /var/spool/smail/input)
Date: Sun, 18 Jul 1999 20:09:36 +0200 (CEST)
Args: -oem -f [email protected] -oMs
localhost -oMa 127.0.0.1 -oMr esmtp -oMu ijalonso
-oMv rfc1413 -oMP in.smtpd <[EMAIL PROTECTED]>
m113mor-000jq8b From: root (in /var/spool/smail/input)
Date: Mon, 12 Jul 1999 22:36:57 +0200 (CEST)
Args: -oem -f [EMAIL PROTECTED] -oMs localhost -oMa
127.0.0.1 -oMr esmtp -oMu ijalonso -oMv rfc1413
-oMP
in.smtpd <[EMAIL PROTECTED]>
m113mot-000jsbb From: root (in /var/spool/smail/input)
Date: Mon, 12 Jul 1999 22:36:59 +0200 (CEST)
Args: -oem -f [EMAIL PROTECTED] -oMs localhost -oMa
127.0.0.1 -oMr esmtp -oMu ijalonso -oMv rfc1413
-oMP
in.smtpd <[EMAIL PROTECTED]>
m113mp3-000jt3b From: root (in /var/spool/smail/input)
Date: Mon, 12 Jul 1999 22:37:09 +0200 (CEST)
Args: -oem -f [EMAIL PROTECTED] -oMs localhost
-oMa 127.0.0.1 -oMr esmtp -oMu ijalonso -oMv
rfc1413
-oMP in.smtpd <[EMAIL PROTECTED]>
m113mpx-000jtUb From: root (in /var/spool/smail/input)
Date: Mon, 12 Jul 1999 22:38:05 +0200 (CEST)
Args: -oem -f [EMAIL PROTECTED] -oMs localhost -oMa
127.0.0.1 -oMr esmtp -oMu ijalonso -oMv rfc1413
-oMP
in.smtpd <[EMAIL PROTECTED]>
�Podr�a tener algo que ver el hecho de que antes en la direcci�n
apareciera <[EMAIL PROTECTED]> o <[EMAIL PROTECTED]> (no estoy seguro) en
lugar de hacer referencia a localhost?
Mas informaci�n sobre mutt
[EMAIL PROTECTED] (/home/ijalonso)$ mutt -v
Mutt 0.95.3i (1999-02-12)
Copyright (C) 1996-8 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type
utt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type
utt -vv' for details.
System: Linux 2.0.34 [using slang 10202]
Compile options:
-DOMAIN
-HOMESPOOL +USE_SETGID +USE_DOTLOCK -USE_FCNTL -USE_FLOCK
+USE_IMAP +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR
+HAVE_PGP5
+HAVE_PGP2 +HAVE_GPG -BUFFY_SIZE
-EXACT_ADDRESS +ENABLE_NLS
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/spool/mail"
SHAREDIR="/usr/share/mutt"
SYSCONFDIR="/etc"
ISPELL="/usr/bin/ispell"
_PGPPATH="/usr/bin/pgp"
_PGPV2PATH="/usr/bin/pgp"
_PGPV3PATH="/usr/bin/pgp"
Para contactar los autores mande un correo a <[EMAIL PROTECTED]>.
Os adjunto tambien el config del smail y la forma en que invoco a
fetchmail dentro del archivo ineton. No pongo mas datos por que me
parece que esto me esta quedando largu�simo. Los log del smail los mando
en otro correo.
Gracias por vuestra ayuda
[EMAIL PROTECTED] escribi�:
>
> ::::: En el art�culo <[EMAIL PROTECTED]>, "Ignacio
> J. Alonso" <[EMAIL PROTECTED]> dec�a:
>
> Ignacio:: Hola... no se si este mensaje llegar� o no (si creo que
> Ignacio:: los que mando si que van), desde que he actualizado a
> Ignacio:: slink el mutt no me ve los mensajes nuevos, pero
> Ignacio:: tenerlos los tengo o por lo menos mi directorio
> Ignacio:: /var/spool/smail/input lo tengo abarrotado de
> Ignacio:: archivos. Antes para ver si tenia archivos por enviar
> Ignacio:: hacia mailq, pero ahora esto me da una ristra de
> Ignacio:: archivos... estoy bastante perdido..... �es culpa de
> Ignacio:: mutt? �es culpa de procmail? �podeis orientarme? --
>
> Hola.
>
> He respondido ya en otro mail, pero por si acaso te indico: la culpa
> es probablemente de smail. Lo que deber�as comprobar es c�mo invocas
> a fetchmail (si env�a los mensajes al puerto 25 o est� en modo mda) y
> si en los log de smail aparecen problemas (que deber�a).
>
> Un saludo.
>
> --
>
> RESET
--
=======NaClU2===============================================
_/ _/ _/_/_/ _/_/_/ Desde: 40�25'N 3�39'O
_/ _/ _/ _/ _/
_/ _/ _/ _/_/_/ _/_/_/ mailto:[EMAIL PROTECTED]
_/ _/ _/ _/ _/ _/
_/ _/_/_/ _/ _/ _/_/_/ http://web.jet.es/ijalonso
============================================================# This is the main Smail configuration file.
# It was originally generated by `smailconfig', part of the Smail package
# distributed with Debian, but it may edited by the mail system administrator.
# It was originally generated by smailconfig at Sun Apr 12 18:47:49 CEST 1998
# Please modify the above line, if you change this file by hand.
# See smailconf(5) for details of the things that can be configured here.
visible_name=jet.es
-domains
hostnames=T1000.cyb.org
max_load_ave=5
smtp_accept_max=20
smtp_accept_queue=10
rfc1413_query_timeout=15
require_configs
-second_config_file
-qualify_file
-retry_file
copying_file=/usr/doc/smail/copyright
max_message_size=10M
received_field="Received: \
${if def:sender_host\
{from $sender_host ${if def:sender_host_addr ([$sender_host_addr]) }}\
{${if def:sender_host_addr:from [$sender_host_addr] }}}\
by $primary_name\n\t\
${if def:sender_proto: with $sender_proto }\
${if def:ident_sender:(ident $ident_sender using $ident_method) }\
id $message_id\n\t\
(Debian $version_string); $spool_date"
# Debian Config Version 2.1
# ----------Begin-----------
# You really should know what you do here!
#WARNING: You will have to add a correct local definition for
# smtp_remote_allow if you have many local networks, or unset it
# if you wish to disable this feature (default).
#WARNING: The current implementation of this feature blocks
# relay from incoming SMTP to *any* outgoing transport. This
# means that even UUCP gateways require explicit permission if
# this feature is enabled.
# it's off by default, so all hosts can relay mails over this host.
# example to switch it on, and allow relay from localnet hosts:
# normally it's not wrong to turn this on ...
#smtp_remote_allow=localnet
# This flag tells smail to verify the hostnames given in
# HELO or EHLO SMTP commands.
# it's off by default
# example to switch it on:
#+smtp_hello_verify
# more helo/ehlo verify switches, see manpages for details
#smtp_hello_verify_literal
#smtp_hello_verify_ptr
# A colon-separated list of host IP patterns that are
# allowed to deliver mail even though they have broken
# DNS or give incorrect or invalid HELO or EHLO SMTP
# greetings.
# it's off by default, which mean smtp_hello_broken_allow=*
# example to switch it on:
#smtp_hello_broken_allow=192.168.100.*
# Vixie / MAPS RBL (http://maps.vix.com/rbl)
# switch to turn on the Mail Abuse Protection System (MAPS)
# it's off by default
# example to switch it on:
#+vixie_rbl
#vixie_rbl_force_allow="192.168.100.10:[your local ip#]"
# Do not do dns lookups for MAIL FROM: address
# This is debian-Smail only feature... it WILL BE DELETED in the future
# It's only use is for local systems with no working dns System
# It's off by default
# example to switch it on:
#+smtp_sender_verify
#!/bin/sh
#
# ineton
#
# -------- Conectar a Internet --------
# Lanzar el demonio pppd:
pon
# Mirar en los log como va la conexion
(tail -f /var/log/messages | egrep "ppd||chat")&
# -------- Coger/Enviar correo --------
# Normalmente se tardan 35 - 40 seg. en conectar
sleep 40
# Mato el plog
killall -v -9 tail
#Mando el correo en la cola:
smail -q
# Llamo a fetchmail:
fetchmail -d 600 -v -L /home/ijalonso/etc/fetchmail.log
# Se va viendo el log de fetchmail en la consola 8
(tail -f /home/ijalonso/etc/fetchmail.log > /dev/tty8) &
