This sort of directory hash is very easy to implement in Cyrus; a
better directory hash than the one included wasn't chosen since we
wanted something simple that worked well enough for us.
Unfortunately, due to extreme laziness on my part, the directory hash
function used is used in multiple plac
>>> Have you checked the following files for proper configuration entries:
>>>
>>> 1) Cyrus.conf (on RH it is in /usr/lib/sasl).
>>
>> I don't believe Cyrus uses a .conf file in usr/lib/sasl.
>> It was my understanding that what would ordinarily
>> go into Cyrus.conf file in /usr/lib/sasl actuall
Where can I get my hands on sieve documentation? The only thing keeping me
from using imap 2.x is the inability to use procmail due to a broken
deliver. I am primarily using procmail to sort through my mail and direct
it into different folders. Can the same be accomplished with sieve? If so,
Moby wrote:
> So, no sieve and no way to have procmail deliver mail. Pretty much rules
> out the usual ways of mail filtering!
>
> --Moby
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Nick Snellock
> Sent: Tuesday, December 05, 2000 9:59 AM
> To
My fault for not painting the full picture. It can go in either/or. Value
in imapd.conf will override the value if Cyrus.conf.
--Moby
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael Fair
Sent: Tuesday, December 05, 2000 12:23 PM
To: [EMAIL PROT
So, no sieve and no way to have procmail deliver mail. Pretty much rules
out the usual ways of mail filtering!
--Moby
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Nick Snellock
Sent: Tuesday, December 05, 2000 9:59 AM
To: Cyrus Info Mailingliste
Subj
So, no sieve and no way to have procmail deliver mail. Pretty much rules
out the usual ways of mail filtering!
--Moby
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Nick Snellock
Sent: Tuesday, December 05, 2000 9:59 AM
To: Cyrus Info Mailingliste
Subj
> Have you checked the following files for proper configuration entries:
>
> 1) Cyrus.conf (on RH it is in /usr/lib/sasl).
I don't believe Cyrus uses a .conf file in usr/lib/sasl.
It was my understanding that what would ordinarily
go into Cyrus.conf file in /usr/lib/sasl actually
goes into /et
> Users are signing up for a PHP/MySQL portal that runs on our system, with
> the ability to set their own passwords. We also offer IMP-based e-mail
that
> uses Cyrus impad. I can cut and paste encrypted password from the
underlying
> MySQL database for the portal into /etc/shadow, but don't kno
AA15354
Hi,
We have a host here that has several ethernet interfaces configured.
We would like to run more then one instance of cyrus, each binding to a
different interface. The thinking behind this is, that we would like to split
the cyruses to more then one machine when the number of users gro
AA13795
On Friday 01 December 2000 22:07, Ken Murchison wrote:
> Krzysztof Sierota wrote:
> > Hello,
> >
> > I have read some documentation on the new 2.0.7 cyrus server, and I
> > really like the improvements. However, I am a bit concerned about the
> > lack of reconstruct tool that would be com
3a0$[EMAIL PROTECTED]> <001701c05e4d$fe63a5d0$0100a8c1@jeremy>
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator
="4D4F5353"
Content-Transfer-Encoding: 7bit
Jeremy Howard wrote:
> Scot W. Hetzel wrote:
> > From: "Michael Fair" <[EMAIL PROTECTED]>
> > > 4) Microso
On 12/4/00 7:14 PM, "unplug" <[EMAIL PROTECTED]> wrote:
> If I still continue to send 1MB email to user.abc, he can't receive the mail,
> right!! However, I can see the maillog and it shows me that the 1MB email is
> delivered without problem. Where does the 1MB email go?? Does it go to the
> q
I have to confess to a great deal of confusion regarding authentication
issues.
I am trying to get to a point were I can move Cyrus in to replace an
exchange system. I am getting tired of doing recovery of the exchange
mailstore when it bin-annually decides to self destruct.
Sieve seems to be broken in 2.0.7
Nick
Moby wrote:
> I have had problems running deliver and deliver-wrapper that come with cyrus
> imap 2.0.X. If you do not need to use these (if your MTA can directly talk
> lmtp and you are not using stuff like procmail) then everything is pretty
> stable :)
Visit the following URL:
http://www.openldap.org/faq/data/cache/52.html
This may give you some information to get started. Your requirements
drive the schema and the acls.
__
Seva
Martin Stockhammer wrote:
> Hello,
>
> I use cyrus imap 1.6.24 with OpenLDAP for authentication.
> Authentication
I have had problems running deliver and deliver-wrapper that come with cyrus
imap 2.0.X. If you do not need to use these (if your MTA can directly talk
lmtp and you are not using stuff like procmail) then everything is pretty
stable :)
--Moby
-Original Message-
From: [EMAIL PROTECTED]
Have you checked the following files for proper configuration entries:
1) Cyrus.conf (on RH it is in /usr/lib/sasl).
2) imapd.conf (on RH it is in /etc).
3) In case you are using pam, check imap (on RH in /etc/pam.d)
Also make sure your cyrus user account has read access to /etc/shadow.
--Mo
Hi,
> I use cyrus imap 1.6.24 with OpenLDAP for authentication.
> Authentication is made via PAM and the pam_ldap-module.
> Now I want to store the groups in LDAP too. What do I have to
> do for this?
Go to www.padl.com and get the migration tools. These will help you
generate group ldif files fr
Hello,
I use cyrus imap 1.6.24 with OpenLDAP for authentication.
Authentication is made via PAM and the pam_ldap-module.
Now I want to store the groups in LDAP too. What do I have to
do for this?
I have read that nss_ldap is used for this, but I don't know
how to configure it.
Thanks
Martin St
Hello,
how stable is the release of cyrus imap 2.0**?
The new features of 2.0 are very interesting and I
would upgrade to 2.0 if it's stable enough.
Thanks
Martin Stockhammer
--
Martin Stockhammer
Visual Analysis GmbH
http://www.visualanalysis.com
email: [EMAIL PROTECTED]
21 matches
Mail list logo