[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: problemas con recepcion de correos en servidor postfix



On Fri, 30 Nov 2007, cesar wrote:
> pero se me presento un problema cuando configure el servidor de correo y
> es que no podia recibir correos solamente enviar, hice unos cambios en
> el script del dns para lograr recibir correos y me funciono
> perfectamente pero se me dio el problema que el dia de ayer se me
> arruino la fuente del cpu y al volver a instalarla me dio el mismo error
> que antes descrito adjunto,
> 
> 
> $TTL        86400
> @       IN      SOA     dns.bichos.com. admin.bichos.com. (
>                         2007101601       ; serial, todays date + todays
>   MX      10 www.bichos.com.
> www  MX      10 www.bichos.com.
> bichos.com.      A        xx.x.xxx.x
> www       A       xx.x.xxx.x
> IN      NS      dns.bichos.com.
>         IN      A       xx.x.xxx.x
>         IN      MX      10 bichos.com.
> dns     IN      A       xx.x.xxx.x
> mail    IN      A       xx.x.xxx.x
> www     IN      CNAME   dns
> ftp     IN      CNAME   dns
> 
> el mensaje que reciben los que envian correo a mi servidor es el
> siguiente
> Hi. This is the qmail-send program at yahoo.com.
> I'm afraid I wasn't able to deliver your message to the following
>  addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
> <fdasd@bichos.com>:
> 168.243.82.147 does not like recipient.
> Remote host said: 554 5.7.1 <fdasd@bichos.com>: Relay
>  access denied
> Giving up on 168.243.82.147.

Yopur setup looks very strange:
first of all you should not have had the addresses obfuscated, since it
make the exam very hard and inconcludent.

first note: when i try for such addresses i get: 
dipolo:~# host bichos.com
bichos.com has address 208.229.145.2 
bichos.com mail is handled by 5 mail.netegg.net. 
dipolo:~# host mail.netegg.net 
mail.netegg.net has address 127.0.0.1 
dipolo:~# host 168.243.82.147
147.82.243.168.in-addr.arpa domain name pointer static.147.saltel.net.
dipolo:~#

well ... why public dns show me a 127. address for the mx of bichos.com
???
is possible you have somo inchoherent DSS around for the same domain ?
if static.147.saltel.net does not know he is the mx for bichos.com of
couse is right in bouncing back !!!!





Reply to: