Okay patches submitted.
For for the time delay but I had a bit of hard drive scare last night
after I finished the code but before I could spin the patch.
Any input, suggestions and or scorn is welcome :)
- J
On Tue, 2009-09-08 at 21:22 -0700, Jason Mills wrote:
Working on it right now :)
Patches submitted where?
-Jared
On 09/09/2009 04:43 PM, Jason Mills wrote:
Okay patches submitted.
For for the time delay but I had a bit of hard drive scare last night
after I finished the code but before I could spin the patch.
Any input, suggestions and or scorn is welcome :)
- J
On Tue,
From: Jason Mills jmmi...@cpan.org
Signed-off-by: Jason Mills jmmi...@cpan.org
---
lib/Qpsmtpd.pm| 35 +--
lib/Qpsmtpd/Plugin.pm |1 +
2 files changed, 26 insertions(+), 10 deletions(-)
diff --git a/lib/Qpsmtpd.pm b/lib/Qpsmtpd.pm
index
From: Jason Mills jmmi...@cpan.org
Signed-off-by: Jason Mills jmmi...@cpan.org
---
config.sample/plugins |3 +++
plugins/reverse_config_cachekey| 10 ++
t/plugin_tests/reverse_config_cachekey | 18 ++
3 files changed, 31 insertions(+), 0
Well I guess git send-email omitted my commit log in the sent patches.
So I'll just cover it real quick here:
Patch 1 of 2 adds a new hook currently named 'config-get-cachekey'.
This hook allows plugin authors to mutate or build logic around the key
used when referencing Qpsmtpd.pm's
Hi all, been monitoring the mailing for a bit but this would be my first
time asking a question.
Recently the boss-man tasked me with bringing the per_user_config
(originally authored by Gavin Carr) in line with the latest version of
Qpsmtpd. So far I've got as far as retooling the plugin into a
On Sep 8, 2009, at 21:05, Jason Mills wrote:
So to the point of the question: Would anyone mind if I patched the
configuration stuff within Qpsmtpd to allow configuration minded
plugins
to alter/hook/stack into how Qpsmtpd discovers and utilizes cached
configuration values?
Show us a
Working on it right now :)
On Tue, 2009-09-08 at 21:17 -0700, Ask Bjørn Hansen wrote:
On Sep 8, 2009, at 21:05, Jason Mills wrote:
So to the point of the question: Would anyone mind if I patched the
configuration stuff within Qpsmtpd to allow configuration minded
plugins
to
