I'm trying to measure SMTP performance.
I have unwired most processors in the config.xml, but
the spooling still seems takes place. I'd love to
just send all the messages straight to /dev/null.
I'll also try under a more competent file system
(ext2fs instead of ntfs) as well, but getting rid of
Hello,
Is there an easy way to avoid all file i/o in message
processing (for raw performance measurement)?
Thanks,
Gabor
=
Gabor Kincses
Running FreeBSD 4.7-RELEASE and Mandrake Linux 8.1
__
Do you Yahoo!?
Yahoo! Mail - You care a
See
http://svn.apache.org/repos/asf/james/server/branches/branch_2_1_fcs/src/jav
a/org/apache/james/transport/mailets/AbstractVirtualUserTable.java for a
correct way to modify the recipient collection.
--- Noel
-
To unsu
> The code uses the ComponentManager to lookup the UsersStore.
> I'm running into the problem where ComponentManager is deprecated.
> Is there a workaround I can use to get at the UsersRepository?
Use the deprecated code for now until we remove it entirely.
--- Noel
Alright. It appears I'm smacking to myself today but if there's anyone out
there actually listening on this list I could definitely use your help. I'm
almost there with my first mailet but for some reason I'm running into a snag.
What I want to do is replace the recipients of the original ema
So, I found an old thread that discusses how to obtain the UsersRepository
using the Avalon framework:
http://tinyurl.com/4v8r3
The code uses the ComponentManager to lookup the UsersStore. I attempted to
use this same code and I'm running into the problem where ComponentManager is
deprecated.
Hi there,
I've got my mailet deploying correctly but I have a question that I can't seem
to answer. Is there a way to get a handle on the users repository from inside
a Mailet that extends GenericMailet? Specifically, I'd like to get the
forwardDestination of a specific user from within a Mai
> I'd have to look, but no one would unless we tell them. :-)
And that would be the fault of the person maintaining the website I
suppose. i.e. Me!
;-)
d.
***
The information in this e-mail is confidential and for use by