Luca Olivetti schrieb:
>
> Simon Matter wrote:
>
> > Most postfix RPM packages I have seen, including my own, let postfix
> > have it's own uid and gid (89) and group postdrop (90). In addition to
> > the own group they make postfix also a member of group mail.
>
> But redhat doesn't include po
Simon Matter wrote:
> Most postfix RPM packages I have seen, including my own, let postfix
> have it's own uid and gid (89) and group postdrop (90). In addition to
> the own group they make postfix also a member of group mail.
But redhat doesn't include postfix (last I checked it was available o
Luca Olivetti schrieb:
>
> [EMAIL PROTECTED] wrote:
>
> > See ftp://kalamazoolinux.org/pub/pdf/Cyrus.pdf
>
> BTW, page 28, postfix.
> The proposed configuration won't work if postfix isn't in group mail (it
> isn't by default under mandrake linux).
Most postfix RPM packages I have seen, includ
On Mon, 23 Sep 2002, Rob Siemborski wrote:
> On Mon, 23 Sep 2002, Luca Olivetti wrote:
>
> > what about
> > http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&msg=15004
>
> I'd need more information to discuss it, since SASL 2.1.2 didn't include
> an LDAP saslauthd module. Kn
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&msg=15004
>I'd need more information to discuss it, since SASL 2.1.2 didn't include
>an LDAP saslauthd module. Knowing how LDAP was compiled, and so on would
>help, but if it's not a current issue, I'm not going to worry about
Luca Olivetti wrote:
> Mr. Simix wrote:
>
>> Right, I'm using Cyrus-IMAPd->saslauthd->pam->[ldap|shadow|...].
>
>
> Does it work? How?
> I'm not using ldap, but a user of my packages has complained that he had
> problems with a similar setup. By searching the list it seems that the
> problem
On Mon, 23 Sep 2002, Luca Olivetti wrote:
> what about
> http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&msg=15004
I'd need more information to discuss it, since SASL 2.1.2 didn't include
an LDAP saslauthd module. Knowing how LDAP was compiled, and so on would
help, but if
Rob Siemborski wrote:
>>Yes, but what happens if openldap is compiled againts sasl v1?
>
>
> This shouldn't matter. saslauthd is a separate process from the
> application that is authenticating.
what about
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&msg=15004
> Note
Rob Siemborski wrote:
>>saslauthd won't care what OpenLDAP is linked against. saslauthd talks to some
>>mechanism like PAM.
>
>
> Saslauthd can also use LDAP directly, in which case it needs to link
> libldap and liblber.
Yes, but what happens if openldap is compiled againts sasl v1?
$ ldd /
On Mon, 23 Sep 2002, Luca Olivetti wrote:
> Yes, but what happens if openldap is compiled againts sasl v1?
This shouldn't matter. saslauthd is a separate process from the
application that is authenticating.
Note that your ldd output only indicates a dependency on libsasl and not
libsasl2.
> W
[EMAIL PROTECTED] wrote:
> See ftp://kalamazoolinux.org/pub/pdf/Cyrus.pdf
BTW, page 28, postfix.
The proposed configuration won't work if postfix isn't in group mail (it
isn't by default under mandrake linux).
Bye
--
Luca Olivetti
Wetron Automatización S.A. http://www.wetron.es/
Tel. +34 93 5
On Mon, 23 Sep 2002 [EMAIL PROTECTED] wrote:
> >I'm not using ldap, but a user of my packages has complained that he had
> >problems with a similar setup. By searching the list it seems that the
> >problem is that openldap is compiled aganinst sasl v1, at least under
> >mandrake. I looked at the
[EMAIL PROTECTED] wrote:
>>I'm not using ldap, but a user of my packages has complained that he had
>>problems with a similar setup. By searching the list it seems that the
>>problem is that openldap is compiled aganinst sasl v1, at least under
>>mandrake. I looked at the redhat packages for o
>>Right, I'm using Cyrus-IMAPd->saslauthd->pam->[ldap|shadow|...].
>Does it work?
Yes.
>How?
See ftp://kalamazoolinux.org/pub/pdf/Cyrus.pdf
>I'm not using ldap, but a user of my packages has complained that he had
>problems with a similar setup. By searching the list it seems that the
>pro
Mr. Simix wrote:
> Right, I'm using Cyrus-IMAPd->saslauthd->pam->[ldap|shadow|...].
Does it work? How?
I'm not using ldap, but a user of my packages has complained that he had
problems with a similar setup. By searching the list it seems that the
problem is that openldap is compiled aganinst
Henrique de Moraes Holschuh wrote:
>On Sun, 22 Sep 2002, Mathieu Arnold wrote:
>
>
>>--On dimanche 22 septembre 2002 12:27 -0400 Ken Murchison <[EMAIL PROTECTED]>
>>wrote:
>>
>>
>>
>>>
>>>
>>that is true, you can only give it a login and a *plain text* password,
>>then, pam checks for
Hi GOMBAS!
On Mon, 23 Sep 2002, GOMBAS Gabor wrote:
> On Sun, Sep 22, 2002 at 02:27:43PM -0300, Henrique de Moraes Holschuh wrote:
> > How does libpam-opie and openssh manage to do challenge-response auth
> > through the PAM layer, then?
>
> libpam-opie puts the challenge in the text of the pass
On Sun, Sep 22, 2002 at 02:27:43PM -0300, Henrique de Moraes Holschuh wrote:
> How does libpam-opie and openssh manage to do challenge-response auth
> through the PAM layer, then?
libpam-opie puts the challenge in the text of the password prompt.
Openssh has nothing to do with it, it only sees t
On Sun, 22 Sep 2002, Mathieu Arnold wrote:
> --On dimanche 22 septembre 2002 12:27 -0400 Ken Murchison <[EMAIL PROTECTED]>
> wrote:
>
> > Quoting Eric Estabrooks <[EMAIL PROTECTED]>:
> >
> >> It should be possible to write a pam module (or extend an existing one)
> >> to include other mechanism
On Sun, 22 Sep 2002, Mr. Simix wrote:
> Okay, but we can say whenever PAM is involved, then only plain can be
> used, right?
More generally, whenever saslauthd is used, only PLAIN or LOGIN can be
used, yes.
-Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siembors
On Sun, 22 Sep 2002, Tarjei Huse wrote:
> Hmm. If I can generalize here:
> -> If you use an auxprop module, then you may use non-plaintxt mechs. Currently
> only the MySQL one supports this and thus stores the same secrets as the
> saslpasswd 2 file but in a db.
Yes.
> -> There is an auxprop pl
--On dimanche 22 septembre 2002 12:27 -0400 Ken Murchison <[EMAIL PROTECTED]>
wrote:
> Quoting Eric Estabrooks <[EMAIL PROTECTED]>:
>
>> It should be possible to write a pam module (or extend an existing one)
>> to include other mechanisms beside plain, if like you said you had plain
>
> My
Ken Murchison wrote:
>Quoting Eric Estabrooks <[EMAIL PROTECTED]>:
>
>
>
>>
>>
>>>
>>>
>>It should be possible to write a pam module (or extend an existing one)
>>to include other mechanisms beside plain, if like you said you had plain
>>
>>
>
>My understanding of PAM is that yo
Hi,
>> If you do not use saslpasswd2, then Cyrus only uses plaintext methods for
> > authentication, right?
> No. You can use a MySQL backend as well to supply the secrets for
> non-plaintext methods. The OpenLDAP people also have an auxprop
> plugin that will get the secerts directly from thei
Quoting Eric Estabrooks <[EMAIL PROTECTED]>:
> Mathieu Arnold wrote:
>
> >--On dimanche 22 septembre 2002 15:45 +0200 "Mr. Simix"
> <[EMAIL PROTECTED]>
> >wrote:
> >
> >
> >
> >>Rob Siemborski wrote:
> >>
> >>
> >>>On Sun, 22 Sep 2002, Tarjei Huse wrote:
> >>>
> >>>
> >>>
> >>>
> >>>
--On dimanche 22 septembre 2002 10:11 -0500 Eric Estabrooks
<[EMAIL PROTECTED]> wrote:
> It should be possible to write a pam module (or extend an existing one)
> to include other mechanisms beside plain, if like you said you had plain
> text passwords available on the server side. Of course t
Mathieu Arnold wrote:
>--On dimanche 22 septembre 2002 15:45 +0200 "Mr. Simix" <[EMAIL PROTECTED]>
>wrote:
>
>
>
>>Rob Siemborski wrote:
>>
>>
>>>On Sun, 22 Sep 2002, Tarjei Huse wrote:
>>>
>>>
>>>
>>>
If you do not use saslpasswd2, then Cyrus only uses plaintext methods
for a
--On dimanche 22 septembre 2002 15:45 +0200 "Mr. Simix" <[EMAIL PROTECTED]>
wrote:
> Rob Siemborski wrote:
>> On Sun, 22 Sep 2002, Tarjei Huse wrote:
>>
>>
>>> If you do not use saslpasswd2, then Cyrus only uses plaintext methods
>>> for authentication, right?
>>
>>
>> No. You can use a My
Rob Siemborski wrote:
> On Sun, 22 Sep 2002, Tarjei Huse wrote:
>
>
>>If you do not use saslpasswd2, then Cyrus only uses plaintext methods for
>>authentication, right?
>
>
> No. You can use a MySQL backend as well to supply the secrets for
> non-plaintext methods. The OpenLDAP people also h
--On dimanche 22 septembre 2002 14:06 +0200 "Mr. Simix" <[EMAIL PROTECTED]>
wrote:
> Tarjei Huse wrote:
>> (I'm reading up on old mail here)
>> Quoting Simon Matter <[EMAIL PROTECTED]>:
>>
>>> Page 7:
>>> saslpasswd2 is not always needed. My cyrus user is in the LDAP tree and
>>> I've
>>
>>
On Sun, 22 Sep 2002, Tarjei Huse wrote:
> If you do not use saslpasswd2, then Cyrus only uses plaintext methods for
> authentication, right?
No. You can use a MySQL backend as well to supply the secrets for
non-plaintext methods. The OpenLDAP people also have an auxprop
plugin that will get th
Tarjei Huse wrote:
> (I'm reading up on old mail here)
> Quoting Simon Matter <[EMAIL PROTECTED]>:
>
>>Page 7:
>>saslpasswd2 is not always needed. My cyrus user is in the LDAP tree and I've
>
>
> If you do not use saslpasswd2, then Cyrus only uses plaintext methods for
> authentication, right?
On Tue, 2002-09-17 at 03:36, [EMAIL PROTECTED] wrote:
> Simon Matter wrote:
> >Page 20:
> >Would be nice to add a postfix section:
> >To use lmtp as mail transport, add this to /etc/postfix/main.cf
> >mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
> >and make sure lmtp is not chrooted (un
(I'm reading up on old mail here)
Quoting Simon Matter <[EMAIL PROTECTED]>:
> Page 7:
> saslpasswd2 is not always needed. My cyrus user is in the LDAP tree and I've
If you do not use saslpasswd2, then Cyrus only uses plaintext methods for
authentication, right?
Tarjei
On Thu, Sep 19, 2002 at 04:54:16PM -0400, [EMAIL PROTECTED] wrote:
> New version
>
> ftp://kalamazoolinux.org/pub/pdf/Cyrus.pdf
Great work on this. I take it you don't mind if people pass it along
to others? Anything you want referenced other than the credits given
in the PDF?
> I'd really like
edu/~pauls/
> -Original Message-
> From: Mr. Simix [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 19, 2002 3:49 PM
> To: Schmehl, Paul L
> Cc: Scott Russell; Luca Olivetti; [EMAIL PROTECTED]
> Subject: Re: Cyrus IMAP Presentation
>
>
> Schmehl, Pau
New version
ftp://kalamazoolinux.org/pub/pdf/Cyrus.pdf
The bulletin board information should be correct now, and I've added some
neccesary sendmail stuff.
I'd really like to have the names of some large sites and how many users and
shared folders they have. This is really important to the sui
IL PROTECTED])
> Department Coordinator
> The University of Texas at Dallas
> AVIEN Founding Member
> http://www.utdallas.edu/~pauls/
>
>
>
>>-Original Message-
>>From: Scott Russell [mailto:[EMAIL PROTECTED]]
>>Sent: Wednesday, September 18, 2002 1
IL PROTECTED])
Department Coordinator
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/~pauls/
> -Original Message-
> From: Scott Russell [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 18, 2002 10:02 AM
> To: Luca Olivetti
> Cc: [EMA
Hate to replay to my own post but I forgot
about per IP based virtdomain support in
2.0/2.1 series.
This is done by running multiple instances
of cyrus master, usually chrooted and bound
to specific IPs.
I don't know much about this kind of virtual
hosting with Cyrus but I know there are some
>>My m4 -
>>FEATURE(`preserve_local_plus_detail')
>>...
>>MAILER(cyrusv2)dnl
>>...
>>define(`confLOCAL_MAILER', `cyrusv2')
>>And it works. But I still can't get bulletin boarding to work. The docs
>>make it look like [EMAIL PROTECTED] should post the message
>>into my INBOX.Presentations folder,
On Wed, Sep 18, 2002 at 10:32:08AM -0700, Michael Fair wrote:
> > Having Cyrus setup it's lmtp socket under /var/spool/postfix (but not
> > /public or /private) is the right thing to do. I say this because
> > often postfix runs in a chroot env and won't access the lmtp socket if
> > it's outside
> Having Cyrus setup it's lmtp socket under /var/spool/postfix (but not
> /public or /private) is the right thing to do. I say this because
> often postfix runs in a chroot env and won't access the lmtp socket if
> it's outside of /var/spool/postfix
This isn't true in the slightest and making it
[EMAIL PROTECTED] wrote:
>
> I've created a presentation about Cyrus IMAPd that I will be showing to
> the local LUG in a couple of weeks. I'd appreciate it if some Cyrus
> masters
> would take a look at it and see if I've gotten anything wrong.
> ftp://kalamazoolinux.org/p
Date: Wed, 18 Sep 2002 11:23:11 -0400
From: [EMAIL PROTECTED]
[...]
OK, I did that and now sendmail is happily delivering via LMTP!
Thanks. Added a slide about setting up to use LMTP.
My m4 -
FEATURE(`preserve_local_plus_detail')
...
MAILER(cyrusv2)dnl
...
define(`c
I've created a presentation about Cyrus IMAPd that I will be showing to
the local LUG in a couple of weeks. I'd appreciate it if some Cyrus
masters
would take a look at it and see if I've gotten anything wrong.
ftp://kalamazoolinux.org/pub/pdf/Cyrus.pdf
>>>A few points:
>>>- S
On Wed, Sep 18, 2002 at 08:53:07AM +0200, Luca Olivetti wrote:
> Amos Gouaux wrote:
>
> >To quote <[EMAIL PROTECTED]>:
> >
> > The "lmtp" delivery agent should be listening on "private/lmtp", so it
> > will work, but...
>
> But since this directory is writable only by user 'postfix' cyrus
> (
Luca Olivetti wrote:
> Amos Gouaux wrote:
>
>> To quote <[EMAIL PROTECTED]>:
>>
>> The "lmtp" delivery agent should be listening on "private/lmtp", so it
>> will work, but...
>
>
> But since this directory is writable only by user 'postfix' cyrus
> (running as user cyrus) wouldn't be able
Amos Gouaux wrote:
> To quote <[EMAIL PROTECTED]>:
>
> The "lmtp" delivery agent should be listening on "private/lmtp", so it
> will work, but...
But since this directory is writable only by user 'postfix' cyrus
(running as user cyrus) wouldn't be able to create the socket there
>
> Thi
pretty much identical to what they are now.
Hope that helped.
-- Michael --
- Original Message -
From: "Amos Gouaux" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 17, 2002 9:13 PM
Subject: Re: Cyrus IMAP Presentation
> >>>>
> On Tue, 17 Sep 2002 21:56:07 -0500,
> Schmehl, Paul L <[EMAIL PROTECTED]> (spl) writes:
spl> This simply isn't true. At UTD we are using altnamespace *and*
spl> we allow our users to have a PEA (Personalized Email Address)
spl> which can include firstname.lastname@.
This is done by t
er 17, 2002 7:08 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Cyrus IMAP Presentation
>
>
> > Do "typical" installations use altnamespace or the hierarchical name
> space?
>
> One point I didn't see on the list about this so far
&g
> Do "typical" installations use altnamespace or the hierarchical name
space?
One point I didn't see on the list about this so far
in regards to "typical" installations and unix hierarchy
separator feature is that without it there is now way to
have a "." in the mailbox name which is important in
[EMAIL PROTECTED] wrote:
>
> >>I've created a presentation about Cyrus IMAPd that I will be showing to
> >>the local LUG in a couple of weeks. I'd appreciate it if some Cyrus masters
> >>would take a look at it and see if I've gotten anything wrong.
> >>ftp://kalamazoolinux.org/pub/pdf/Cyrus.p
> On 17 Sep 2002 13:17:06 -0400,
> Brian <[EMAIL PROTECTED]> (b) writes:
b> I knew someone would mention that book ;-) ... but it really doesn't
b> count. It was pretty much out of date by the time it came out and,
b> while it did cover Cyrus, it was pretty broad in scope.
Well, trut
>>I've created a presentation about Cyrus IMAPd that I will be showing to
>>the local LUG in a couple of weeks. I'd appreciate it if some Cyrus masters
>>would take a look at it and see if I've gotten anything wrong.
>>ftp://kalamazoolinux.org/pub/pdf/Cyrus.pdf
>A few points:
>- Slide 4: Just for
On Tue, 2002-09-17 at 12:40, Amos Gouaux wrote:
> b> I've often wondered why O'Reilly has never commissioned a book about
> b> Cyrus. With co-lo's getting cheaper and cheaper, I always recommend
> b> Cyrus whenever one of my sysadmin friends says they're going to do
> b> POP/IMAP, but it's alway
> On 17 Sep 2002 12:05:34 -0400,
> Brian <[EMAIL PROTECTED]> (b) writes:
b> I've often wondered why O'Reilly has never commissioned a book about
b> Cyrus. With co-lo's getting cheaper and cheaper, I always recommend
b> Cyrus whenever one of my sysadmin friends says they're going to do
b
> On Tue, 17 Sep 2002 16:52:28 +0200,
> Luca Olivetti <[EMAIL PROTECTED]> (lo) writes:
lo> I don't understand: this is a socket opened *by* cyrus, and postfix
lo> is instructed to talk lmtp to that unix socket.
lo> A local user could use the socket to inject mail to cyrus, but (s)he
lo> c
On Tue, 2002-09-17 at 11:47, [EMAIL PROTECTED] wrote:
> And, with no derision intended for the Cyrus team, the documentation
> is pretty sketchy about numerous points and has very few examples.
> A great deal of knowledge is assumed on behalf of the reader, knowledge it is
> nearly impossible
[EMAIL PROTECTED] wrote:
>
> I've created a presentation about Cyrus IMAPd that I will be showing to the
> local LUG in a couple of weeks. I'd appreciate it if some Cyrus masters would
> take a look at it and see if I've gotten anything wrong.
>
> ftp://kalamazoolinux.org/pub/pdf/Cyrus.pdf
A
On Tue, Sep 17, 2002 at 09:31:02AM -0400, Ken Murchison wrote:
> > >(Slide 8)
> > >The mailbox hierarchy does not have to work the way you describe (see also
> > >altnamespace and unixhierarchysep)
> >
> > Noted, but I don't know if I want to go into that.
> >
> > Do "typical" installations use
>>This is precisely the reason that a sysadmin considering Cyrus as part of a
>>mail distribution system should build from source. The economics of
>>implementing a Cyrus based mail server system are very powerful when
>>considered against commercial systems such as Microsoft, Notes, and
>>others
On Tue, 2002-09-17 at 10:41, Arley Carter wrote:
> This is precisely the reason that a sysadmin considering Cyrus as part of a
> mail distribution system should build from source. The economics of
> implementing a Cyrus based mail server system are very powerful when
> considered against commerc
Amos Gouaux wrote:
> lo> edit /etc/cyrus.conf and replace the existing lmtpunix line with
>
> lo> lmtpunix cmd="lmtpd" listen="/var/spool/postfix/public/lmtp" prefork=1
>
> While this will work, as has been discussed on postfix-users, those
> sockets really are not for third party software such
At 09:20 17.09.2002 -0500, Schmehl, Paul L wrote:
>What is noatime? "# man -k noatime" shows nothing on RH 7.2.
>
"man mount" is the right place to look :-)
Regards
--
Andreas Hödle
Kühn & Weyh Software GmbH
WWW.KWSOFT.DE
This is an impressive set of slides you put together. I believe should
should rework the section about "get the packaged version because
configuring from source is very confusing and has subtle semantics that
aren't immediately apparent. (paraphrasing this portion of your slide
presentation)
Th
On Tue, 17 Sep 2002, Schmehl, Paul L wrote:
> What is noatime? "# man -k noatime" shows nothing on RH 7.2.
It's a filesystem mount directive that tells the filesystem to not record
access times, which reduces the number of writes to disk that need to
happen (if you don't care about access times
> On Tue, 17 Sep 2002 08:55:53 +0200,
> Luca Olivetti <[EMAIL PROTECTED]> (lo) writes:
lo> edit /etc/cyrus.conf and replace the existing lmtpunix line with
lo> lmtpunix cmd="lmtpd" listen="/var/spool/postfix/public/lmtp" prefork=1
While this will work, as has been discussed on postfix-u
TECTED]]
> Sent: Tuesday, September 17, 2002 9:08 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Cyrus IMAP Presentation
>
>
> On Tue, 17 Sep 2002 [EMAIL PROTECTED] wrote:
>
> > On another performance note; is it safe to do noatime on the mail
>>>(Slide 16)
>>>- "-n 5" is probably low for a reasonably high traffic site.
>>I've got about 200 users, if there should be more threads will
>>authentication fail or just be really slow?
>Authentication will start to fail (atleast when using unix domain
>sockets), because the saslauthd listen q
On Tue, 17 Sep 2002 [EMAIL PROTECTED] wrote:
> On another performance note; is it safe to do noatime on the mail filesystem
> and/or configuration filesystem? Or does cyrus make use of these attributes?
noatime is safe (and even encouraged!) ;)
-Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
On Mon, 16 Sep 2002 [EMAIL PROTECTED] wrote:
> >(Slide 11)
> >Technically, you can have administrative accounts other than
> >"cyrus". And you can change the access right required to delete folders
> >with the deleteright flag.
>
> True, but again a little deeper than I want to go. It has to fi
>>>(Slide 8)
>>>The mailbox hierarchy does not have to work the way you describe (see
>>>also altnamespace and unixhierarchysep)
>>Noted, but I don't know if I want to go into that.
>>Do "typical" installations use altnamespace or the hierarchical name
>>space?
>>If I change it after the server i
[EMAIL PROTECTED] wrote:
>
> >>I've created a presentation about Cyrus IMAPd that I will be showing to
> >>the
> >>local LUG in a couple of weeks. I'd appreciate it if some Cyrus masters
> >>would> take a look at it and see if I've gotten anything wrong.
> >Some of these may be a bit picky, bu
cassandre wrote:
> I quoteWerner Reisberger <[EMAIL PROTECTED]>
>
>
>
> There is more than one way to run cyrus with procmail. I am using it since
> years with postfix. That's my entry in master.cf
Sure, and there's more than one way use cyrus+postfix, with or without
procmail, I just r
Le Mardi 17 Septembre 2002 08:55, vous avez écrit :
> [EMAIL PROTECTED] wrote:
> >>I beleive there are Debian Packages, put together by Henrique de Moraes
> >>Holschuh <[EMAIL PROTECTED]>.
> >
> > Now mentioned.
>
> I also have rpm packages for mandrake (8.2 at the moment) at
> http://perso.wanado
I've just checked your new version of Cyrus.pdf:
Page 7:
saslpasswd2 is not always needed. My cyrus user is in the LDAP tree and I've
never used any saslpasswd* command on any of my boxes.
Page 23:
Postfix consists of one master process and many child processes. The line in
master.cf ensures t
[EMAIL PROTECTED] wrote:
>>I beleive there are Debian Packages, put together by Henrique de Moraes
>>Holschuh <[EMAIL PROTECTED]>.
>
>
> Now mentioned.
I also have rpm packages for mandrake (8.2 at the moment) at
http://perso.wanadoo.es/olivetti/cyrus/
In that package (in the README.RPM) there
79 matches
Mail list logo
