Edward Prendergast wrote:
> Sorry - that was a typo in the command. I did ascertain that I should've
> been using a username not a mailbox name and changed the command
> accordingly, as you can see in the logs below.
>
> I'm not sure how to apply this information about the unix hierarchy
> separa
Nikos Gatsis wrote:
> I had to be more specific.
> I need advices for backing up cyrus emails...
>
> Thank you
The individual emails are merely text files on a Unix file system, you
can back them up with pretty much any Unix backup tool, though don't
ignore the advice to export the databases at
I had to be more specific.
I need advices for backing up cyrus emails...
Thank you
Mike Eggleston wrote:
On Thu, 25 Oct 2007, Nikos Gatsis might have said:
Hello list.
I need some advice for backup my system.
Is there a tutorial or help for my question?
I use slapcat(8) to a file, t
> Simon Matter wrote:
>>> Simon Matter wrote:
> On the Linux box, all fresh compilations aside from the sasl 2.1.15
> binaries:
I once posted to the list that 2.3.9 needs at least cyrus-sasl-2.1.19.
As
a package maintainer I know that :)
>>> Did you ever figure out why? I'm
> Hello Simon,
>
> When your latest source rpm can be available on your download site?
Hi Patrick,
This could take some time because I also have to wait for some patches to
get updated, or do it myself where I can. I did an 2.3.10-RC package but
found that a number changes require some bigger upd
John Capo wrote:
> On Thu, October 25, 2007 21:10, John Capo wrote:
>> Quoting Ken Murchison ([EMAIL PROTECTED]):
>>
>>> Simon Matter wrote:
>>>
> On the Linux box, all fresh compilations aside from the sasl 2.1.15
> binaries:
>
I once posted to the list that 2.3.9 needs at least
Simon Matter wrote:
>> Simon Matter wrote:
On the Linux box, all fresh compilations aside from the sasl 2.1.15
binaries:
>>> I once posted to the list that 2.3.9 needs at least cyrus-sasl-2.1.19.
>>> As
>>> a package maintainer I know that :)
>> Did you ever figure out why? I'm not surpr
Hello Simon,
When your latest source rpm can be available on your download site?
I wonder when the statuscache could be offically patched...
BTW, the renaming folder patch requires admin ppl to cleanup (renamed)
folders by script.
Is it possible possible to purge them immediately while users cha
Hi,
I'm sorry to bother everyone, but I'm trying to unsubscribe from this
list.
I've sent the requisite e-mail to the unsubscribe link on the cyrus
website repeatedly. I still get e-mails.
Does anyone know about this?
Thanks,
-N
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wi
On Thu, October 25, 2007 21:10, John Capo wrote:
> Quoting Ken Murchison ([EMAIL PROTECTED]):
>
>> Simon Matter wrote:
>>
On the Linux box, all fresh compilations aside from the sasl 2.1.15
binaries:
>>>
>>> I once posted to the list that 2.3.9 needs at least cyrus-sasl-2.1.19. As a
Quoting Ken Murchison ([EMAIL PROTECTED]):
> Simon Matter wrote:
> >> On the Linux box, all fresh compilations aside from the sasl 2.1.15
> >> binaries:
> >
> > I once posted to the list that 2.3.9 needs at least cyrus-sasl-2.1.19. As
> > a package maintainer I know that :)
>
> Did you ever figur
2.3.7 on frontend and one backend (RedHat 5) and 2.3.9 on the other
backend (freebsd 6.1).
Most of errors are between frontend (imap2) and freebsd backend
(imap-old) and protocol is pop3:
Oct 25 20:37:30 imap2 pop3[12945]: connect(imap-old.amis.net) failed:
Connection timed out
Oct 25 20:37:30
> Simon Matter wrote:
>>> On the Linux box, all fresh compilations aside from the sasl 2.1.15
>>> binaries:
>>
>> I once posted to the list that 2.3.9 needs at least cyrus-sasl-2.1.19.
>> As
>> a package maintainer I know that :)
>
> Did you ever figure out why? I'm not surprised that code in Cyru
On Mon, 22 Oct 2007, Rob Mueller wrote:
>> squatter would really benefit from incremental updates. At the moment a
>> single new message in a mailbox containing 20k messages causes it to read
>> in all the existing messages in order to regenerate the index.
>
> We spoke to Ken about this ages back
On Thu, 25 Oct 2007, Nikos Gatsis might have said:
> Hello list.
> I need some advice for backup my system.
> Is there a tutorial or help for my question?
I use slapcat(8) to a file, then backup the file in my regular backup system.
Mike
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus
Simon Matter wrote:
>> On the Linux box, all fresh compilations aside from the sasl 2.1.15
>> binaries:
>
> I once posted to the list that 2.3.9 needs at least cyrus-sasl-2.1.19. As
> a package maintainer I know that :)
Did you ever figure out why? I'm not surprised that code in Cyrus
somehow d
Hello list.
I need some advice for backup my system.
Is there a tutorial or help for my question?
Thank you
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
On Thu, Oct 25, 2007 at 10:38:01AM -0400, Ken Murchison wrote:
> Vladimir Nikolic wrote:
> >
> > I have questions regarding murder scalability. Untill last week we had
> > one imap server with about 5 users and 2TB mailboxes. Server was
> > overloaded and little slow but there was no trouble
>
> On the Linux box, all fresh compilations aside from the sasl 2.1.15
> binaries:
I once posted to the list that 2.3.9 needs at least cyrus-sasl-2.1.19. As
a package maintainer I know that :)
Regards,
Simon
>
> imapd 2.3.7 + sasl 2.1.15: works
> imapd 2.3.7 + sasl 2.1.22: works
> imapd 2.3.9 +
Vladimir Nikolic wrote:
> Hi,
>
> I have questions regarding murder scalability. Untill last week we had
> one imap server with about 5 users and 2TB mailboxes. Server was
> overloaded and little slow but there was no troubles like connections
> drop and repeatedly asking users for password
On 10/25/07, Wayne <[EMAIL PROTECTED]> wrote:
> I have an ipurge event in my cyrus.conf that doesn't appear to be
> running. I had moved it from a cron job (which worked) to a cyrus
> event.
>
> purgejunk cmd="ipurge -f -d 15 'user/*/Junk Mail'" at=1700
I thing % is more appropriate than *
On 25 Oct 07, at 1501, Ken Murchison wrote:
> Ian G Batten wrote:
>> On the Linux box, all fresh compilations aside from the sasl
>> 2.1.15 binaries:
>> imapd 2.3.7 + sasl 2.1.15: works
>> imapd 2.3.7 + sasl 2.1.22: works
>> imapd 2.3.9 + sasl 2.1.15: not tried
>> imapd 2.3.9 + sasl 2.1.22: wor
Ian G Batten wrote:
>
> On the Linux box, all fresh compilations aside from the sasl 2.1.15
> binaries:
>
> imapd 2.3.7 + sasl 2.1.15: works
> imapd 2.3.7 + sasl 2.1.22: works
> imapd 2.3.9 + sasl 2.1.15: not tried
> imapd 2.3.9 + sasl 2.1.22: works
> imapd 2.3.10 + sasl 2.1.15: fails (cannot ex
Sorry - that was a typo in the command. I did ascertain that I should've
been using a username not a mailbox name and changed the command
accordingly, as you can see in the logs below.
I'm not sure how to apply this information about the unix hierarchy
separator? Is this in reference to the copyi
On 25 Oct 07, at 1248, Ken Murchison wrote:
> What does imapd.conf look like?
>
> Does the output of 'ctl_mboxlist -d' look reasonable?
>
> Does 'mbexamine user.igb' look reasonable?
OK, there's a steady stream of imapd processes being forked and then
dying on SIGSEGV. I've caught one in the
On the Linux box, all fresh compilations aside from the sasl 2.1.15
binaries:
imapd 2.3.7 + sasl 2.1.15: works
imapd 2.3.7 + sasl 2.1.22: works
imapd 2.3.9 + sasl 2.1.15: not tried
imapd 2.3.9 + sasl 2.1.22: works
imapd 2.3.10 + sasl 2.1.15: fails (cannot examine mailboxes, then
coredumps pri
I have an ipurge event in my cyrus.conf that doesn't appear to be
running. I had moved it from a cron job (which worked) to a cyrus
event.
purgejunk cmd="ipurge -f -d 15 'user/*/Junk Mail'" at=1700
The cyrus.conf man page didn't help me much as far as if the first
word can be anything. On
On 10/25/07, Ian G Batten <[EMAIL PROTECTED]> wrote:
>
>
> I've just compiled 2.3.10 on batten.eu.org (my private x86 servers)
> and although it looks OK on the Solaris 10 system, it's in deep
> trouble on the elderly Linux machine. Both are upgrades from 2.3.7,
> the Solaris box is a replication
Edward Prendergast wrote:
> Hi,
>
> I've given up on cyrus-murder for now and am just focusing on replication.
>
> When I run /usr/lib/cyrus-imapd/sync_client -v -l -u [EMAIL PROTECTED]
> it errors on the master:
-u takes usernames, not mailbox names. Try -u [EMAIL PROTECTED]
Also note that b
On 25 Oct 07, at 1248, Ken Murchison wrote:
> What does imapd.conf look like?
See second mail.
>
> Does the output of 'ctl_mboxlist -d' look reasonable?
Yes.
ctl_mboxlist -d > /tmp/foo
ctl_mboxlist -u < /tmp/foo
ctl_mboxlist -d | diff -c - /tmp/foo
comes up clean, too.
>
> Does 'mbexamine
>> idled_shutdown_check: 0
>
> Are you applying third-party patches? 'idled_shutdown_check' isn't
> a valid option in the stock distro.
No: the config dates back to the dawn of time, but the installation
today is a straight download and compile.
ian
Cyrus Home Page: http://cyrusimap.w
Ian G Batten wrote:
>
>
> On 25 Oct 07, at 1248, Ken Murchison wrote:
>
>> What does imapd.conf look like?
>
> See second mail.
>
>> Does the output of 'ctl_mboxlist -d' look reasonable?
>
> Yes.
>
> ctl_mboxlist -d > /tmp/foo
> ctl_mboxlist -u < /tmp/foo
> ctl_mboxlist -d | diff -c - /tmp/f
Hi,
I have questions regarding murder scalability. Untill last week we had
one imap server with about 5 users and 2TB mailboxes. Server was
overloaded and little slow but there was no troubles like connections
drop and repeatedly asking users for password.
Now we have that old server and th
Ian G Batten wrote:
>
> On 25 Oct 07, at 1230, Ian G Batten wrote:
>
>>
>>
>> I've just compiled 2.3.10 on batten.eu.org (my private x86 servers)
>> and although it looks OK on the Solaris 10 system, it's in deep
>> trouble on the elderly Linux machine. Both are upgrades from 2.3.7,
>> the So
Ian G Batten wrote:
>
> On 25 Oct 07, at 1248, Ken Murchison wrote:
>
>> What does imapd.conf look like?
>>
>> Does the output of 'ctl_mboxlist -d' look reasonable?
>>
>> Does 'mbexamine user.igb' look reasonable?
>
> OK, there's a steady stream of imapd processes being forked and then
> dying
What does imapd.conf look like?
Does the output of 'ctl_mboxlist -d' look reasonable?
Does 'mbexamine user.igb' look reasonable?
Ian G Batten wrote:
>
>
> I've just compiled 2.3.10 on batten.eu.org (my private x86 servers) and
> although it looks OK on the Solaris 10 system, it's in deep tro
On 25 Oct 07, at 1230, Ian G Batten wrote:
>
>
> I've just compiled 2.3.10 on batten.eu.org (my private x86 servers)
> and although it looks OK on the Solaris 10 system, it's in deep
> trouble on the elderly Linux machine. Both are upgrades from
> 2.3.7, the Solaris box is a replication ta
Hi,
I've given up on cyrus-murder for now and am just focusing on replication.
When I run /usr/lib/cyrus-imapd/sync_client -v -l -u [EMAIL PROTECTED]
it errors on the master:
Oct 25 13:52:29 chrisnux sync_client[10651]: USER received NO response:
IMAP_MAILBOX_NONEXISTENT Failed to access inbox
I've just compiled 2.3.10 on batten.eu.org (my private x86 servers)
and although it looks OK on the Solaris 10 system, it's in deep
trouble on the elderly Linux machine. Both are upgrades from 2.3.7,
the Solaris box is a replication target, the Linux box is a
replication master that hand
Indeed, I add allowplaintext: yes and works fine!
Thank you all for your answers!
Simon Matter wrote:
Hello list!
After fedora update cyrus users and also root cannot login to cyrus.
I recieve the message:
Login disabled.
cyradm: cannot authenticate to server with as root
can somebody help m
Nikos Gatsis wrote:
> Hello list!
> After fedora update cyrus users and also root cannot login to cyrus.
> I recieve the message:
>
> Login disabled.
> cyradm: cannot authenticate to server with as root
>
> can somebody help me?
>
> the last version is cyrus-imapd-2.3.9-7.fc7
See the release n
Dear List,
I have got the following error while compiling CyrusIMAP 2.3.1 on my
Centos server. I had patched Autocreate patch for this setup.
--
> Hello list!
> After fedora update cyrus users and also root cannot login to cyrus.
> I recieve the message:
>
> Login disabled.
> cyradm: cannot authenticate to server with as root
>
> can somebody help me?
>
> the last version is cyrus-imapd-2.3.9-7.fc7
Maybe you need this in imapd.conf:
allow
Hello Torsten!
Thank you for your answer!
I add the following lines in imapd.conf and worked!
allowanonymouslogin: no
allowplaintext: yes
The mystery is that these cyrus server was working for over a month
without problem.
After updating some rpms including cyrus imapd appear this problem!
Dear Nikos!
Some details about your setup would be helpful. against what do you
authenticate your users? /etc/passwd, LDAP, ...
Did you make sure you got some SASL mechs in /usr/lib/sasl2? This is a common
pitfall in Debian Linux. Installing lib-sasl2 does not mean that you installed
any mecha
Hello list!
After fedora update cyrus users and also root cannot login to cyrus.
I recieve the message:
Login disabled.
cyradm: cannot authenticate to server with as root
can somebody help me?
the last version is cyrus-imapd-2.3.9-7.fc7
Thank you
Cyrus Home Page: http://cyrusimap.web.cm
46 matches
Mail list logo