On Wed, Jul 17, 2002 at 07:11:03PM -0400, Sam Varshavchik wrote:
Ben Rosengart writes:
On Wed, Jul 17, 2002 at 05:55:13PM -0400, Sam Varshavchik wrote:
Ben Rosengart writes:
Simple: we generate a userdb on host A, in /export/foo. We read
it on host B, in /foo. Please do not suggest
On Thu, Jul 18, 2002 at 09:43:13AM -0700, Jesse Keating wrote:
On Thu, 18 Jul 2002 12:32:14 -0400
Ben Rosengart [EMAIL PROTECTED] wrote:
#
#If I build courier to use /foo/userdb*, and have a symlink on host
#A from /foo to /export/foo, then to build the database for host C,
#I have to
On Thu, 18 Jul 2002 13:57:20 -0400
Ben Rosengart [EMAIL PROTECTED] wrote:
#
#No, I want to maintain multiple userdbs across multiple servers.
#
#(I also want to maintain the same userdb across multiple servers, but
# I can do that without patching makeuserdb, as you point out, so it's
# not
Ben Rosengart writes:
On Thu, Jul 18, 2002 at 09:51:15AM -0400, Sam Varshavchik wrote:
On Thu, 18 Jul 2002, Ben Rosengart wrote:
I need to manage it from host A. Now I either have to maintain
separate builds of courier-imap, or delete and recreate the symlink
every time either
On Thu, Jul 18, 2002 at 11:07:06AM -0700, Jesse Keating wrote:
A) when replying please use 'l' to reply, instead of reply-all. Your client
(mutt) is smart enough to handle list email, so l replies to the list, and I
don't get a second copy of your reply in my inbox.
What do you have this
On Thu, Jul 18, 2002 at 02:30:24PM -0400, Sam Varshavchik wrote:
Why don't you simply build Courier using --sysconfdir=/etc/courier and
--with-userdb=/etc/courier/userdb, and install a soft link on each host,
/etc/courier, that points to the right configuration directory for that
host
At 03:15 PM 7/18/02 -0400, you wrote:
On Thu, Jul 18, 2002 at 11:07:06AM -0700, Jesse Keating wrote:
B) What is your problem with the multiple userdbs across multiple
servers? One
DB per server? I'm lost as to what your problem is.
It is impossible to build more than one userdb on the
On Thu, Jul 18, 2002 at 03:34:03PM -0400, Ben Rosengart wrote:
The problem with running makeuserdb on [production hosts instead
of a management host] is that it costs me an ssh every time I change
a database on [the management host].
It also means that if I have N hosts and N/4 different
If you're only running 'makeuserdb' on host A, then there's not much of
a problem with the current system. You can symlink userdb/whatever to
the files you need, and run 'makeuserdb' on host A. Hosts B and C only
need to read userdb.dat, so there shouldn't be a need for external
files.
If you
On Thu, Jul 18, 2002 at 01:32:43PM -0700, Gordon Messmer wrote:
If you're only running 'makeuserdb' on host A, then there's not much of
a problem with the current system. You can symlink userdb/whatever to
the files you need, and run 'makeuserdb' on host A. Hosts B and C only
need to read
Ben Rosengart wrote:
On Thu, Jul 18, 2002 at 11:07:06AM -0700, Jesse Keating wrote:
A) when replying please use 'l' to reply, instead of reply-all. Your client
(mutt) is smart enough to handle list email, so l replies to the list, and I
don't get a second copy of your reply in my inbox.
On Fri, Jul 19, 2002 at 08:39:29AM +1200, Juha Saarinen wrote:
Ben Rosengart wrote:
On Thu, Jul 18, 2002 at 11:07:06AM -0700, Jesse Keating wrote:
A) when replying please use 'l' to reply, instead of reply-all. Your
client
(mutt) is smart enough to handle list email, so l replies to the
: Gordon Messmer [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, July 18, 2002 4:33 PM
To: [EMAIL PROTECTED]
Subject: Re: [courier-users] Re: giving makeuserdb a little
flexibility
If you're only running 'makeuserdb' on host A, then there's not much of
a problem with the current system. You
Ben Rosengart writes:
On Thu, Jul 18, 2002 at 02:30:24PM -0400, Sam Varshavchik wrote:
Why don't you simply build Courier using --sysconfdir=/etc/courier and
--with-userdb=/etc/courier/userdb, and install a soft link on each host,
/etc/courier, that points to the right configuration
On Fri, 19 Jul 2002 08:39:29 +1200
Juha Saarinen [EMAIL PROTECTED] wrote:
#
#Jesse probably meant the 'reply to (g)roup' key.
Nope, I meant the L key, only lowercase. It means reply-list in
Mutt. Most _smart_ clients handle mailing lists the way that they
should, when the list is adhering to
On Thu, Jul 18, 2002 at 01:53:30PM -0700, Jesse Keating wrote:
Nope, I meant the L key, only lowercase. It means reply-list in
Mutt. Most _smart_ clients handle mailing lists the way that they
should, when the list is adhering to RFC's, and not munging the
reply-to header.
Hmmm... 'L'
On Thu, Jul 18, 2002 at 05:06:35PM -0400, Bowie Bailey wrote:
Without changing makeuserdb, you're not going to be able to keep your
current setup without moving some files around every time you rebuild
userdb.
That is correct.
cp -f /export/B/userdb /courier/etc/userdb
On Thu, Jul 18, 2002 at 05:03:26PM -0400, Sam Varshavchik wrote:
That's fine. A small change of plans: you're not going to run makeuserdb
by hand. You'll run a shell script that creates a soft link from
/etc/courier to /export/B before running makeuserdb once, then creates a
soft link
On Thu, Jul 18, 2002 at 05:03:26PM -0400, Sam Varshavchik wrote:
That's fine. A small change of plans: you're not going to run makeuserdb
by hand. You'll run a shell script that creates a soft link from
/etc/courier to /export/B before running makeuserdb once, then creates a
soft link
Bowie Bailey writes:
[...]
cp -f /export/B/userdb /courier/etc/userdb
makeuserdb
cp -f /courier/etc/userdb.dat /export/B/userdb.dat
Since we're at it, would Samone confirm or deny that
it is correct to use cp on userdb files? (I heard that
some implementation may result in
On Tue, Jul 16, 2002 at 05:04:56PM -0400, Sam Varshavchik wrote:
Ben Rosengart writes:
The destination directory can currently be set at compile time.
I am proposing making this configurable at run-time too. What is
the down-side? Who could possibly be harmed by making the software
On Wed, 2002-07-17 at 13:16, Ben Rosengart wrote:
Simple: we generate a userdb on host A, in /export/foo. We read
it on host B, in /foo. Please do not suggest that we maintain two
builds of courier-imap. I don't think you would appreciate it if
someone treated you as if your time had no
On Wed, Jul 17, 2002 at 05:55:13PM -0400, Sam Varshavchik wrote:
Ben Rosengart writes:
Simple: we generate a userdb on host A, in /export/foo. We read
it on host B, in /foo. Please do not suggest that we maintain two
builds of courier-imap. I don't think you would appreciate it if
Ben Rosengart writes:
On Fri, Jul 05, 2002 at 11:59:49PM -0400, Sam Varshavchik wrote:
On Fri, Jul 05, 2002 at 11:51:01PM -0400, Ben Rosengart wrote:
We don't build the userdb on the same host where we use it.
You have a site-specific custom configuration.
The destination directory
24 matches
Mail list logo
