On Tue, Jul 14, 2015 at 09:19:02PM -0700, E.B. wrote:
> > However, all the requests from a single smtpd(8) service will go
> > to the same policy service instance. So in memory caching can be
> > used to construct per-transaction state (if, for example, the policy
> > service fires for each recip
> However, all the requests from a single smtpd(8) service will go
> to the same policy service instance. So in memory caching can be
> used to construct per-transaction state (if, for example, the policy
> service fires for each recipient and also at data and/or end of
> data).
That's guaranteed
On Tue, Jul 14, 2015 at 06:04:37PM -0700, E.B. wrote:
> Beginner question - I want to confirm that policy service running
> under postfix spawn could have multiple instances running (if
> there are multiple smptd processes) and so they should never
> cache any important user data in local memory b
Beginner question - I want to confirm that policy service running
under postfix spawn could have multiple instances running (if
there are multiple smptd processes) and so they should never
cache any important user data in local memory because they
would be out of sync with other instances of the sa
On Tue, Jul 14, 2015 at 07:06:39PM -0500, John Gateley wrote:
> I can't find any steps for telling postfix to build with SASL support
> enabled in the docs.
http://www.postfix.org/SASL_README.html#postfix_build
--
Viktor.
On 7/14/15 7:06 PM, John Gateley wrote:
I'm just starting to work on SASL support, and tried the postconf -A
and -a commands
to make sure SASL support was enabled at build time. It wasn't, both
commands return
nothing (and no error code).
Nevermind. Found it. In a place in the documentation
I'm just starting to work on SASL support, and tried the postconf -A and
-a commands
to make sure SASL support was enabled at build time. It wasn't, both
commands return
nothing (and no error code).
I can't find any steps for telling postfix to build with SASL support
enabled in the docs.
Is
