The compile problem which is not being able to
link with the Berkeley Database, but before
going into the details of solving that problem,
is there any particular reason you are
starting with the old 1.6.24 instead of the
newer (and better) 2.0.12?
I even believe some guys here on the list hav
> Hi All
>
> I'm pretty happy with my slow progress with Cyrus-IMAP, Postfix, and
> fetchamil.
I'm in the same boat in regards to doing the cooler PAM/LDAP/sieve
stuff. I am currently running cyrus on my own box to create a
prototype that I would like to roll out to the ISP I work for.
I'm curre
David Reid wrote:
>
> So, I eventually found the cause of delivery problems was that the app I
> used to create the mailboxes (not cyradm) was setting the quota to 0. I've
> set them all at a more realistic limit, but how do I remove the quota once
> set from a user? Apart from that it's workin
I also set up cyrus on a Debian potato system,
though I compiled the DB libs locally.
Your setup looks correct. What do the error messages
in auth.log or messages and syslog say.
If I was to troubleshoot it, I would look into the
following.
Try:
imtest -a test -u test -m login panda
I had probl
> > This is a workaround. We really need a solution to
> the
> > problem. We will be looking into some alternatives
> to
> > sleepycats library for some of the databases. I
> was
> > thinking about trying the tdb library from samba
> > project.
>
> What is the advantage of tdb over BerkeleyDB?
I
Hi,
I have a problem with the interaction of sendmail and cyrus, I think
especially lmtpd.
When a mail arrives at sendmail and the user exists and the quota is not
exceeded, everything is ok and sendmail hands the mail to deliver to put it
in the user's mailbox.
The problems occur:
1.) User un
> After some more testing we think that the main problem
> is between lmtpd processes accessing the
> /var/imap/deliverdb databases. While reading a source
> of imap/duplicate.c, there's a note next to
> get_db_name
> function saying that too many processes where
> contending for the locks on del
I am experiencing the same. Sometimes instead of Over quota I get Connection
reset by localhost.
cyrus2.0.12cvs, sendmail 8.11 RedHat 7
Nick Ustinov
[EMAIL PROTECTED]
http://www.videinfra.com
-Original Message-
From: Poliak, Uwe [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 25, 20
Hi,
I pressed the send-button too early when writing the last mail...
Here's the rest:
Cyrus is compiled with the following settings:
# ./configure --with-cyrus-prefix=/usr/local/cyrus --with-cyrus-user=cyrus
--with-cyrus-group=mail --with-auth=unix --without-notif
y --with-libwrap --with-dbd
Haven't seen anything. I use latest cyrus2.0.12-cvs and the same problem
persists. As I said, temporary workaround is to limit number of lmtp
processes by setting sendmail to DeliveryMode=q
Nick Ustinov
[EMAIL PROTECTED]
http://www.videinfra.com
-Original Message-
From: Simon Loader [
Helmut Apfelholz writes:
>
>I've just checked the CVS, duplicate.c hasn't been
>changed at all, so the algorithm remains the same. I
>also haven't seen any patch in the archives.
The patch was submitted to the Cyrus bug reporting address some time
ago. All it does, though, is to provide an eve
[...]
> I then planned that the users log in with their
> email address (or a slightly modified version of
> it to support older versions of Netscape and a
> couple other MUA's that didn't like email addresses
> as log in name) and rewrote the mailbox lookup
> routines to return the new mailbox in
Okay, think I hit enough points in the subject :)
I'm looking at using pam-pgsql to do authentication, instead of sasldb ...
I'm hitting problems with sasldb that I can't explain, where users
passwords all of a sudden don't work, and figure if I move into a db
environment, at least I can better
Greetings,
A while back when this whole discussion about virtual domains started,
one of the temporary solutions was to change the Cyrus code base to
accept different config files. With the new CVS that has the -C config
option design by Ken Murchison, I have been able to successfully
implement
--- Simon Loader <[EMAIL PROTECTED]> wrote:
>
> > After some more testing we think that the main
> problem
> > is between lmtpd processes accessing the
> > /var/imap/deliverdb databases. While reading a
> source
> > of imap/duplicate.c, there's a note next to
> > get_db_name
> > function saying
Hello fellow listmembers,
We switched to a new version of the cyrus imapd (version 2.0.12) and i think we have
encounted the 'locking problem' that is being discussed here.
What we are seeing here is that it takes a long while for the greetings to show even
after the connection has been establ
Wilson,
I did not mean to say that Novell designed LDAP. What I meant to say is
Novell
designed NDS to be highly organized.
Sorry for the "incorrect" terminology and anyone I have offended...
-John
Wilson Yeung wrote:
> > multiple contexts in an ldap tree (since Novell designed LDAP to be
h
Kevin,
Here at Rutgers, we are looking to do the same thing you are, and are
currently running into the same problems you are facing. Our LDAP servers
run
on Novell NDS, and when we initially had this problem with pam_ldap, we
looked
to use the pam_nds module, which we thought would handle the p
before I get flamed,
I meant 01 cent.
Atif,
Fortunately, I am at a University with 2 class B's reserved for IP's. I can
take whatever I want whenever I want to, and that is probably the reason I
didn't even consider IP cost and availability, and how it would affect the
situation. This solution works well in our case, but may not be
"John C. Amodeo" wrote:
>
> Greetings,
>
> A while back when this whole discussion about virtual domains started,
> one of the temporary solutions was to change the Cyrus code base to
..
..
..
> - IP addresses to spare... (You will need 1 address for each virtual
> server)
IP addresses are gett
Ørnulf Nielsen wrote:
>
> [...]
> > I then planned that the users log in with their
> > email address (or a slightly modified version of
> > it to support older versions of Netscape and a
> > couple other MUA's that didn't like email addresses
> > as log in name) and rewrote the mailbox lookup
>
well, it seems that this problem is only experienced by redhat users. i
played with different kernels, same result. what was cyrus ver that worked
fine for you? i tried 2.0.9 - it was just like 2.0.12.
nick
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wedn
Which user should own the relevant cyrus binaries, like deliver?
Root, or cyrus?
Thanks,
Brendan
--- [EMAIL PROTECTED] wrote:
> Hello fellow listmembers,
>
> We switched to a new version of the cyrus imapd
> (version 2.0.12) and i think we have encounted the
> 'locking problem' that is being discussed here.
>
> What we are seeing here is that it takes a long
> while for the greetings to sh
yep, 1.5 worked fine for me as well (except 40-minute long mailbox creation
in a 20Mb mailboxes text file ;-). I thought there is 2.x version that
works. seems there is no. so, that's db3 problem.
nick
-Original Message-
From: NiekR [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 25, 2
--- Nick Ustinov <[EMAIL PROTECTED]> wrote:
> well, it seems that this problem is only experienced
> by redhat users. i
> played with different kernels, same result. what was
> cyrus ver that worked
> fine for you? i tried 2.0.9 - it was just like
> 2.0.12.
Our server was running 1.5.21 first (I
Nick,
we did not have the problem on Cyrus 1.5.14 (not using LMTP) on a Linux 2.2
kernel (Linux RedHat 6.0)
Regards
Niek Rijnbout
At 21:46 25-04-2001 +0300, Nick Ustinov wrote:
>well, it seems that this problem is only experienced by redhat users. i
>played with different kernels, same result
Title: Message
By replicating Tom
Sedge's sieve directory structure and imapd.conf file (as he posted recently), I
was able to get Sieve working. However, I am still unable to get Sieve to
work with the sieveusehomedir=yes option in imapd.conf. I created a script
named .sieve in my home di
Just have the SMTP server authorize
through the same PAM interface that
your cyrus server does.
If you have SASL in the middle, that's
fine too. I think most SMTP servers
these support PAM directly.
-- Michael --
- Original Message -
From: "The Hermit Hacker" <[EMAIL PROTECTED]>
To: <[
30 matches
Mail list logo
