exit 75 on cyrus startup
Hello All, My new cyrus install with postfix exits with exit 75 error , what does that mean? and how do I sort that out ? Imran. --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
How to debug cyrus install
Hello All, I have installed Cyrus and all the required servers like mysql , postfix etc using the documentation by Luc de Louw at http://www.delouw.ch/linux/Postfix-Cyrus-Web-cyradm-HOWTO/html/t1.html Sorted out all issues and now although on starting the cyrus server I do not get any errors, but still the cyrus server does not start. Can anyone please help me with this, how to debug this issue and sort this out.mysql , saslauthd with pam and postfix are running fine. Thanks a lot. Imran. --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
RE: why is pam not supported by saslauthd
> when I start Cyrus on my machine after a complete install with all > dependencies I get this error > > [EMAIL PROTECTED] config]# /etc/rc.d/init.d/cyrus start > saslauthd[31190] :set_auth_mech : unknown authentication mechanism: pam > > and on checking saslauthd I see that pam is not available > > saslauthd 2.1.21 > authentication mechanisms: getpwent rimap shadow > > How do I enable pam for saslauthd so that it works for me. > > Thanks a lot in advance. > > Imran Did you use "--with-pam=/path/to/pam" when you ran configure? Thanks, Michael King Systems Administrator Web International, Inc. www.webinternational.net --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Using Cyrus-imapd with Sieve (reject works, vacation does not)
Philip Edelbrock wrote:
I'm about to deploy a new mail server using Cyrus-imapd and Sieve
(RHE-ES 4). My last step is to make sure I can have automated vacation
messages. But, I can't get a test script to work. Rejects work fine,
but vacation does not.
This machine has no user accounts matching the email accounts (an
advantage to using Cyrus-imapd, I think). Does Sieve's vacation
functionality require user home directories to store a DB? (just a guess).
Here's my test script:
require "reject";
require "fileinto";
require "vacation";
require "envelope";
if header :contains "Subject" "test" {
vacation :days 7 "vactest!";
}
Replacing the vacation line with a reject line works.
Thanks!
Phil
Ack! I work on this for days, and finally make some headway just /after/
emailing the list. *sigh*
Anyways, populating the ":addresses" parameter makes it work. I was
hoping to have a generic script that I could use for any user, but at
least I've got something working now.
Phil
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Using Cyrus-imapd with Sieve (reject works, vacation does not)
I'm about to deploy a new mail server using Cyrus-imapd and Sieve
(RHE-ES 4). My last step is to make sure I can have automated vacation
messages. But, I can't get a test script to work. Rejects work fine,
but vacation does not.
This machine has no user accounts matching the email accounts (an
advantage to using Cyrus-imapd, I think). Does Sieve's vacation
functionality require user home directories to store a DB? (just a guess).
Here's my test script:
require "reject";
require "fileinto";
require "vacation";
require "envelope";
if header :contains "Subject" "test" {
vacation :days 7 "vactest!";
}
Replacing the vacation line with a reject line works.
Thanks!
Phil
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
why is pam not supported by saslauthd
when I start Cyrus on my machine after a complete install with all dependencies I get this error [EMAIL PROTECTED] config]# /etc/rc.d/init.d/cyrus start saslauthd[31190] :set_auth_mech : unknown authentication mechanism: pam and on checking saslauthd I see that pam is not available saslauthd 2.1.21 authentication mechanisms: getpwent rimap shadow How do I enable pam for saslauthd so that it works for me. Thanks a lot in advance. Imran --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Saslauthd with ldaps
On Fri, Jun 03, 2005 at 02:35:52PM +0200, Paul van der Vlis wrote: > > ldap_servers: ldaps://firewall.domain.nl/ > ldap_auth_method: fastbind > ldap_tls_cacert_file: /path/to/rootcert.pem > ldap_filter: cn=%u,o=wlg > > > The rootcert.pem is the root-certificate of the Novell server. > > A problem is: there are 2 Novell servers what are together the > e-directory, can we use 2 root-certificates? you can, but the point of a root server is most of the time to have only one CA which then signs the certificates for the servers. Unless the certificates of your novell servers are self-signed. --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: EMBARRASSING TO THE LIST: Re: *WARNING* Your EmailAccount Will Be Closed
On Wed, 2005-06-01 at 18:51 +0200, Ulf Rasch wrote: > > Marco Colombo wrote: > [snip] > > Interesting theories. But they seem to backfire on you, since, according > > to Mr. Jeffrey T Eaton <[EMAIL PROTECTED]> this list _is_ closed: > > "The list is not now, nor ever has been, open-posting. Posting is > > restricted to subscribers, or to those users local to cmu.edu" > > > > Then it must be one of those lists that let you configure your sending > > address, which is good. I must have done that at subscription time, and > > later forgot about it. > > > > Anyway it doesn't make much a difference, as you can see. Open or close > > is just a policy. If you think of it as an anti spam measure, it doesn't > > work. Sometimes, even advanced measures fail. > > > > Anyway, given that the list is restricted, there's no point in > > discussing... > > > > .TM. > > Well, if this list is closed then maybe the subscriber with the address: > > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > could be dropped from the list. If you don't like their policy, please bring the issue with the list management. You know, they can be easily reached at owner-info- [EMAIL PROTECTED] as per the Sender: header. Addressing the list (or me) on this matter is pointless, since we - the other subscribers and me - are not more capable of changing list policies than you are. Your message was just received by thousands (?) people who are not able to fulfill your request, no matter what they think about it. .TM. -- / / / / / / Marco Colombo ___/ ___ / / Technical Manager / / / ESI s.r.l. _/ _/ _/ [EMAIL PROTECTED] --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Saslauthd with ldaps
Igor Brezac schreef: > > On Wed, 1 Jun 2005, Paul van der Vlis wrote: > >> Hello, >> >> I want to authentifate to a Novell NDS from saslauthd on a Debian Sarge >> machine. >> >> This works fine: >> ldapsearch -x -b "cn=paulvdv,o=wlg" -D "cn=paulvdv,o=wlg" >>-w secret -H ldaps://firewall.domain.nl:636 >> >> This is my saslauthd.conf: >> >> ldap_servers: ldaps://firewall.domain.nl:636/ >> ldap_tls_cert: /home/paul/.cert/cacert.pem >> ldap_tls_key: /home/paul/.cert/privkey.pem > > It appears you are specifying ca cert as the client cert. Is this what > you want? No, I want to authentificate over an encrypted connection, that's all. > Your configuration does not require client cert so you should > remove those params. Perhaps you wanted to specify > ldap_tls_cacert_(file|dir)? We have it working now with something like: ldap_servers: ldaps://firewall.domain.nl/ ldap_auth_method: fastbind ldap_tls_cacert_file: /path/to/rootcert.pem ldap_filter: cn=%u,o=wlg The rootcert.pem is the root-certificate of the Novell server. A problem is: there are 2 Novell servers what are together the e-directory, can we use 2 root-certificates? >> ldap_search_base: cn=paulvdv,o=wlg >> ldap_filter: cn=%u,o=wlg > > Have you tried this filter in the ldapsearch above? This does not look > right. We've removed the ldap_search_base and added the fastbind, this looks right. Thanks for your help. If you think it could be better, please tell... With regards, Paul van der Vlis. --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Disable creation of hardlinks in message store
> Simon Matter wrote: > >>>Simon Matter wrote: >>> >>> >I've tried to get rid of hardlinked files in our cyrus spools to make >partial mailbox restores easier and more safe. My first idea was to > set >"singleinstancestore: no" in imapd.conf and make all payload files >independant from each other. Unfortunately I realized later that while >incoming messages are stored in independant files, the IMAP COPY > command >still creates hardlinked message files. Of course there is nothing > wrong >with singleinstancestore because the manpage clearly states that only >delivery via lmtp/nntp is affected. >I have now looked at the code and found that mailbox_copyfile() has a >nolink parameter which controls the copy/link behaviour. My idea was > to >create a new config option to disable hardlinks completely. > >My questions: >- is such an option a very bad idea? >- does such a patch already exist somewhere? >- what's the best name of a new config option? >- is there a chance to have such a patch accepted into the > distribution? I'd like to include the following patch into my cyrus-imapd rpm packages to address the issue mentioned above. While testing it on a test box it seemed to work very well. Do the cyrus developers see any possible problem with it? >>> >>>Actually, your patch affects ALL mailbox_copyfile(), which means that >>>messages won't even be hardlinked from the stage./ to the destination >>>mailbox. I don't think we want to do this, since this will hurt >>>performance for all messages deliveries (even single recipient >>> messages). >> >> >> That's why I was asking whether it's a good idea. IIRC >> mailbox_copyfile() >> is also used to handle other files, not only message files. So my >> solution >> was a dirty hack. >> >> >>>IMO, singleinstancestore *should* also govern IMAP COPY (does anyone >> >> >> That's what I expected first but found that it's only implemented for >> incoming messages for unknown reason. Your proposed solution looks like >> the way to go. > > Committed. Thanks, works perfect here. --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
