On Wednesday 07 December 2011 10:21:03 Reindl Harald wrote:
> Am 07.12.2011 17:17, schrieb Wietse Venema:
> > Reindl Harald:
> >> Am 07.12.2011 16:59, schrieb Wietse Venema:
> >>> Sebastian Wiesinger:
> >>>> I read these but it's not clear to me. So the transport lookup
> >>>> doesn't work, but why does that prevent postfix from doing a
> >>>> 4xx error code?
> >>>
> >>> You should remove the domains from SQL (or LDAP or other slow
> >>> tables).
> >>>
> >>> Once you do that, smtpd will reply 4xx after email address
> >>> lookup error (it won't reply 4xx when trivial-rewrite can't
> >>> look up the domain).
> >>
> >> the question was WHY it won't
I would guess that the answer to that would require understanding of
Postfix design decisions. It's not likely something which can be
easily covered in an email post.
> > Yes it was. I point the attention to the RIGHT problem, which is
> > fixing the suboptimal configuration that does domain queries from
> > SQL.
>
> this is only "suboptimal" because the behavior to hang instead
> a tempfail, you CAN NOT remive domains from sql if you maintain
> your servers over sql-backends and automatisms where as example
> 10 different machine have to use instantly the same configuration
Nonsense. Recognition of new domains need not be instant. Email is
itself not instant messaging. Domain owners should expect reasonable
delays in changes of domain hosting, and are responsible to plan
accordingly. Your expectations are absurd.
A simple workaround, as I am sure has been suggested on this list
numerous times, is to run a query from a cron job to populate and
postmap the domain lists.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
