Configurando SENDMAIL EN FC8

Hola buenas tardes

El dia de hoy les tengo el siguiente caso

He instalado SENDMAIL en mi FEDORA 8 para la configuracion de un server mail. Todo esta bien cuando me envio correos internos atraves de la red local. cuando le envio a los correos de GMAIL llega todo bien. PERO cuando envio a hotmail o yahoo el servidor me devuelve este mensaje.

The original message was received at Tue, 6 May 2008 17:09:14 -0400
from [192.168.1.92]

----- The following addresses had permanent fatal errors -----
<alternativos2000@hotmail.com>
(reason: 550 DY-001 Mail rejected by Windows Live Hotmail for policy reasons. We generally do not accept emai...l/network admins, please visit http://postmaster.live.com for email delivery information and support)

----- Transcript of session follows -----
... while talking to mx2.hotmail.com.:
>>> MAIL From:<ecvillar@dusa.com.do> SIZE=1336
<<< 550 DY-001 Mail rejected by Windows Live Hotmail for policy reasons. We generally do not accept email from dynamic IP's as they are not typically used to deliver unauthenticated SMTP e-mail to an Internet mail server. http://www.spamhaus.org maintains lists of dynamic and residential IP addresses. If you are not an email/network admin please contact your E-mail/Internet Service Provider for help. Email/network admins, please visit http://postmaster.live.com for email delivery information and support
554 5.0.0 Service unavailable
550 5.1.1 <ecvillar@dusa.com.do>... User unknown

Y CUANDO EJECUTO EL COMANDO tail -f /var/log/maillog Y ENVIO EL MAIL ME APARECE LO SIGUIENTE:

May 6 17:09:14 localhost sendmail[2957]: m46L9EIS002957: from=<ecvillar@dusa.com.do>, size=1151, class=0, nrcpts=1, msgid=<DA9856060813403C998830A18BF1EAAE@laptoplab>, proto=SMTP, daemon=MTA, relay=[192.168.1.92]
May 6 17:09:16 localhost sendmail[2959]: m46L9EIS002957: to=<alternativos2000@hotmail.com>, delay=00:00:02, xdelay=00:00:02, mailer=esmtp, pri=121151, relay=mx2.hotmail.com. [65.54.244.40], dsn=5.0.0, stat=Service unavailable
May 6 17:09:16 localhost sendmail[2959]: m46L9EIS002957: to=<ecvillar@dusa.com.do>, delay=00:00:02, mailer=local, pri=121151, dsn=5.1.1, stat=User unknown
May 6 17:09:16 localhost sendmail[2959]: m46L9EIS002957: m46L9GIS002959: postmaster notify: User unknown
May 6 17:09:16 localhost sendmail[2959]: m46L9GIS002959: to=fulano, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=32360, dsn=2.0.0, stat=Sent
May 6 17:09:24 localhost dovecot: pop3-login: Login: user=<fulano>, method=PLAIN, rip=::ffff:192.168.1.92, lip=::ffff:192.168.1.214
May 6 17:09:24 localhost dovecot: POP3(fulano): Disconnected: Logged out top=0/0, retr=1/4314, del=1/1, size=4296

POR FAVOR HECHENME UNA MANITA DE VERAS LA NECESITO.

Me parece que el problema es que tenés IP dinámica y Yahoo y MSN te toman como SPAM. No se si hay solución para esto, pero revisa este tema, que es el que te esta haciendo rebotar los mails.


gamba47

Hola amigo

Estuve chequiando mis interfaces de red y tengo todo estatico, todas mis IPs estan manualmente.

Espero que alguien me heche una manita.

Hasta la proxima.

No digo que tu PC tenga IP dinamica, si no me refiero a la IP de tu red, es decir, vos que tipo de servicio tenes contratado??? un servicio dedicado con IP fija??? un servicio ADSL residencial?? un servicio de Cablemodem de los que se venden comunmente en el mercado???

Hay que ver cual tenes para determinar si tu ISP te vende internet con IP fija o Dinamica, si es el primer caso lo que hay que hacer es poner en las bases de datos de SPAM que TU IP no hace SPAM, para que todos reciban tus mails, en caso contrario (con IP dinamica) no se como se hace, porque cada 2 dias tu IP cambia sola y es dificil que vuelvas a obtener la misma, tendrias que investigar un poco mas sobre este tema.

Este es uno de los temas por los que un servicio dedicado con IP fija es mas caro que uno comun y corriente.

Saludos. gamba47

En mi empresa tenemos un ADSL a 1.5Mbp. como crees que pueda resolver el problema?

a ver si esto te da una mano

Este me parece que es la solución
http://www.linuxparatodos.net/portal/forum/viewtopic.php?showtopic=29292

http://www.linuxparatodos.net/portal/forum/viewtopic.php?forum=2&showtopic=30665&highlight=spam

Setting up sendmail to use an SMTP server
I have a laptop, and I want, on that laptop, to be able to use mutt to send email from my laptop. These days, this is hard, because of the anti-spam restrictions used. So what I want is to have sendmail send all my mail to another SMTP server.
However, that requires a server that will relay my mail. The ones I have access to are the one I use to read my mail (via fetchmail), and the one that comes with my internet access at home. The authentication mechanism supported by the former requires sending my username and password in clear text. However, the second SMTP server supports encryption (using STARTTLS), so I can use that. (I also don't care much about that password, since I don't use the account.)
Security and SMTP
Take this section with a grain of salt—I'm not an expert on this, and if you really care about security you should check this for yourself. And if that doesn't make you suspicious, the fact that I wrote the whole section from memory after doing all the reading about it two weeks earlier should.
There are two useful security mechanisms that SMTP servers can support:
• One is encrypting the connection. (Some SMTP servers listen for encrypted connections on a different port, but that method of encryption is deprecated. The preferred mechanism is the STARTTLS command, which initiates encryption on an existing connection to port 25.) Encryption prevents someone listening in on the connection (which could mean other hosts on networks on the route, especially if non-switched networks are involved, or compromised routers) from seeing either the login/password or the contents of the mail message. (The contents of the mail message will likely end up being sent in clear text at a later stage, so the latter probably isn't much help.)
• The second is using a type of authentication that doesn't force you to reveal your password. (I'm not sure exactly which authentication types reveal the password, but I know that LOGIN and PLAIN do, and I suspect that most of the others don't.) Using an authentication mechanism that doesn't reveal your password is a good thing because (1) if you're not using encryption, it prevents someone listening in from learning your password and (2) if someone is impersonating the SMTP server to steal passwords, they can't steal your password.
It looks (although I'm not sure) that if an SMTP server supports STARTTLS, then sendmail (acting as an SMTP client) on Red Hat 9 will use it. I know my configuration is using STARTTLS, since I checked with ethereal. I don't know how to set up sendmail to forward to an always-encrypted SMTP server on the alternative port, but it probably isn't too hard. Which authentication mechanisms sendmail (acting as an SMTP client) is willing to use depends on the "M" section of the AuthInfo line (see below).
To tell what the server supports, telnet to the SMTP server on port 25 (telnet smtp.server 25), enter the command EHLO my.host.name and then QUIT. The response to the EHLO will list certain features that the server supports. If the server returns a line saying 250-STARTTLS, then it supports STARTTLS, and the line that begins with 250-AUTH says what authentication mechanisms are supported.
After probing through configuration files and a lot of documentation, I found that this isn't that hard to set up (or wouldn't be, if it were documented). I just had to add three lines (already present, but commented out) to my /etc/mail/sendmail.mc:
• define(`SMART_HOST',`smtp.myisp.net')
• MASQUERADE_AS(`dbaron.org')
• FEATURE(masquerade_envelope)
Then I had to add the authentication information to /etc/mail/access (on which I changed the permissions so it wasn't world-readable):
AuthInfo:smtp.myisp.net "U:username@myisp.net" "I:username@myisp.net" "P:******" "M:LOGIN PLAIN"
(I'm not sure which of the "U" or "I" parts matters, but I'm not really too worried. The list of authentication mechanisms after the "M" gives the authentication mechanisms that the sendmail (acting as a client) will try when authenticating with the server. It must overlap with the mechanisms that the server supports.)
Once I did this, I ran make in /etc/mail (which requires having the sendmail-cf RPM installed) and restarted sendmail (/etc/rc.d/init.d/sendmail restart).
The documentation I had to dig through (after finding it, mostly through Google) to figure this out included:
• Red Hat docs on masquerading and forwarding through a relay (These don't mention authentication, though. If they did, I wouldn't be complaining about lack of documentation. The analogous documentation on postfix didn't mention authentication either, and I couldn't find any documentation online about using postfix with SMTP AUTH.) (Update: Newer postfix documentation suggests that I could do what I want using relayhost and smtp_sasl_password_maps.)
• RFC 2222
• SASL Mechanisms
• SMTP AUTH in sendmail 8.10-8.12 (especially useful)
• Sendmail 8.12 AUTH (especially useful)
________________________________________

(Back to Linux, David Baron)
LDB, dbaron@dbaron.org, 2003-07-31, 2003-08-13


http://dbaron.org/linux/sendmail


ESTA ES LA SOLUCION.

Gracias por compartirla, no te olvides por favor de valorar las respuestas, para que el foro se mantenga ordenado, esta por ejemplo es un COMENTARIO.



gamba47