Re: unknown_address_reject_code = 550 working random?

2014-01-17 Thread Benny Pedersen

Andrea skrev den 2014-01-16 17:36:


I had many mails rejected with a 450 code for Sender address
rejected: Domain not found, and wanted to change them to a 550 code
to avoid queue on the previous mta.


dig +trace datasolutions.pe

where is dns failing ?

postfix softfails if it cant confirm it is not successfull find the 
domain in question, so if you sure cant find it either, you next step 
would be to make it rejected, not with a code change from softfails but 
with a sender domain reject, if you make hardfails on all domains then 
it will be hard to find why later


unknown_address_reject_code = 550 working random?

2014-01-16 Thread Andrea
Hello,
here I have a strange behaviour from postfix.

I had many mails rejected with a 450 code for Sender address rejected:
Domain not found, and wanted to change them to a 550 code to avoid queue
on the previous mta.

So I added the row:
unknown_address_reject_code = 550
on main.cf and restarted postfix.

Now it seems he does it randomly, and this happens on 3 similar servers.
Some logs as sample:

Jan 16 17:13:24 mta1 postfix/smtpd[19697]: NOQUEUE: reject: RCPT from xxx:
450 xaetapiwij3419...@datasolutions.pe: Sender address rejected: Domain
not found; from=xaetapiwij3419...@datasolutions.pe to=xaetapiwij3419@xxx
proto=ESMTP helo=xxx
Jan 16 17:13:36 mta1 postfix/smtpd[19689]: NOQUEUE: reject: RCPT from xxx:
550 mivaololy1175g@danielmorales.intercast.local: Sender address
rejected: Domain not found;
from=mivaololy1175g@danielmorales.intercast.local to=mivaololy1175@xxx
proto=ESMTP helo=xxx
Jan 16 17:13:36 mta1 postfix/smtpd[19676]: NOQUEUE: reject: RCPT from xxx:
450 yjyawe414...@portalvideo.ro: Sender address rejected: Domain not
found; from=yjyawe414...@portalvideo.ro to=yjyawe4144@xxx proto=ESMTP
helo=xxx

Anyone knows why this happens?
How can I force to have always 550 for inexistent domain on sender address?

This happens on both postfix 2.9.6-2 or 2.2.8-1.2

Thanks,
Andrea


Re: unknown_address_reject_code = 550 working random?

2014-01-16 Thread Noel Jones
On 1/16/2014 10:36 AM, Andrea wrote:
 Hello,
 here I have a strange behaviour from postfix.
 
 I had many mails rejected with a 450 code for Sender address
 rejected: Domain not found, and wanted to change them to a 550 code
 to avoid queue on the previous mta.
 
 So I added the row:
 unknown_address_reject_code = 550
 on main.cf http://main.cf and restarted postfix.
 
 Now it seems he does it randomly, and this happens on 3 similar servers.
 Some logs as sample:
 
 Jan 16 17:13:24 mta1 postfix/smtpd[19697]: NOQUEUE: reject: RCPT
 from xxx: 450 xaetapiwij3419...@datasolutions.pe
 mailto:xaetapiwij3419...@datasolutions.pe: Sender address
 rejected: Domain not found; from=xaetapiwij3419...@datasolutions.pe
 mailto:xaetapiwij3419...@datasolutions.pe to=xaetapiwij3419@xxx
 proto=ESMTP helo=xxx
 Jan 16 17:13:36 mta1 postfix/smtpd[19689]: NOQUEUE: reject: RCPT
 from xxx: 550 mivaololy1175g@danielmorales.intercast.local: Sender
 address rejected: Domain not found;
 from=mivaololy1175g@danielmorales.intercast.local
 to=mivaololy1175@xxx proto=ESMTP helo=xxx
 Jan 16 17:13:36 mta1 postfix/smtpd[19676]: NOQUEUE: reject: RCPT
 from xxx: 450 yjyawe414...@portalvideo.ro
 mailto:yjyawe414...@portalvideo.ro: Sender address rejected:
 Domain not found; from=yjyawe414...@portalvideo.ro
 mailto:yjyawe414...@portalvideo.ro to=yjyawe4144@xxx
 proto=ESMTP helo=xxx
 
 Anyone knows why this happens?
 How can I force to have always 550 for inexistent domain on sender
 address?
 
 This happens on both postfix 2.9.6-2 or 2.2.8-1.2
 
 Thanks,
 Andrea
 


http://www.postfix.org/postconf.5.html#unknown_address_reject_code
... The response is always 450 in case of a temporary DNS error.



  -- Noel Jones


Re: unknown_address_reject_code = 550 working random?

2014-01-16 Thread Wietse Venema
Andrea:
 Anyone knows why this happens?
 How can I force to have always 550 for inexistent domain on sender address?

Postfix will ALWAYS reply 450 after TEMPORARY lookup error.
Doing otherwise would be a mistake.

Wietse


Re: unknown_address_reject_code = 550 working random?

2014-01-16 Thread Andrea
2014/1/16 Wietse Venema wie...@porcupine.org

 Andrea:
  Anyone knows why this happens?
  How can I force to have always 550 for inexistent domain on sender
 address?

 Postfix will ALWAYS reply 450 after TEMPORARY lookup error.
 Doing otherwise would be a mistake.

 Wietse



You mean that after I put unknown_address_reject_code = 550 on
main.cfthe ones rejected with 550 are due to my rule and the ones
rejected with
450 are due to lookup errors?

If yes, it's VERY strange, DNS is responding for sure now. No doubt about
it.

And, second thing: if a domain is not existing you consider this a lookup
error? DNS responds and tells postfix that domain doesn't exist.

Shortly: for me it's ok that postfix replies with 450 for lookup error, but
is there a way to force him to reply with 550 if DNS is responding and
domain is not existing?

Thanks,
Andrea


Re: unknown_address_reject_code = 550 working random?

2014-01-16 Thread Wietse Venema
Andrea:
 2014/1/16 Wietse Venema wie...@porcupine.org
 
  Andrea:
   Anyone knows why this happens?
   How can I force to have always 550 for inexistent domain on sender
  address?
 
  Postfix will ALWAYS reply 450 after TEMPORARY lookup error.
  Doing otherwise would be a mistake.

A lookup error means that there is no reply - the requestor does
not know whether the requested domain exists. This is not to
be confused with a reply that says the domain does not exist.

Wietse


Re: unknown_address_reject_code = 550 working random?

2014-01-16 Thread Andrea
2014/1/16 Wietse Venema wie...@porcupine.org


 A lookup error means that there is no reply - the requestor does
 not know whether the requested domain exists. This is not to
 be confused with a reply that says the domain does not exist.

 Wietse


Ok... I get my error:
postfix replies with Domain not found in both cases, but with 450 if
domain is registered and its DNS is down, and with 550 if domains doesn't
exist. I didn't check existence of domains because I associated Domain not
found with unexistent domain.

Thanks,
Andrea