On Wed, Apr 20, 2016, at 05:13 PM, Wietse Venema wrote: > This is what happens in the simple case. > > 1) smtpd talks to the cleanup server. > > 2) cleanup writes a probe message to the queue. > > 3) qmgr selects a delivery agent. > > 4) The delivery agent does a partial delivery attempt and reports > results to the verify daemon. > > 5) The verify daemon updates the verify database. > > 6) smtpd retrieves the result from the verify database.
That's a great summary. I need to go back and stare some more at the diagrams in the docs. Thanks. > It gets more complicated with external content filters. In that > case, step 1) effectively talks to the after-filter cleanup server. > If you configured your virtual aliasing *before* the content filter, > then the probe message will miss that. In other words you would > need to expand aliases after the content filter. The aliasing is done on the backend. All addresses & aliases are managed there. That's why I'm attempting the remote address_verification; the frontend has none of this information atm. I don't use virtual aliases. Virtual transport is, iiuc, disabled. I turned on verbose logging fo cleanup, qmgr, and verify, to watch/see if I could effectively move the verify step after the preq & postq content filter steps. So far, haven't been able to effect any change. At least I know what to be looking at, if not for. Jason
