Try using saslauthd as your verifier and run saslauthd -a pam
Should cure you.
--On Thursday, May 16, 2002 3:03 PM +0800 LiuJinhui
<[EMAIL PROTECTED]> wrote:
>
> I have configure smtp-auth via PAM-ldap in my server.
> So I think there is no problem with pam-ldap.
> But when I configure my
I am trying to use deliver (2.1.4) from procmail. According to the
man-page and several HOWTO-documents on the web describing solutions
with earlier versions of cyrus, "deliver -a foo -m user.foo.folder"
shoud deliver to the folder "folder" of user foo, as should
"deliver -a foo -m folder foo". No
OK, It seems that it was my fault since i cant reproduce the same
problem
Rename is now working as expected with BB and user.x.
Thanks...
On Wed, 15 May 2002, Michael Bacon wrote:
> Would it be sufficient if the patch were altered slightly to send a
> LOG_DEBUG message to syslog every time the master decremented one of the
> worker counters, specifying what it did? Right now, it seems like the
I've had some ideas for a bit of i
On Thu, 16 May 2002, Jeremy Howard wrote:
> I *strongly* recommend also including shutdown.diff. This is important
> in Linux to avoid sockets handing around in CLOSE_WAIT state. Remove the
> ' && !imapd_in->tls_conn' bit everywhere for general distribution--this
> is a workaround for a memory
On Thu, 16 May 2002, Jeremy Howard wrote:
> I'm not 100% sure, but I think the change you've made to return if the
> centry isn't found may mean the nconnections doesn't get updated
> correctly in some cases. You probably want to update nconnections in the
> case of the SERVICE_CONNECTION messa
Jeremy Howard wrote:
>
> Henrique de Moraes Holschuh wrote:
>
> >I don't know what Ken and Lawrence think of these patches, but I just
> >finished porting the child pid tracking of master-avail.diff to 2.1.4CVS,
> >and will post that to this list soon. I will also include it in Debian,
> >whi
Jeremy Howard wrote:
>
> Lawrence Greenfield wrote:
>
> > Date: Wed, 15 May 2002 16:02:42 -0300
> > From: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
> >[...]
> > The point is, if that indeed happens, log or no log, master loses track of
> > the number of children that can service
On Thu, 16 May 2002, Ken Murchison wrote:
> If you have multiple services/processes the cores will overwrite each
> other, so you need to catch it fairly quickly (unless they all have the
Unless you tell the kernel to use the pid in the corefile name...
Add this to the script on Linux 2.4.x:
[ -
Henrique de Moraes Holschuh wrote:
>
> On Thu, 16 May 2002, Ken Murchison wrote:
> > If you have multiple services/processes the cores will overwrite each
> > other, so you need to catch it fairly quickly (unless they all have the
>
> Unless you tell the kernel to use the pid in the corefile n
Date: Thu, 16 May 2002 09:32:17 -0300
From: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
[...]
I would like to add a "Ominous events" counter to the SNMP MIB, which would
be increased by all weirdness master notices (children dying in available
state, children dying with non-OK e
On Thu, 16 May 2002, Lawrence Greenfield wrote:
>From: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
> [...]
>I would like to add a "Ominous events" counter to the SNMP MIB, which would
>be increased by all weirdness master notices (children dying in available
>state, children dy
Please disregard any "no service found, child #" messages this patch causes,
it is OK to have children not belonging to any service (EVENTS children, for
example). Just remove the else clause that does that syslogging entirely.
--
"One disk to rule them all, One disk to find them. One disk to
For what its worth, we run into this problem a lot in our environment as
well... I had come to the same conclusion as Jeremy and Henrique did before
they even posted their message about it to the list.
The environment we are running is as follows:
Cyrus IMAPD 2.0.16
Compaq Tru64 5.1 on Alpha
This is a slightly updated version of the patch, rediffed to apply cleanly
to 2.1.4 as distributed in the tarball. It logs when child die for no good
reason, so it should help address concerns that it would mask a worse
problem.
--
"One disk to rule them all, One disk to find them. One disk t
I'm running 2.1.4 on Solaris with SASL 2.1.3-BETA and have a question that I
haven't been able to find in the documentation or the archives. I'm new to
both, so please bear with me.
I'm using auxprop as the pwcheck_method. We would like to be able to switch
our Cyrus service between two hosts
Hi,
I've got a folder that I want to wipe, but it's got a \Noselect flag
and my attempts at removal are thwarted :/
CUT
$ /usr/cyrus/bin/reconstruct -r user.foo
user.foo
user.foo.Calendar
user.foo.Contacts
user.foo.Deleted Items
user.foo.Deleted Items.Calendar11
user.foo.Drafts
use
On Thu, 16 May 2002, Mathew Hennessy wrote:
> >What version of cyrus is this?
> >
> CVS:
Run recovery on your databases (ctl_cyrusdb -r)
-Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Group * Cyert Hall 235 * 412-268-7456
Research Sys
On Thu, 16 May 2002, Mathew Hennessy wrote:
> I've got a folder that I want to wipe, but it's got a \Noselect flag
> and my attempts at removal are thwarted :/
What version of cyrus is this?
-Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew
Rob Siemborski wrote:
>On Thu, 16 May 2002, Mathew Hennessy wrote:
>
>
>
>>I've got a folder that I want to wipe, but it's got a \Noselect flag
>>and my attempts at removal are thwarted :/
>>
>>
>
>What version of cyrus is this?
>
CVS:
name : Cyrus IMAPD
version: v2.1.4 2002/
On Thu, 16 May 2002, Mathew Hennessy wrote:
> Did that, then a reconstruct -r user.*.. No luck.. Still listed as
> \Noselect, still a reserved mailbox.. (wishing the cyradm dm command
> had a --force option)..
>
> The underlying directory exists, with cyrus.* files.. The big problem
> with th
Rob Siemborski wrote:
>Run recovery on your databases (ctl_cyrusdb -r)
>
Did that, then a reconstruct -r user.*.. No luck.. Still listed as
\Noselect, still a reserved mailbox.. (wishing the cyradm dm command
had a --force option)..
The underlying directory exists, with cyrus.* files.. T
Hi,
in an attempt to see if it solved the mozilla unseen problem (see
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&msg=13859)
I compiled cyrus with db3 as the seen db. I quickly went back to flat
because I saw much more "DBERRORS db3: x lockers" than normal (btw, is
LiuJinhui wrote:
>
> I have configure smtp-auth via PAM-ldap in my server.
>So I think there is no problem with pam-ldap.
> But when I configure my cyrus-imap to authorize via
>PAM-ldap,I got the error in log:
>
> May 16 14:56:53 test1 imapd[22815]: unrecognized plaintext verifier PAM
>
Henrique de Moraes Holschuh wrote:
>Still, I am seriously thinking about doing something to any unknown children
>master notices (with proper LOG_ERR logging, of course) because said
>children is messaging it. Such a thing (unknown children) can only happen
>if either the underlying OS is messed
Ken Murchison wrote:
>I'm running a config almost the same as you and have never seen this
>problem. AFAIK, the CMU guys have never seen this either. Do you have
>a core that you can run a backtrace on, or can you force a core by
>setting MALLOC_CHECK_=2 before starting master (see malloc(3) fo
Jeremy Howard wrote:
>
> Ken Murchison wrote:
>
> >I'm running a config almost the same as you and have never seen this
> >problem. AFAIK, the CMU guys have never seen this either. Do you have
> >a core that you can run a backtrace on, or can you force a core by
> >setting MALLOC_CHECK_=2 be
Date: Fri, 17 May 2002 09:35:39 +1000
From: Jeremy Howard <[EMAIL PROTECTED]>
[...]
Yes, 2.1.3 with skiplist for everything. We have the tls cache turned
off, however. We prune the delivery database with -E0 every hour to
avoid it getting big (otherwise DB recovery takes too long)
Just a little note about this patch. This part:
+/* Did we find it? */
+if (!c || c->pid != msg->service_pid) {
+ syslog(LOG_ERR, "can't find pid %d to process message %d",
+ msg->service_pid, msg->message);
+ return;
We found that this actually occured quite-regularly, especially on a
Actually, a number of users having been saying that renaming folders seems
to cause problems. I think I've found a completely reproduceable scenario
that crashes the IMAP server for me every time.
[root@server2 root]# telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.
Escape charact
Ken Murchison wrote:
>If you set MALLOC_CHECK_=2, then imapd will abort() whenever it thinks
>that there might be a corruption. By examining this core, it is easier
>to track down these problems. I've done this a few times to track down
>the subtle errors that have baffled others.
>
>
Great.
Henrique de Moraes Holschuh wrote:
>On Thu, 16 May 2002, Jeremy Howard wrote:
>
>
>>I *strongly* recommend also including shutdown.diff. This is important
>>in Linux to avoid sockets handing around in CLOSE_WAIT state. Remove the
>>' && !imapd_in->tls_conn' bit everywhere for general distribu
Rob, could you post a core backtrace as well?
Rob Mueller (fastmail) wrote:
>Actually, a number of users having been saying that renaming folders seems
>to cause problems. I think I've found a completely reproduceable scenario
>that crashes the IMAP server for me every time.
>
>[root@server2 roo
Something like this might make life easier for admins who still
have problems understanding what the first S in SASL is supposed to
be referring to:
--- perl/sieve/managesieve/managesieve.c.2.1.4 Thu May 16 17:06:30 2002
+++ perl/sieve/managesieve/managesieve.cFri May 17 08:46:02 2002
@@
34 matches
Mail list logo
