On Tue, May 1, 2012 at 12:53 AM, David Nicol wrote:
>
> On 04/28/2012 03:41 PM, Robert Spier wrote:
>
>> I'm working on a "Qpsmtpd Big Picture" document that contains a flowchart
> >> of a sample connection, a catalog of all the plugins, what each plugin
> >> does/sets/changes, and what informati
On Apr 30, 2012, at 11:38 PM, Robert Spier wrote:
> On Mon, Apr 30, 2012 at 1:56 PM, Matt Simerson wrote:
>
> On Apr 29, 2012, at 11:45 PM, Michael Papet wrote:
>
> >> As it stands, there's often no way to answer questions like, 'how much of
> >> my ham will fail this test?' or 'will I lose va
On Mon, Apr 30, 2012 at 1:56 PM, Matt Simerson wrote:
>
> On Apr 29, 2012, at 11:45 PM, Michael Papet wrote:
>
> >> As it stands,
> >> there's often no way to answer questions like, 'how much of
> >> my ham will fail this test?' or 'will I lose valid mail
> >> using plugin X?' It's completely ne
On 04/28/2012 03:41 PM, Robert Spier wrote:
> log a reasonable amount, especially for LOGINFO. I know, I know,
> reasonable is hard to pin down, but a little bit of guidance could go a
> long ways here:
>
>DEBUG -> fire hose, spray away logging anything and everything.
>INFO
On Apr 29, 2012, at 11:45 PM, Michael Papet wrote:
>> As it stands,
>> there's often no way to answer questions like, 'how much of
>> my ham will fail this test?' or 'will I lose valid mail
>> using plugin X?' It's completely nebulous.
>
> When I need this, I use logging. I flip qpsmtpd into
On Saturday 28. April 2012 13.41.20 Robert Spier wrote:
> > > Maybe the time has come to "do a release" (0.9?) and then open
> > > things up for major cleanups/changes.
>
> This might actually be 0.85, but that's irrelevant.
As someone who prefers to run his production systems with as few deviati
> As it stands,
> there's often no way to answer questions like, 'how much of
> my ham will fail this test?' or 'will I lose valid mail
> using plugin X?' It's completely nebulous.
When I need this, I use logging. I flip qpsmtpd into info mode with a few
extra logging stanzas. While I see th
On Sat, Apr 28, 2012 at 7:54 PM, Ask Bjørn Hansen wrote:
> On Apr 28, 2012, at 13:41, Robert Spier wrote:
>
> > One thing that would help is if you could split your changes into
> multiple
> > pull requests -- if we're going to try using github as our mechanism,
> every
> > pull request should be
On Apr 28, 2012, at 13:41, Robert Spier wrote:
> One thing that would help is if you could split your changes into multiple
> pull requests -- if we're going to try using github as our mechanism, every
> pull request should be for one "feature". There's a lot of your changes
> pending right now
> I'm all in favor.
>
> I'm doing more work on plugins right now and have a bunch more changes in the
> pipes. Most of the changes revolve around several practices which I think all
> plugins should adhere to:
>
> One thing that would help is if you could split your changes into multiple
> pu
>
>
> > Maybe the time has come to "do a release" (0.9?) and then open things up
> > for major cleanups/changes.
>
This might actually be 0.85, but that's irrelevant.
> >
> > -R
>
> I'm all in favor.
>
> I'm doing more work on plugins right now and have a bunch more changes in
> the pipes. Most
11 matches
Mail list logo
