Matt Sergeant wrote:
> Yeah I like it. I hate to be a pain in the ass but I'd love to see you
> add something to t/qpsmtpd-address.t too :-)
Slavedriver! :0
I'll see what I can do this AM. For everyone's benefit, I'll even add some POD
to Qpsmtpd::Address so all can share in the wealth of new f
Bob Dodds wrote:
Yes, I need hand-holding. I see the point of sorting
recipients into per domain lists but I need examples
to learn how to implement it.
my @sorted_recipients = sort @{$self->recipients};
It doesn't get much easier than that. With an overloaded object, as
long as one of the c
Dear John,
I am strucked at the finding Auth user from
a plugin, if i can know auth user from a plugin then i
will write the other code.
pls help me in this regard, i want this info in a
plugin.
Anil
__
Enjoy this Diw
I just committed some preliminary POD describing the available methods
in Qpsmtpd::Address. I also threw in a simple test of the overloaded
comparison method.
I assigned the copyright to Peter, since he started it, but I wonder if
we want/need to get better about being consistent. Should we
[EMAIL PROTECTED] wrote:
First, I'd really hate to get the latest version installed and the
server into production, and then find out that the new version of qpsmtpd
got released an hour later. Seems that I've been hearing that the new
version will be released "any day now" for several mo
On 2 Nov 2005, at 13:52, John Peacock wrote:
I just committed some preliminary POD describing the available methods
in Qpsmtpd::Address. I also threw in a simple test of the overloaded
comparison method.
Thanks.
I assigned the copyright to Peter, since he started it, but I wonder
if we wan
On Wed, 2 Nov 2005, John Peacock wrote:
> > When should we expect the new version?
>
> When it's done?
"Quack!" ;-)
Just trying to get an idea of what's going on and what, if
anything, is being waited for. Explanation appreciated.
> > I have almost 20 plugins that are near
[EMAIL PROTECTED] wrote:
8) Remember to sync your mirror once in the while to get the new shiny
things I have added...
Actually, this is mostly why I want to stick with a stable release
- I don't know how all these shiny things may affect, or be affected by,
the customized code I have.
John Peacock wrote:
> [...]
FWIW, I've been running branches/0.31 for months now, with hardly any
lost mail [that wasn't my own damn fault]. ;-)
> [...]
Umm - if (hardly any != no), I'm concerned.
Putting aside things which are of your own doing, do you know of failure
cases in the 0.31 bran
Gordon Rowell wrote:
> Umm - if (hardly any != no), I'm concerned.
No, it _was_ completely my fault. It was the in-memory caching feature and it
took me ~10 minutes to realize I'd used close() instead of flush() on the
filehandle. I didn't see it in my testing because I was using files that were
Anilkumar wrote:
Dear John,
I am strucked at the finding Auth user from
a plugin, if i can know auth user from a plugin then i
will write the other code.
pls help me in this regard, i want this info in a
plugin.
Anil
John Peacock has put auth_user into branches/0.31, if
you have that ve
Dear John,
Thanks again, i have sucessfully written a plugin.
i am giving the code for my plugin. I have given
plugin name as "check_valid_auth", please check the
plugin at your end , and if find suitable pls publish
it in Version 0.31 of qpsmtpd as plugin.
also suggest me some improvement in i
12 matches
Mail list logo
