You have lmtpproxyd set up to query the murder master server for
each message that comes in.
You're options are to
1. Have lmtpproxyd query the local server for each incoming message.
This decreases load on the murder master. You do this by creating a
config file for lmtpproxyd and setting murder
Quoting Greg Boug <[EMAIL PROTECTED]>:
> Hi guys,
>
> I'm looking to implement a murder of imap daemons, but not all of
> them are
> going to be heavily loaded. I'm attempting to set the system up
> using
> multiple servers acting as both a front and back end. Ie. they
> are both
> running proxyd
Quoting Michael Leupold <[EMAIL PROTECTED]>:
> Am Donnerstag, 18. Mai 2006 21:26 schrieb Andrew Morgan:
> > On Thu, 18 May 2006, Brenden Conte wrote:
> > > True, and i perhaps used a bad example - this occurs anytime
> i try to
> > > connect to the backend, not just on CREATE. for example, i
> ca
lumbia,dc=edu" scope=2 deref=0
filter="(uid=phr2101)"
conn=1 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text=
conn=1 op=2 SRCH base="ou=group,dc=cc,dc=columbia,dc=edu" scope=2
deref=0 filter="(memberUid=phr2101)"
conn=1 op=2 SEARCH RESULT tag=101 err=0 nent
Glad I could help.
The -t "" option will cause imtest to do starttls.
Once the connection is secure the server will allow the PLAIN mech
to be used.
-Patrick
Quoting "John C. Amodeo" <[EMAIL PROTECTED]>:
> Patrick,
>
> That worked. Before, I was never using the -t "" option, so I
> assume we
