Joe Rhett wrote:
> > The main point of this is to actually get some virtual hosting within a
> > single mailstore. The use_ip_as_realm patch will provide most of the
> > changes needed to do either named or ip vhosts, primarily how
> > information (mailboxes, acls, message flags, etc) is sep
Date: Fri, 4 May 2001 15:03:24 -0700 (PDT)
From: Helmut Apfelholz <[EMAIL PROTECTED]>
Does anyone no if the partition with user directories
has to be mounted 'atime'. I would like to speed the
access a bit by mounting it with 'noatime' option, but
don't know if this wouldn't cau
Hi,
Does anyone no if the partition with user directories
has to be mounted 'atime'. I would like to speed the
access a bit by mounting it with 'noatime' option, but
don't know if this wouldn't cause any damage.
Anyone knows ?
thanks.
H.
__
Do Yo
On Fri, 4 May 2001, Joe Rhett wrote:
> If you have a different DNS name & IP address for each virtual domain,
> you'll need a different SSL certificate for each one or the browser will
> complain upon establishing a connection -- long before SASL issues are
Doh. I realized my mistake a minute af
> > > I have a suggestion on this subject. What about the possibility of
> > > binding a realm to a local address for cyrus (IP based vhost)? Yes,
> > > authentication and named vhosts via username and realm is ideal, but
> > > given that that information is usually not explicitly send by the
> >
> > The best way is to have the client log into a single hostname with a single
> > IP (and single matching certificate) but provide domain information during
> > the login.
>
> This is indeed a better idea, which already has been discussed. My
> opinion is that the server should have the option
On Fri, 4 May 2001, Joe Rhett wrote:
> > I have a suggestion on this subject. What about the possibility of
> > binding a realm to a local address for cyrus (IP based vhost)? Yes,
> > authentication and named vhosts via username and realm is ideal, but
> > given that that information is usually n
Joe Rhett wrote:
>
> It's not possible at that level, which is what I was saying.
>
> The best way is to have the client log into a single hostname with a single
> IP (and single matching certificate) but provide domain information during
> the login.
This is indeed a better idea, which already
Joe Rhett wrote:
>
> > I have a suggestion on this subject. What about the possibility of
> > binding a realm to a local address for cyrus (IP based vhost)? Yes,
> > authentication and named vhosts via username and realm is ideal, but
> > given that that information is usually not explicitly send
It's not possible at that level, which is what I was saying.
The best way is to have the client log into a single hostname with a single
IP (and single matching certificate) but provide domain information during
the login.
The second, non-scaleable approach is a different configuration per IP
ad
> I have a suggestion on this subject. What about the possibility of
> binding a realm to a local address for cyrus (IP based vhost)? Yes,
> authentication and named vhosts via username and realm is ideal, but
> given that that information is usually not explicitly send by the
> client, if the ima
Hello all,
I've gotten my Cyrus 2.0.13 installation up and running on a RH 6.2.3 box
thanks to the archives of this list but have one remaining hurdle.
Cyradm won't initialize and I get the following error message:
root@imap rolfe]# cyradm
Can't locate Cyrus/IMAP/Shell.pm in @INC (@INC contai
Dan Makovec wrote:
> While the IMSP support in Silkymail was cute, the fact that none of my other
> clients support it makes it a bit useless. When I can find a decent Windows
> based mail client that supports the same addressbook format as this, then I
> will make use of it. Until then, sadly,
Dan Makovec wrote:
>
> After taking a look at silkymail, and all the web clients listed last month,
> Atif's version of IMP seemed to be the only one that did what I want.
> Basically, because I make *extensive* use of Cyrus sieve, my mail gets put
> into various subfolders before the client conn
Hi,
I had this same error too. It occurs when you change your authentication
mechanism to Pam or LDAP (through the use of a patch) or to something
else. You need to create the sasldb file using the saslpasswd command.
Put a dummy account or something in the file. As long as that file
exists, y
15 matches
Mail list logo
