Postfix: Sender Non-Delivery Notification...

1. Postfix: Sender Non-Delivery Notification...

Gnu Linux
rkslinux

(usa Debian)

Enviado em 31/07/2009 - 13:30h

Alguém já teve esse problema?

tail -f /var/log/maillog
Jul 31 13:25:55 email amavis[3622]: (03622-17) Passed CLEAN, MYNETS LOCAL [127.0.0.1] [127.0.0.1] <root@email.dominio.com.br> -> <tiger@email.dominio.com.br>, Message-ID: <200907311625.n6VGPsuP010331@email.dominio.com.br>, mail_id: GktJlKgDMADA, Hits: -1.34, size: 608, queued_as: 702A64FCDE, 630 ms
Jul 31 13:25:55 email postfix/smtp[10337]: C564E4FCD2: to=<tiger@email.dominio.com.br>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.7, delays=0.06/0.01/0/0.63, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=03622-17, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 702A64FCDE)
Jul 31 13:25:55 email postfix/qmgr[10328]: C564E4FCD2: removed
Jul 31 13:25:55 email postfix/local[10344]: 702A64FCDE: to=<tiger@email.dominio.com.br>, relay=local, delay=0.06, delays=0.01/0.01/0/0.03, dsn=5.1.1, status=bounced (unknown user: "tiger")
Jul 31 13:25:55 email postfix/cleanup[10336]: 7FD714FCDF: message-id=<20090731162555.7FD714FCDF@email.dominio.com.br>
Jul 31 13:25:55 email postfix/qmgr[10328]: 7FD714FCDF: from=<>, size=3029, nrcpt=1 (queue active)
Jul 31 13:25:55 email postfix/bounce[10346]: 702A64FCDE: sender non-delivery notification: 7FD714FCDF
Jul 31 13:25:55 email postfix/qmgr[10328]: 702A64FCDE: removed
Jul 31 13:25:55 email postfix/local[10344]: 7FD714FCDF: to=<root@email.dominio.com.br>, relay=local, delay=0.02, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (delivered to mailbox)
Jul 31 13:25:55 email postfix/qmgr[10328]: 7FD714FCDF: removed

Se puderem me ajudar, ficarei muito grato!

Atenciosamente,

Robson Oliveira



  


2. Re: Postfix: Sender Non-Delivery Notification...

Adriano Rodrigues Balani
balani

(usa Slackware)

Enviado em 08/08/2009 - 16:01h

Essa mensagem aparece quando o Postfix envia a mensagem ao destinatario e o servidor do destinatario retorna que o usuario não existe lá, tambem pode ocorrer por não haver verificação de host, tipo HELO, SPF, ou Dns Reverso de quem tá enviando.


Abraços.

Adriano R. Balani