Hey Devdas,
Tuesday, June 26, 2001, 5:28:22 AM, you wrote:
DB> On Tue, 26 Jun 2001, Devdas Bhagat spewed into the ether:
DB>
>> Cannot authenticate to server as cyrus
>>
>> Without the -u option, I get the error
>> Cannot connect to server
>> if I try to do anything
DB> Ok, I fixed that erro
Hey Ken,
Thursday, July 05, 2001, 9:45:04 PM, you wrote:
KM> I am pleased to announce the availability of a selectable hierarchy
KM> separator for Cyrus IMAP. Up until now, Cyrus used a netnews-style
KM> hierarchy, where '.' was used as the hierarchy delimiter -- thus
KM> prohibiting '.' from
Hey guys,
Sorry for the massive post here, but I asked very similar
questions on all these lists. I finally got my problem fixed,
and figured I would share my results with each of the lists, in
case anyone else asks.
You're all probably gonna laugh when you here what I did t
Nick Sayer writes:
>
>I wrote a perl script that takes a Unix "mbox" formatted mailbox and
>uploads it to an IMAP folder. I could post and/or e-mail it if there is
>any demand.
Does it preserve status flags? If so, I'm certainly interested.
Otherwise, I'll just use procmail/formail.
--
-Gar
On Thu, Jul 05, 2001 at 10:24:25PM +0200, GOMBAS Gabor wrote:
> On Thu, Jul 05, 2001 at 12:01:20PM -0400, Scott Russell wrote:
>
> > No core files are generated when a sig 11 happens so a gdb trace isn't
> > available.
>
> Are you sure there are no limits on the core file size? On most Linux sys
Sam Smith wrote:
>I have seen all the old messages about using mbxcvt and c-client. How does that
>work exactly? It says in the docs that cyrus imap is NOT one of the formats it
>supports.
>
>Also the scripts from "Managing IMAP" are out-of-date, since at least one uses
>the tcl version of cyradm
I stronly recommend you use the sendmail.mc bits that I posted a little
while ago. It works, it preserves the envelope headers for sieve, it
avoids forking a process (deliver) needlessly in deliveries and allows
cyrus to hardlink CCed messages.
And sendmail is not hard to configure. It is hard
Sorry if this is duplicated, I never saw it come thru the first time
so I thought I would resend it.
---original message--
You know, I'm not totally sure 2.0.12 is much more stable. Last night
I backed down to 2.0.12, and guess what. Right at sta
I am pleased to announce the availability of a selectable hierarchy
separator for Cyrus IMAP. Up until now, Cyrus used a netnews-style
hierarchy, where '.' was used as the hierarchy delimiter -- thus
prohibiting '.' from appearing in mailbox names. This release allows a
UNIX-style '/' separator
GOMBAS Gabor wrote:
>
> On Thu, Jul 05, 2001 at 12:01:20PM -0400, Scott Russell wrote:
>
> Well, I've been running 2.0.14 for over a month now and I haven't seen any
> "signaled to death" messages (or any other problems) with it. Some older
> versions did have problems, but 2.0.14 works nicely
On Thu, Jul 05, 2001 at 12:01:20PM -0400, Scott Russell wrote:
> No core files are generated when a sig 11 happens so a gdb trace isn't
> available.
Are you sure there are no limits on the core file size? On most Linux systems
it defaults to 0 thus preventing the creation of any core files.
> O
Scott Russell wrote:
>
> Ken -
>
> The patch you supplied 'fixed' it. (I'm not sure why not being a C coder
> myself). Does this patch actually fix the problem or does it back out a
> change that was added going from 2.0.13 to 2.0.14?
It should fix the problem. Basically, imapd processes are
Ken -
The patch you supplied 'fixed' it. (I'm not sure why not being a C coder
myself). Does this patch actually fix the problem or does it back out a
change that was added going from 2.0.13 to 2.0.14?
Side note, the patch didn't apply cleanly. Hunk2 failed even after I fixed
the line wrap damag
Scott Russell wrote:
>
> All -
>
> I'm new to Cyrus and have been experiencing sig 11 issues on imapd over the
> past 2 weeks. I've spent a great deal of time reading the list archives
> trying to id the root cause. So far it hasn't been pretty but I've boiled
> down to the following info.
[.
Greets Again.
Following up on my previous email I've now got a core file from cyrus
2.0.14. This comes from a sig 11 of imapd during auth from my previously
posted hurtme.php script. My current config is listed in the previous email
as well:
[root@oggvorbis test1]# gdb /usr/cyrus/bin/imapd core
From: "Christopher Riordan" <[EMAIL PROTECTED]>
> I keep getting these and there is no helpful message I can get. I don't
know
> what file it is complaining about, tis is all I get in teh logs.
>
> Jul 5 09:38:37 hal lmtpd[700]: DBERROR: dbenv->open failed: No such file
or
> directory
> Jul 5 09
All -
I'm new to Cyrus and have been experiencing sig 11 issues on imapd over the
past 2 weeks. I've spent a great deal of time reading the list archives
trying to id the root cause. So far it hasn't been pretty but I've boiled
down to the following info.
Current Config:
Red Hat 6.2 + errata
I keep getting these and there is no helpful message I can get. I don't know
what file it is complaining about, tis is all I get in teh logs.
Jul 5 09:38:37 hal lmtpd[700]: DBERROR: dbenv->open failed: No such file or
directory
Jul 5 09:38:37 hal lmtpd[700]: deliver: unable to init duplicate de
I have seen all the old messages about using mbxcvt and c-client. How does that
work exactly? It says in the docs that cyrus imap is NOT one of the formats it
supports.
Also the scripts from "Managing IMAP" are out-of-date, since at least one uses
the tcl version of cyradm.
What are people using
Louis LeBlanc wrote:
> Jul 4 22:17:15 acadia deliver[2376]: connect(/home/mail/socket/lmtp) failed:
>Permission denied
>
> However,
> # ls -l /home/mail/socket
> total 0
> srwxrwxrwx 1 root mail 0 Jul 4 20:20 lmtp
And what about the permissions on /home/mail/socket, and /home/mail
(and ul
Louis LeBlanc wrote:
> Now another change in error messages, not lmtp this time. I'm gettin'
> signalled to death by 11. Pisser.
>
> Is 2.0.14 a bad release? I see a few messages in the archives with no
> solutions.
>
2.0.12 is probably the most stable 2.x release, although it's not great for
v
21 matches
Mail list logo