Re: pam ldap auth
"Kevin J. Menard, Jr." wrote: > > Hey guys, > > I'm trying to authenticate using PAM LDAP. I use a debian system, with > mostly debs from woody. However, I built Cyrus 2.0.14 from source, > since the debian packages are horribly out of date. > > I set up SASL to use PAM in imapd.conf, but cyradm cannot use a user > from LDAP for some reason. So, my question is, is NSS LDAP necessary to > get all this working? I didn't want to use it, due to the large number > of people saying how buggy it was, and I didn't see a need for it (I > don't see myself needing to do any lookups other than uid and > userPassword). But maybe I'm missing something. > > And does the user cyrus need to be in any special groups to authenticate > via PAM against LDAP (though I've tried nearly everything at this > point). > > Thanks for any and all info. > > -- > Kevin Hi Kevin, i use pam_ldap with cyrus 2.0.14 and can authenticate against ldap 2.0.11 even with cyradm. In my opinion you do not need nss_ldap. It is only necessary if you want to store information for unix user accounts in a ldap directory. Can you see activity in the ldap log file, when you try to use cyradm ? Perhaps some configuration parameters like ldapbase, ldaphost or ldapport may not be set correctly. Regards, Philipp -- Philipp Sacha | Bosch Telecom GmbH [EMAIL PROTECTED]| Broadband Network Operations http://www.bosch-kabeltv.de/ | Zitadellenweg 34, D-13599 Berlin | Tel.: +49 30 3388-1094, Fax:-1936
Cyrus IMAP not responding
Cyrus Gurus, I have been running Cyrus v2.0.14-NAMESPACE-r3 in a production system for the past 5 days now. During the last two of these days, the imapd server has stopped to respond on 4 occasions. By this I mean that, the master process is running, and child imapd and pop3d processes are all listed in a process listing, but a telnet to port 143 will not bring up the usual banner and imapd greeting after the connection IS established. I am luckily around or a phone call away, to kill the master process and restart it again, which starts allowing connections and sessions again. The logs with the standard suggested settings in syslog.conf, contain no information at all. I do have CYRUS_VERBOSE=9 defined in my env before running the master process. I have just changed local6.debug to local6.* to see if I am missing out on extra little messages, it does seem produce more info. I have no core files around, and my ulimit -c reports 100. Is there any way to do some diagnostics the next time this happens?? One time I sent a kill -SIGSEGV to master, but it did not core, and I was unable to restart it again because master could not bind any ports. Using Redhat 7.1, Linux 2.2.19, Sendmail 8.11.4, Cyrus v2.0.14-NAMESPACE-r3, and there are over 100 clients using this production system. Thanks in advance, Stuart
Re: What is CYRUS_SERVICE? (was Re: Installing on FreeBSD)
On 07/03/01 08:07 PM, Ken Murchison sat at the `puter and typed: > > > > Take a look at your [x]inetd.conf file and make sure there aren't any > entries for imap, pop3, etc. > > Is that a typo? 'make sure there aren't any entries for imap, pop3, etc'??? What about sieve? Thanks Lou -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ
Re: What is CYRUS_SERVICE? (was Re: Installing on FreeBSD)
Louis LeBlanc wrote: > > Thanks for the pointers Joe. This seems to be along the lines I went, > but I am running into a hitch with the test: > > # cyradm -user cyrus localhost > Jul 3 16:51:36 acadia imapd: could not getenv(CYRUS_SERVICE); exiting > Jul 3 16:51:36 acadia imapd: could not getenv(CYRUS_SERVICE); exiting Take a look at your [x]inetd.conf file and make sure there aren't any entries for imap, pop3, etc. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Sieve and websieve question/problem
I'm having a "problem" with sieve and websieve. I use websieve to
create and install a sieve script (listed after this message).
It seems that some rules file the messages into the proper folders, but
they sometimes also arrive in my INBOX. I didn't check off the "Copy"
checkbox in websieve rule, and if you look at the script it generates,
it appears correct. Not all messages that match a particular rule end
up in my INBOX. I don't see anything obvious between the messages that
just go into the proper folder and ones that go into the proper folder
and also into my INBOX. In particular I've been playing with the
"dhcp-server" rule since that list generates messages often.
Are there any logs or debug options that may help?
-Shawn Sivy
The College of NJ
===
# Mail rules for user ssivy
# Created by Websieve version 0.59f
require ["fileinto"];
if allof (address :contains ["from"] "stern@") {
fileinto "INBOX.nadine";
}
if allof (address :contains ["from"] "[EMAIL PROTECTED]") {
fileinto "INBOX.listproc_msgs";
}
elsif allof (address :matches ["from"] "**listproc@**") {
fileinto "INBOX.listproc_msgs";
}
elsif allof (address :contains ["Cc","CC","To","TO"] "dhcp-server") {
fileinto "INBOX.dhcp";
}
elsif allof (address :contains ["Cc","CC","To","TO"]
"[EMAIL PROTECTED]", address :contains
["from"] "MAILER-DAEMON") {
fileinto "INBOX.returned_mail";
}
elsif allof (address :contains ["Cc","CC","To","TO"]
"[EMAIL PROTECTED]", address :contains
["from"] "Mail Delivery Subsystem") {
fileinto "INBOX.returned_mail";
}
elsif allof (header :contains "subject" "Your Driving Record") {
fileinto "INBOX.junk-mail";
}
elsif allof (address :contains ["Cc","CC","To","TO"] "@trenton.edu") {
fileinto "INBOX.junk-mail";
}
elsif allof (header :contains "subject" "toner") {
fileinto "INBOX.junk-mail";
}
elsif allof (address :contains ["from"] "@hotmail.com") {
fileinto "INBOX.junk-mail";
}
elsif allof (address :contains ["from"] "@yahoo.com") {
fileinto "INBOX.junk-mail";
}
elsif allof (address :contains ["from"] "@msn.com") {
fileinto "INBOX.junk-mail";
}
elsif allof (address :contains ["from"] "@cgpn.net") {
fileinto "INBOX.junk-mail";
}
elsif allof (address :contains ["Cc","CC","To","TO"] "@cgpn.net") {
fileinto "INBOX.junk-mail";
}
if allof (address :contains ["Cc","CC","To","TO"] "required-logins@") {
fileinto "INBOX.0required-login";
}
elsif allof (address :contains ["Cc","CC","To","TO"] "info-cyrus@") {
fileinto "INBOX.cyrus";
}
elsif allof (header :contains "subject" "[PORTALS]") {
fileinto "INBOX.0portals-list";
}
else {
keep;
}
##PSEUDO script start
#rule&&1&&ENABLED&&[EMAIL PROTECTED]&&folder&&INBOX.listproc_msgs&&2&&
#rule&&
3&&ENABLED&&*listproc@*&&folder&&INBOX.listproc_msgs&&2&&
#rule&& 5&&ENABLEDdhcp-serverfolder&&INBOX.dhcp&&2&&
#rule&&
7&&ENABLED&&MAILER-DAEMON&&[EMAIL PROTECTED]folder&&INBOX.returned_mail&&2&&
#rule&& 9&&ENABLED&&Mail Delivery
Subsystem&&[EMAIL PROTECTED]folder&&INBOX.returned_mail&&2&&
#rule&& 11&&ENABLED&&Your Driving
Record&&folder&&INBOX.junk-mail&&2&&
#rule&& 13&&ENABLED@trenton.edufolder&&INBOX.junk-mail&&2&&
#rule&& 15&&ENABLED&&toner&&folder&&INBOX.junk-mail&&2&&
#rule&& 17&&ENABLED&&@hotmail.com&&folder&&INBOX.junk-mail&&2&&
#rule&& 19&&ENABLED&&@yahoo.com&&folder&&INBOX.junk-mail&&2&&
#rule&& 21&&ENABLED&&@msn.com&&folder&&INBOX.junk-mail&&2&&
#rule&& 23&&ENABLED&&@cgpn.net&&folder&&INBOX.junk-mail&&2&&
#rule&& 25&&ENABLED@cgpn.netfolder&&INBOX.junk-mail&&2&&
#rule&& 27&&DISABLED&&raid
Event&&address&&[EMAIL PROTECTED]&&3&&
#rule&&
29&&DISABLED&&@extremenetworks.com&&address&&[EMAIL PROTECTED]&&3&&
#rule&&
31&&DISABLED&&coburn@&&address&&[EMAIL PROTECTED]&&3&&
#rule&&
33&&DISABLED&&smalley@&&address&&[EMAIL PROTECTED]&&3&&
#rule&&
35&&DISABLED&&stober@&&address&&[EMAIL PROTECTED]&&3&&
#rule&&
37&&DISABLED&&pignatel@&&address&&[EMAIL PROTECTED]&&3&&
#rule&&
39&&DISABLED&&techwalt@&&address&&[EMAIL PROTECTED]&&3&&
#rule&&
41&&DISABLED&&sbriggs@&&address&&[EMAIL PROTECTED]&&3&&
#rule&&
43&&DISABLED&&sawchuk@&&address&&[EMAIL PROTECTED]&&3&&
#rule&&
45&&DISABLED&&kerswill@&&address&&[EMAIL PROTECTED]&&3&&
#rule&&
47&&DISABLED&&stern@&&address&&[EMAIL PROTECTED]&&3&&
#rule&& 49&&ENABLED&&stern@&&folder&&INBOX.nadine&&3&&
#rule&&
51&&ENABLEDrequired-logins@folder&&INBOX.0required-login&&2&&
#rule&& 53&&ENABLEDinfo-cyrus@folder&&INBOX.cyrus&&2&&
#rule&& 55&&ENABLED&&[PORTALS]&&folder&&INBOX.0portals-list&&2&&
#vacation&&7&&"[EMAIL PROTECTED]", "[EMAIL PROTECTED]"&&On vacation for
the next week&&off
#mode&&basic
Re: Installing on FreeBSD
Hi,
> On Tue, 03 Jul 2001 15:23:46 -0400
> Joe Talbott <[EMAIL PROTECTED]> said:
josepht> Here are the steps I took to install on FreeBSD 4.3-STABLE
There are requests that someone wish to have spool directory in
another place than default. So, current cyrus-imapd port doesn't
create spool automatically. You'll see the following message at the
end of install, instead.
To setup mail spool, modify /usr/local/etc/imapd.conf appropriately,
then run /usr/local/cyrus/bin/mkimap.
josepht> cd /usr/ports/mail/cyrus-imapd/
josepht> sudo make clean
josepht> sudo make
josepht> sudo make install
josepht> # edited imapd.conf, added 'root' and 'cyrus' as admins, added tls-cert
josepht> and key
josepht> sudo vi /usr/local/etc/imapd.conf
You need to run /usr/local/cyrus/bin/mkimap here.
josepht> # configured sendmail to deliver to cyrus
josepht> # there's a sample file in the docs directory
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
Re: Installing on FreeBSD
Thanks for the info Nick. I had no problems with db3 or SASL, and I already have a pretty clean sendmail config that will pipe messages through procmail - which then calls deliver. Makes for a much more dynamic and flexible mail filtering system. As for the PAM stuff, I was really planning to use pwcheck in its usual manner. I have had very good luck with this on 1.6.24 and would like to change as little as possible going to my new server (I'm already changing the OS *and* the imapd version!). Thanks for your response. Lou On 07/03/01 01:45 PM, Nick Sayer sat at the `puter and typed: > It's fairly straightforward. I recommend this set of steps: > > 1. Install the db3 port. Just do that in the ordinary way. > > 2. Search the archives of this list for the SASL pwcheck_pam.c file. > When you build the cyrus-sasl port, you want to modify the build so that > pwcheck uses this file. > > 3. Modify /etc/pam.conf to add entries for the 'cyrus' service to use > whichever PAM functionality you desire (at this point you have the > option of adding other pam module ports if you wish, such as pam_smb). > > 4. Install the cyrus-imap port in the usual manner. You don't need to > add any options. > > 5. Make yourself an /etc/mail/_.mc file. Do this by copying the > sendmail.mc file and modifying it to taste. One thing you will need to > do is this: > > FEATURE(local_lmtp)dnl > define(`confLOCAL_MAILER',`cyrus')dnl > MAILER(smtp)dnl > > MAILER_DEFINITIONS > McyrusP=[IPC], F=lsSDFMngA@/:|SmXz, E=\r\n, S=EnvFromL, R=EnvToL/HdrToL, >T=DNS/RFC822/X-Unix,U=cyrus:cyrus, A=FILE /var/imap/socket/lmtp > > The MAILER_DEFINITION should be salted to taste. The A argument should > be set to wherever the lmtp socket lives, as defined by cyrus.conf, and > the rest of the arguments should shadow the normal SMTP mailer > definition for the most part. > > You may wish to modify the mc file in other ways (for example, adding > cyrus-sasl may make it desirable to add sasl authentication to sendmail > for authenticated SMTP), but such mods are outside the scope of this > document. > > When you're done, make .cf and test it, copying it to sendmail.cf if > it works. Then 'make restart' to restart sendmail. > > That ought to do it. > > > Louis LeBlanc wrote: > > >Hey all. I have Cyrus imapd 1.6.24 running on a RH 6.2 linux box, and > >it has done quite well since just after the 1.6.24 release. No > >complaints whatsoever. Install was complicated, but well documented > >in the Linux HowTo, so great. > > > >Now the problem. I am switching my server to FreeBSD 4.3 and would > >like to upgrade to 2.0.14 - which is present in a FreeBSD port. > > > >Does anyone know where I can find install info specific to FreeBSD? I > >am checking out the html install info in the distribution, and it > >notes a couple Linux specific steps, but . . . > > > >Any and all help is appreciated. > > > >TIA > >Lou > > > > > -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ
Re: Installing on FreeBSD
On 07/03/01 05:07 PM, Joe Talbott sat at the `puter and typed: > Joe Talbott wrote: > > > > forgot this: > > # run mkimap perl script to create directories and set permissions > sudo /usr/local/cyrus/bin/mkimap > > > Of course. I think this is that step that most people actually remember to do and always forget to talk about it :) I did remember this one by the way. L -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ
What is CYRUS_SERVICE? (was Re: Installing on FreeBSD)
Thanks for the pointers Joe. This seems to be along the lines I went, but I am running into a hitch with the test: # cyradm -user cyrus localhost Jul 3 16:51:36 acadia imapd: could not getenv(CYRUS_SERVICE); exiting Jul 3 16:51:36 acadia imapd: could not getenv(CYRUS_SERVICE); exiting IMAP Password: Broken pipe Hmm. I looked in the source for a CYRUS_SERVICE tag, and found that it is limited to the master code. That process reads the /usr/local/etc/cyrus.conf file, right? I do have this file, and I made only minor mods (comment out the POP stuff). I already had the cert and a starting point for a sendmail.mc file (I am piping through procmail, which then calls deliver), so I have half the battle won, but this doesn't seem to work quite right. pwcheck is working: # ps -ax | grep pwcheck 302 ?? Is 0:00.00 /usr/local/sbin/pwcheck as is master: # ps -ax | grep master 286 con- I 0:00.10 /usr/local/cyrus/bin/master Maybe this is a clue? # imtest -t "" -a cyrus localhost C: C01 CAPABILITY failure: prot layer failure bash-2.05# Jul 3 17:06:14 acadia imapd: could not getenv(CYRUS_SERVICE); exiting Jul 3 17:06:14 acadia imapd: could not getenv(CYRUS_SERVICE); exiting Maybe not. Any ideas? Thanks a million. Lou On 07/03/01 03:23 PM, Joe Talbott sat at the `puter and typed: > Louis LeBlanc wrote: > > > > Here are the steps I took to install on FreeBSD 4.3-STABLE > > cd /usr/ports/mail/cyrus-imapd/ > sudo make clean > sudo make > sudo make install > > # edited imapd.conf, added 'root' and 'cyrus' as admins, added tls-cert > and key > sudo vi /usr/local/etc/imapd.conf > > # configured sendmail to deliver to cyrus > # there's a sample file in the docs directory > > # created openssl cert and key > sudo openssl req -new -x509 -nodes -out /var/imap/server.pem -keyout > /var/imap/server.pem -days 365 > > # mv /usr/local/etc/rc.d/imapd.sh.sample to imapd.sh > > # test ssl > imtest -t "" -a cyrus localhost > > # created mailbox > cyradm -user cyrus localhost > localhost> cm user.josepht > localhost> quit > > # added sieve to inetd.conf > sieve stream tcp nowait cyrus /usr/local/cyrus/bin/timsieved > timsieve > d > > # use sieveshell to manage sieve scripts > sieveshell -u josepht localhost > > put /home/josepht/sieve_test.script > > activate sieve_test > > quit > > Good Luck, > Joe > > -- > J o e T a l b o t t| I choose to believe > OSS Engineer - Cornerstone Networks | what I was programmed > An Ntelos Communications Company | to believe. > [EMAIL PROTECTED] - 804-817-7000 | -Futurama > -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ
Re: Installing on FreeBSD
Joe Talbott wrote: > > Louis LeBlanc wrote: > > > > Hey all. I have Cyrus imapd 1.6.24 running on a RH 6.2 linux box, and > > it has done quite well since just after the 1.6.24 release. No > > complaints whatsoever. Install was complicated, but well documented > > in the Linux HowTo, so great. > > > > Now the problem. I am switching my server to FreeBSD 4.3 and would > > like to upgrade to 2.0.14 - which is present in a FreeBSD port. > > > > Does anyone know where I can find install info specific to FreeBSD? I > > am checking out the html install info in the distribution, and it > > notes a couple Linux specific steps, but . . . > > > > Any and all help is appreciated. > > > > Here are the steps I took to install on FreeBSD 4.3-STABLE > > cd /usr/ports/mail/cyrus-imapd/ > sudo make clean > sudo make > sudo make install > > # edited imapd.conf, added 'root' and 'cyrus' as admins, added tls-cert > and key > sudo vi /usr/local/etc/imapd.conf > forgot this: # run mkimap perl script to create directories and set permissions sudo /usr/local/cyrus/bin/mkimap > # configured sendmail to deliver to cyrus > # there's a sample file in the docs directory > > # created openssl cert and key > sudo openssl req -new -x509 -nodes -out /var/imap/server.pem -keyout > /var/imap/server.pem -days 365 > > # mv /usr/local/etc/rc.d/imapd.sh.sample to imapd.sh > > # test ssl > imtest -t "" -a cyrus localhost > > # created mailbox > cyradm -user cyrus localhost > localhost> cm user.josepht > localhost> quit > > # added sieve to inetd.conf > sieve stream tcp nowait cyrus /usr/local/cyrus/bin/timsieved > timsieve > d > > # use sieveshell to manage sieve scripts > sieveshell -u josepht localhost > > put /home/josepht/sieve_test.script > > activate sieve_test > > quit > -- J o e T a l b o t t| I choose to believe OSS Engineer - Cornerstone Networks | what I was programmed An Ntelos Communications Company | to believe. [EMAIL PROTECTED] - 804-817-7000 | -Futurama
Re: pam ldap auth
Hi, I've had very little success using sasl and PAM LDAP for password authentication. Instead I patched cyrus-sasl with the ldap_mysql patch. This seems to be working flawless. TTYL, Adi On Tue, 3 Jul 2001, Kevin J. Menard, Jr. wrote: > Hey guys, > > I'm trying to authenticate using PAM LDAP. I use a debian system, with > mostly debs from woody. However, I built Cyrus 2.0.14 from source, > since the debian packages are horribly out of date. > > I set up SASL to use PAM in imapd.conf, but cyradm cannot use a user > from LDAP for some reason. So, my question is, is NSS LDAP necessary to > get all this working? I didn't want to use it, due to the large number > of people saying how buggy it was, and I didn't see a need for it (I > don't see myself needing to do any lookups other than uid and > userPassword). But maybe I'm missing something. > > And does the user cyrus need to be in any special groups to authenticate > via PAM against LDAP (though I've tried nearly everything at this > point). > > Thanks for any and all info. > > -- > Kevin >
Re: Installing on FreeBSD
It's fairly straightforward. I recommend this set of steps: 1. Install the db3 port. Just do that in the ordinary way. 2. Search the archives of this list for the SASL pwcheck_pam.c file. When you build the cyrus-sasl port, you want to modify the build so that pwcheck uses this file. 3. Modify /etc/pam.conf to add entries for the 'cyrus' service to use whichever PAM functionality you desire (at this point you have the option of adding other pam module ports if you wish, such as pam_smb). 4. Install the cyrus-imap port in the usual manner. You don't need to add any options. 5. Make yourself an /etc/mail/_.mc file. Do this by copying the sendmail.mc file and modifying it to taste. One thing you will need to do is this: FEATURE(local_lmtp)dnl define(`confLOCAL_MAILER',`cyrus')dnl MAILER(smtp)dnl MAILER_DEFINITIONS McyrusP=[IPC], F=lsSDFMngA@/:|SmXz, E=\r\n, S=EnvFromL, R=EnvToL/HdrToL, T=DNS/RFC822/X-Unix,U=cyrus:cyrus, A=FILE /var/imap/socket/lmtp The MAILER_DEFINITION should be salted to taste. The A argument should be set to wherever the lmtp socket lives, as defined by cyrus.conf, and the rest of the arguments should shadow the normal SMTP mailer definition for the most part. You may wish to modify the mc file in other ways (for example, adding cyrus-sasl may make it desirable to add sasl authentication to sendmail for authenticated SMTP), but such mods are outside the scope of this document. When you're done, make .cf and test it, copying it to sendmail.cf if it works. Then 'make restart' to restart sendmail. That ought to do it. Louis LeBlanc wrote: >Hey all. I have Cyrus imapd 1.6.24 running on a RH 6.2 linux box, and >it has done quite well since just after the 1.6.24 release. No >complaints whatsoever. Install was complicated, but well documented >in the Linux HowTo, so great. > >Now the problem. I am switching my server to FreeBSD 4.3 and would >like to upgrade to 2.0.14 - which is present in a FreeBSD port. > >Does anyone know where I can find install info specific to FreeBSD? I >am checking out the html install info in the distribution, and it >notes a couple Linux specific steps, but . . . > >Any and all help is appreciated. > >TIA >Lou >
pam ldap auth
Hey guys, I'm trying to authenticate using PAM LDAP. I use a debian system, with mostly debs from woody. However, I built Cyrus 2.0.14 from source, since the debian packages are horribly out of date. I set up SASL to use PAM in imapd.conf, but cyradm cannot use a user from LDAP for some reason. So, my question is, is NSS LDAP necessary to get all this working? I didn't want to use it, due to the large number of people saying how buggy it was, and I didn't see a need for it (I don't see myself needing to do any lookups other than uid and userPassword). But maybe I'm missing something. And does the user cyrus need to be in any special groups to authenticate via PAM against LDAP (though I've tried nearly everything at this point). Thanks for any and all info. -- Kevin
Re: Installing on FreeBSD
Louis LeBlanc wrote: > > Hey all. I have Cyrus imapd 1.6.24 running on a RH 6.2 linux box, and > it has done quite well since just after the 1.6.24 release. No > complaints whatsoever. Install was complicated, but well documented > in the Linux HowTo, so great. > > Now the problem. I am switching my server to FreeBSD 4.3 and would > like to upgrade to 2.0.14 - which is present in a FreeBSD port. > > Does anyone know where I can find install info specific to FreeBSD? I > am checking out the html install info in the distribution, and it > notes a couple Linux specific steps, but . . . > > Any and all help is appreciated. > Here are the steps I took to install on FreeBSD 4.3-STABLE cd /usr/ports/mail/cyrus-imapd/ sudo make clean sudo make sudo make install # edited imapd.conf, added 'root' and 'cyrus' as admins, added tls-cert and key sudo vi /usr/local/etc/imapd.conf # configured sendmail to deliver to cyrus # there's a sample file in the docs directory # created openssl cert and key sudo openssl req -new -x509 -nodes -out /var/imap/server.pem -keyout /var/imap/server.pem -days 365 # mv /usr/local/etc/rc.d/imapd.sh.sample to imapd.sh # test ssl imtest -t "" -a cyrus localhost # created mailbox cyradm -user cyrus localhost localhost> cm user.josepht localhost> quit # added sieve to inetd.conf sieve stream tcp nowait cyrus /usr/local/cyrus/bin/timsieved timsieve d # use sieveshell to manage sieve scripts sieveshell -u josepht localhost > put /home/josepht/sieve_test.script > activate sieve_test > quit Good Luck, Joe -- J o e T a l b o t t| I choose to believe OSS Engineer - Cornerstone Networks | what I was programmed An Ntelos Communications Company | to believe. [EMAIL PROTECTED] - 804-817-7000 | -Futurama
Installing on FreeBSD
Hey all. I have Cyrus imapd 1.6.24 running on a RH 6.2 linux box, and it has done quite well since just after the 1.6.24 release. No complaints whatsoever. Install was complicated, but well documented in the Linux HowTo, so great. Now the problem. I am switching my server to FreeBSD 4.3 and would like to upgrade to 2.0.14 - which is present in a FreeBSD port. Does anyone know where I can find install info specific to FreeBSD? I am checking out the html install info in the distribution, and it notes a couple Linux specific steps, but . . . Any and all help is appreciated. TIA Lou -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ
some contributions to cyrus imapd I miss in 2.0.14
Hi,
I just try to get cyrus imapd 2.0.14 working on my SuSE 7.2 box,
creating a modified version of the (2.0.12) RPM file from ftp.suse.com,
and considering some old version of an RPM from ftp.redhat.com.
1) I want to suggest the first two patches as "formal" improvements for
the next cyrus-imapd release.
- as far as I understand, the tcl version of cyradm is considered
outdated. That's why I suggest to move cyradm.1 from man/ to cyradm/,
from where it can be manually installed if wanted. Currently the
cyradm.1 manpage is first installed and afterwards overwritten during
installation of the perl version.
- SuSE uses a different mandir. This is currently not very well
supported. In the redhat RPM file I found a 2.0.5-mandir patch, on which
my mandir-patch is based. (see first attachment)
- within SuSEs rpm file I found a patch to imap/quota.c which adds the
't' option for a quota report. As it might be useful (currently I have
no own experiences), I updated this patch for 2.0.14 (see second
attachment).
2) I found some more patches within SuSEs (attachments 3 + 4) and
Redhats (attachment 5) RPM file, but I can't comment on them, cause I
didn't fully understand what they fix :-) Maybe somebody can explain,
whether one should use them ...
3) My last attachment is a shell script, which adds some services to
/etc/services. This can be integrated into an RPM file, at least until
the officially distributed version of /etc/services contains all
services used by cyrus. I'm sure there are more elegant ways to
implement such a script e.g. in perl, but this one works for me :-)
This was for the simple part. I just managed to compile/install
cyrus-imapd-2.0.14.rpm on my SuSE 7.2 box.
Now I will have to face the hard task: trying to configure it for our
demands as a small standalone mail server together with postfix, and
maybe later also websieve, HORDE/IMP and whatever other useful tools I
can get :-)
Olaf.
--- cyrus-imapd-2.0.5/man/Makefile.in Sat Jun 17 18:49:10 2000
+++ cyrus-imapd-2.0.5/man/Makefile.in Sat Jun 17 18:49:48 2000
@@ -60,8 +60,9 @@
prefix = @prefix@
exec_prefix = @exec_prefix@
cyrus_prefix = @cyrus_prefix@
+mandir=@mandir@
-MAN1 = $(srcdir)/cyradm.1 $(srcdir)/imtest.1 $(srcdir)/installsieve.1
+MAN1 = $(srcdir)/imtest.1 $(srcdir)/installsieve.1
MAN3 = $(srcdir)/imclient.3
MAN5 = $(srcdir)/imapd.conf.5 $(srcdir)/krb.equiv.5 $(srcdir)/cyrus.conf.5
MAN8 = $(srcdir)/arbitron.8 $(srcdir)/collectnews.8 $(srcdir)/deliver.8 \
@@ -77,19 +78,19 @@
install:
for file in $(MAN1); \
do \
- $(INSTALL) -m 644 $$file $(DESTDIR)$(prefix)/man/man1 || exit 1; \
+ $(INSTALL) -m 644 $$file $(DESTDIR)$(mandir)/man1 || exit 1; \
done
for file in $(MAN3); \
do \
- $(INSTALL) -m 644 $$file $(DESTDIR)$(prefix)/man/man3 || exit 1; \
+ $(INSTALL) -m 644 $$file $(DESTDIR)$(mandir)/man3 || exit 1; \
done
for file in $(MAN5); \
do \
- $(INSTALL) -m 644 $$file $(DESTDIR)$(prefix)/man/man5 || exit 1; \
+ $(INSTALL) -m 644 $$file $(DESTDIR)$(mandir)/man5 || exit 1; \
done
for file in $(MAN8); \
do \
- $(INSTALL) -m 644 $$file $(DESTDIR)$(prefix)/man/man8 || exit 1; \
+ $(INSTALL) -m 644 $$file $(DESTDIR)$(mandir)/man8 || exit 1; \
done
.c.o:
--- cyrus-imapd-2.0.5/Makefile.in Sat Jun 17 18:50:20 2000
+++ cyrus-imapd-2.0.5/Makefile.in Sat Jun 17 18:50:46 2000
@@ -56,6 +56,7 @@
prefix = @prefix@
exec_prefix = @exec_prefix@
cyrus_prefix = @cyrus_prefix@
+mandir = @mandir@
all:: checkdepend
@for d in $(SUBDIRS); \
@@ -68,10 +69,10 @@
$(srcdir)/install-sh -d ${DESTDIR}$(exec_prefix)/bin
$(srcdir)/install-sh -d ${DESTDIR}$(exec_prefix)/lib
$(srcdir)/install-sh -d ${DESTDIR}$(prefix)/include/cyrus
- $(srcdir)/install-sh -d ${DESTDIR}$(prefix)/man/man1
- $(srcdir)/install-sh -d ${DESTDIR}$(prefix)/man/man3
- $(srcdir)/install-sh -d ${DESTDIR}$(prefix)/man/man5
- $(srcdir)/install-sh -d ${DESTDIR}$(prefix)/man/man8
+ $(srcdir)/install-sh -d ${DESTDIR}$(mandir)/man1
+ $(srcdir)/install-sh -d ${DESTDIR}$(mandir)/man3
+ $(srcdir)/install-sh -d ${DESTDIR}$(mandir)/man5
+ $(srcdir)/install-sh -d ${DESTDIR}$(mandir)/man8
@for d in $(SUBDIRS); \
do \
(cd $$d; echo "### Making" install "in" `pwd`; \
--- cyrus-imapd-2.0.14.orig/imap/quota.cMon Mar 5 23:27:25 2001
+++ cyrus-imapd-2.0.14.patched/imap/quota.c Tue Jul 3 12:14:01 2001
@@ -39,7 +39,7 @@
* OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*
*/
-/* $Id: quota.c,v 1.38 2001/03/05 22:27:25 leg Exp $ */
+/* $Id: quota.c,v 1.39 2001/07/03 12:13:41 leg Exp $ */
#include
@@ -122,11 +122,12 @@
int opt;
int fflag = 0;
int r, code = 0;
+int tflag = 0;
char *alt_c
Re: PAM without SASLDB
Stuart Clark wrote: > > How can I get AUTH=DIGEST-MD5 AUTH=CRAM-MD5 removed from the CAPABILITY listing, and >still have cyrus use PAM for authentication? > > * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID >NO_ATOMIC_RENAME UNSELECT MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES >IDLE AUTH=DIGEST-MD5 AUTH=CRAM-MD5 X-NETSCAPE > > Some clients will use this DIGEST method because it is advertised, but I dont have >any user/passwd entries in the /etc/sasldb. If I remove the /etc/sasldb file, it is >OK, but I get many "unable to open Berkeley db /etc/sasldb: No such file or >directory" errors in the log file (which hides the severity of signaled to death by >11). > Remove /usr/lib/sasl/libcrammd5* and /usr/lib/sasl/libdigestmd5*. Ken -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
