Daeron wrote:
>Hi,
> My experience is just the oppersite:
> FreeBSD 4.3, Cyrus 2.0.12 from /usr/ports/mail/cyrus-imap
>/usr/local/etc/imapd.conf edited with "sasl_pwcheck: pam"
> I've also tried "PAM".
>/etc/pam.conf with "imap auth required /usr/local/lib/pam_mysql.so
>user=."
>and same fo
Hi,
My experience is just the oppersite:
FreeBSD 4.3, Cyrus 2.0.12 from /usr/ports/mail/cyrus-imap
/usr/local/etc/imapd.conf edited with "sasl_pwcheck: pam"
I've also tried "PAM".
/etc/pam.conf with "imap auth required /usr/local/lib/pam_mysql.so
user=."
and same for pop3
But nothing aut
Install on FreeBSD is very easy.
cd /usr/ports/mail/cyrus-imapd
make
make install
I think it will also install sasl port itself
then u go in /usr/local/etc and configure imapd.conf and cyrus.conf for
your local needs, very easy and it works with no problems.
Rick
On Tue, 3 Jul 2001, Louis L
Louis LeBlanc wrote:
>
>Is that a typo? 'make sure there aren't any entries for imap, pop3,
>etc'???
>
No, it's not. For cyrus, the 'master' takes the place of [x]inetd and
cron entries. It *reuses* the service handlers in much the same way
apache does.
>
>
>What about sieve?
>
same thing.
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 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 g
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 s
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 u
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
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 Pas
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.
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. Modif
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 swit
13 matches
Mail list logo
