[contining saga from last week -- I haven't had a chance to pursue it
in the meantime...]

Sorry for not supplying the full dump of info. Doing so would be a bit
much, really, and require much more sanitization. What I was after was
just whether or not other people had encountered similar problems with
abc, and what the solution might be if they had. And to get the box in
question OFF of ORDB's list as quickly as possible, of course...

Few people spoke up, and I've learned in the meantime that handling of
source-routed recipients *has* changed over time. This was a deployment
of postfix-20010228-something, so the larger answer is to get off my butt
and upgrade to a better one. In progress.

Could someone explain the exact processing order with regard to rewriting,
resolving, and recipient restrictions? Since handling of source-routed
recipients is still handled a little oddly here and there, and since the
deployment in question doesn't need to deal with them at all, I think I'm
still best off diking out the part of trivial-rewrite/resolve.c that sets
RESOLVE_FLAG_ROUTED. That was the quick band-aid that fixed the problem in
the original deployment, FYI. No, I don't expect such hacks to be supported,
it's just my own way to simplify the process for cases that don't need
anything more complex.

_H*
-
To unsubscribe, send mail to majordomopostfix.org with content
(not subject): unsubscribe postfix-users

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]