On 10/13/2011 01:46 AM, Bron Gondwana wrote:
> On Thu, Oct 13, 2011 at 07:00:42AM +0530, Ramprasad wrote:
>> On 10/13/2011 6:39 AM, Adam Tauno Williams wrote:
>>> On Thu, 2011-10-13 at 05:33 +0530, Ramprasad wrote:
I just upgraded cyrus on a busy Imap server from 2.3.x to 2.4.6 ,
problem
On Thu, Oct 13, 2011 at 07:46:17AM +0200, Bron Gondwana wrote:
> On Thu, Oct 13, 2011 at 07:00:42AM +0530, Ramprasad wrote:
> > On 10/13/2011 6:39 AM, Adam Tauno Williams wrote:
> > > On Thu, 2011-10-13 at 05:33 +0530, Ramprasad wrote:
> > >> I just upgraded cyrus on a busy Imap server from 2.3.x t
On Thu, Oct 13, 2011 at 07:00:42AM +0530, Ramprasad wrote:
> On 10/13/2011 6:39 AM, Adam Tauno Williams wrote:
> > On Thu, 2011-10-13 at 05:33 +0530, Ramprasad wrote:
> >> I just upgraded cyrus on a busy Imap server from 2.3.x to 2.4.6 ,
> >> problem is with lmtp delivery.
> >> All lmtp deliveries
On 10/13/2011 6:39 AM, Adam Tauno Williams wrote:
> On Thu, 2011-10-13 at 05:33 +0530, Ramprasad wrote:
>> I just upgraded cyrus on a busy Imap server from 2.3.x to 2.4.6 ,
>> problem is with lmtp delivery.
>> All lmtp deliveries from postfix are hanging forever.
>> I think this is due to the "Inde
On Thu, 2011-10-13 at 05:33 +0530, Ramprasad wrote:
> I just upgraded cyrus on a busy Imap server from 2.3.x to 2.4.6 ,
> problem is with lmtp delivery.
> All lmtp deliveries from postfix are hanging forever.
> I think this is due to the "Index upgrade" that is going on .. Is there
> a way I can
I just upgraded cyrus on a busy Imap server from 2.3.x to 2.4.6 ,
problem is with lmtp delivery.
All lmtp deliveries from postfix are hanging forever.
I think this is due to the "Index upgrade" that is going on .. Is there
a way I can speed up the index upgrade
I have 2000 users and only 200 us
Hi!
Until today I used massievec to create all sievescripts on my old cyrus
debian install.
But today I got this error:
can't open /etc/imapd.co at /usr/lib/cyrus/upgrade/masssievec line 80
Anyonehave a idea about it?
cyrus: 2.2.13-10
MfG,
Lars Sch
On Fri, Jan 28, 2011 at 07:58:44AM +0100, Martin Schweizer wrote:
> Hello Bron
>
> Sorry for the delay.
> Today I ckecked my logs again and there were no more sync errors. Very
> strange. So I assume all is ok now. Why ever...
> Thanks for support.
No worries! Glad it fixed up :) We do see the
Hello Bron
Sorry for the delay.
Today I ckecked my logs again and there were no more sync errors. Very
strange. So I assume all is ok now. Why ever...
Thanks for support.
Regards,
2011/1/27 Bron Gondwana :
> That all looks fine. Are you able to capture telemetry data?
>
> Did you read the outp
That all looks fine. Are you able to capture telemetry data?
Did you read the output of the reconstruct? Did it say anything about
GUID errors at any point? That's the one thing that -G by itself can't
fix - you need to make a decision to keep or delete the message (because
GUID errors mean file
Hello Patrick
2011/1/26 Patrick Boutilier :
> On 01/26/2011 06:12 AM, Patrick Boutilier wrote:
>> On 01/26/2011 04:34 AM, Martin Schweizer wrote:
>>> Hello
>>>
>>> I upgraded both server (master and client). After restart the sync I
>>> get a lot of messages like them (on different mailboxes):
>>>
Sorry I forgot the relevant part of mailbox.db:
user.mdemonaco 0 default mdemonaco lrswipkxtecda
user.mdemonaco.Drafts 0 default mdemonaco lrswipkxtecda
user.mdemonaco.Sent 0 default mdemonaco lrswipkxtecda
user.mdemonaco.Trash0 default mdemonaco lrswipkxtecda
2011/1/2
On 01/26/2011 06:12 AM, Patrick Boutilier wrote:
> On 01/26/2011 04:34 AM, Martin Schweizer wrote:
>> Hello
>>
>> I upgraded both server (master and client). After restart the sync I
>> get a lot of messages like them (on different mailboxes):
>>
>> (sync_client)
>> Jan 26 09:15:01 acsvfbsd06 sync_
On 01/26/2011 04:34 AM, Martin Schweizer wrote:
> Hello
>
> I upgraded both server (master and client). After restart the sync I
> get a lot of messages like them (on different mailboxes):
>
> (sync_client)
> Jan 26 09:15:01 acsvfbsd06 sync_client[56473]: MAILBOX received NO
> response: System I/O
Hello
I upgraded both server (master and client). After restart the sync I
get a lot of messages like them (on different mailboxes):
(sync_client)
Jan 26 09:15:01 acsvfbsd06 sync_client[56473]: MAILBOX received NO
response: System I/O error
Jan 26 09:15:01 acsvfbsd06 sync_client[56473]: do_folder
> Steinar Bang <[EMAIL PROTECTED]>:
> S... I'll bite the bullet like I did the other times and
> reconstruct the .seen marks, as near as I can. Come tuesday my email
> server has been out of service for a week.
Small postscript: turns out that it wasn't all folders that had their
.seen d
gt;> What previously was mail/s/user/sb/ is now mail/u/s/user/sb/
>
> Here's what I think happened.
>
> I've had this setting since upgrading from 1.5.19 to 2.1.11 in 2002:
>
> > hashimapspool: true
>
>
> Ie. it's not new.
>
> So when I ra
Final words on the upgrade: Moving the mailboxes in the
/var/spool/mail/ gave something that couldn't be opened.
Running
/usr/sbin/cyrreconstruct -r user.*
on /var/spool/mail/ gave me openable mailboxes, but the read marks were
gone (probably the .seen databases took an early beating in t
t;>>> What previously was mail/s/user/sb/ is now mail/u/s/user/sb/
>
> Here's what I think happened.
>
> I've had this setting since upgrading from 1.5.19 to 2.1.11 in 2002:
>
> > hashimapspool: true
>
>
> Ie. it's not new.
>
> So when I r
k happened.
I've had this setting since upgrading from 1.5.19 to 2.1.11 in 2002:
> hashimapspool: true
Ie. it's not new.
So when I ran this command meant for an upgrade from 1.5.* to 2.* things
where messed up:
> $ /usr/lib/cyrus/upgrade/rehash basic
The rehash script expected
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
>>>>> Sebastian Hagedorn <[EMAIL PROTECTED]>:
>> -- Steinar Bang <[EMAIL PROTECTED]> is rumored to have mumbled on 28.
>> November
>> 2007 20:55:16 +0100 regarding Cyrus upgrade from 2.1.18
>>>>> Sebastian Hagedorn <[EMAIL PROTECTED]>:
> -- Steinar Bang <[EMAIL PROTECTED]> is rumored to have mumbled on 28. November
> 2007 20:55:16 +0100 regarding Cyrus upgrade from 2.1.18 to 2.2.13
> moved email messages:
>> What previously was mail/s/user/
> "Alain Spineux" <[EMAIL PROTECTED]>:
> You would have won some time if you had read one of my previous post
> in another thread about pitfall you can meet when migrating. The
> thread title is "Migration 32 to 64 bit". It could still help you to
> understand what you did :-)
Thanx, I'll st
You would have won some time if you had read one of my previous post
in another thread
about pitfall you can meet when migrating. The thread title is
"Migration 32 to 64 bit".
It could still help you to understand what you did :-)
Be aware that we are not all debian user, and dont know the script
-- Steinar Bang <[EMAIL PROTECTED]> is rumored to have mumbled on 28. November 2007
20:55:16 +0100 regarding Cyrus upgrade from 2.1.18 to 2.2.13 moved email
messages:
What previously was mail/s/user/sb/ is now mail/u/s/user/sb/
That means you are using fulldirhash. It's an opt
> Steinar Bang <[EMAIL PROTECTED]>:
[snip]
> And as far as I can tell it lists ranges and unread and so forth. But
> when I try to open the folders I'm told that there are no messages in
> them.
> Hot damn! The mailboxes actually _are_ empty!
In the words of James Bond: "That explains the
Hi,
I am trying to upgrade our mail server from redhat 9 running cyrus-imapd
2.2.8 to RHEL4 running the stock 2.2.12 rpms. I am trying to make sure I am
not missing anything. All the db files seem to be in the correct format as
far as I can tell. Does anyone see problems with the following:
1)
On Mon, 2006-08-14 at 07:27 -0400, Scott Russell wrote:
> 2) Use ctl_mailbox to dump flatfile version of your mailbox.db file.
> This is critical. Keep a copy of it somewhere else. It is small. Put it
> on a USB thumb drive if you have to or just mail it to your home account.
Doing a flat-file
Sun Advocate Webmaster wrote:
I don't use sieve, and I haven't set up any sort of 'murder'
environment (which I am largely unfamiliar with). I don't know a lot
about Berkeley DB, other than it is an offline sort of database (it
isn't a server, but a data storage engine, for lack of better words
Wil Cooley wrote:
On Sat, 2006-08-12 at 04:27 -0700, Nikola Milutinovic wrote:
Watch out for Berkeley DB versions. Most likely, they will differ and
all Cyrus SASL/IMAP DBs that use Berkeley will not be transferrable,
just like that. There are things you can do. :-)
I do not know what
On Sat, 2006-08-12 at 04:27 -0700, Nikola Milutinovic wrote:
> Watch out for Berkeley DB versions. Most likely, they will differ and
> all Cyrus SASL/IMAP DBs that use Berkeley will not be transferrable,
> just like that. There are things you can do. :-)
I do not know what, if any, changes SUSE m
Watch out for Berkeley DB versions. Most likely, they will differ and all Cyrus
SASL/IMAP DBs that use Berkeley will not be transferrable, just like that.
There are things you can do. :-)
First of all, you should export your mailboxes DB using "ctl_mailbox" command.
Next, you should backup the
Hi all,
I am preparing to upgrade our production server's operating system,
which will also entail replacing Cyrus and SASL with newer, updated
versions. I don't have the luxury of installing the upgrades on a new
machine and then swapping it with the old one. Rather, I have to
reinstall the opera
I think I fixed my issue. There seems to be an issue with using
"saslauthd -a pam" on Solaris (I'm using Solaris 9). I have PAM
configured to use LDAP on the back-end for authentication. I downloaded
OpenLDAP and linked SASL against it and am using "saslauthd -a ldap" now
and haven't seen th
I upgrade from Cyrus 2.0.16 to Cyrus 2.2.5 this past weekend. I also
upgrade Postfix from 1.x to 2.1.1. After running for a little while, I
get the error messages below. If I run a "postfix flush", the message
usually get delivered fine. I've seen some talk on the list about
System I/O erro
On Mon, 9 Jun 2003, Paul Boven wrote:
> I've been running cyrus imapd version 2.1.10 with cyrus-sasl-2.1.9 for a
> while, and apart
> of some glitches with Berkely-dB 4.1.25, am quite pleased with it. From
> this mailinglist I
> understand that the Berkeley-dB bug has been solved, so that sounds l
Paul Boven wrote:
Secondly, most of my mail-users use Mozilla or Outlook. Both open
multiple connections,
and because of this, mail you've already read tends to become unread
again. I've heard about
a patch to make cyrus write these changes to disk right away to keep
them synchronized
between conn
L.S.,
I've been running cyrus imapd version 2.1.10 with cyrus-sasl-2.1.9 for a
while, and apart
of some glitches with Berkely-dB 4.1.25, am quite pleased with it. From
this mailinglist I
understand that the Berkeley-dB bug has been solved, so that sounds like
a good reason
to upgrade. Is this part
Hello ,
I am currently running the following version of Cyrus & co , ... which
components should I upgrade and to which version if I want to upgrade to
the latest cyrus version ?
cyradm> ver
name : Cyrus
version: v2.0.16
vendor : Project Cyrus
support-url: http://asg.web.cmu.edu
--On Monday, November 20, 2000 10:20:18 AM -0700 Tim Pushor
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> I just upgraded Cyrus IMAP 1.5.x to 1.6.22 on a small server with only a
> few dozen users. The only problem I am currently having is that folder
> subscriptions are kept inside a directory name
From: "Tim Pushor" <[EMAIL PROTECTED]>
> I just upgraded Cyrus IMAP 1.5.x to 1.6.22 on a small server with only a
few
> dozen users. The only problem I am currently having is that folder
> subscriptions are kept inside a directory named the first letter of the
> username. This directory is not aut
Hello,
I just upgraded Cyrus IMAP 1.5.x to 1.6.22 on a small server with only a few
dozen users. The only problem I am currently having is that folder
subscriptions are kept inside a directory named the first letter of the
username. This directory is not automatically created with cyradm. IMAP
su
42 matches
Mail list logo
