Cyrus IMAP 3.0.1 released

2017-04-19 Thread ellie timoney
The Cyrus team is proud to announce the immediate availability of a new
version of Cyrus IMAP: 3.0.1

This is a bug fix release for the 3.0 series.

Download URLs:

http://www.cyrusimap.org/releases/cyrus-imapd-3.0.1.tar.gz
http://www.cyrusimap.org/releases/cyrus-imapd-3.0.1.tar.gz.sig

ftp://ftp.cyrusimap.org/cyrus-imapd/cyrus-imapd-3.0.1.tar.gz
ftp://ftp.cyrusimap.org/cyrus-imapd/cyrus-imapd-3.0.1.tar.gz.sig

Please consult the release notes and upgrade documentation before
upgrading to 3.0.1:

http://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.1.html
http://www.cyrusimap.org/imap/download/upgrade.html

And join us on Github at https://github.com/cyrusimap/cyrus-imapd to
report issues, join in the deliberations of new features for the next
Cyrus IMAP release, and to contribute to the documentation.

On behalf of the Cyrus team,

Kind regards,

ellie timoney

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus


Re: IMAP.c: loadable library and perl binaries are mismatched

2017-04-19 Thread Patrick Boutilier

On 04/19/2017 01:14 PM, Patrick Goetz wrote:
Correction:  just realized I'm running 2.5.7, not 2.4.17.  Probably just 
need to upgrade, but am still interested in knowing if there is any way 
to get around using cyradm for adding users.



We use this perl module with a very simple perl script to add users.

http://search.cpan.org/~eestabroo/IMAP-Admin-1.6.4/Admin.pm






On 04/19/2017 11:12 AM, Patrick Goetz wrote:

I'm running cyrus 2.4.17 on a couple of Arch linux servers, and Arch is
an aggressively updated rolling release distro.

I don't have to add new users very often, but ran cyradm today and got
the following error message:

[root@www sbin]# cyradm --user administrator localhost
IMAP.c: loadable library and perl binaries are mismatched (got handshake
key 0xdb00080, needed 0xdb80080)


I'm hoping to not have to upgrade cyrus at this precise moment.  Is
there any way to get around this for adding a new cyrus user?  I've only
ever used cyradm for this task.

If I do have to upgrade, the cyrus version in the Arch AUR is still at
2.5.10 -- presumably this upgrade won't break anything?  Do I need to
upgrade to 2.5.x before upgrading to 3.0?

Thanks.


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus



Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus


<>
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: IMAP.c: loadable library and perl binaries are mismatched

2017-04-19 Thread Patrick Goetz
Correction:  just realized I'm running 2.5.7, not 2.4.17.  Probably just 
need to upgrade, but am still interested in knowing if there is any way 
to get around using cyradm for adding users.


On 04/19/2017 11:12 AM, Patrick Goetz wrote:

I'm running cyrus 2.4.17 on a couple of Arch linux servers, and Arch is
an aggressively updated rolling release distro.

I don't have to add new users very often, but ran cyradm today and got
the following error message:

[root@www sbin]# cyradm --user administrator localhost
IMAP.c: loadable library and perl binaries are mismatched (got handshake
key 0xdb00080, needed 0xdb80080)


I'm hoping to not have to upgrade cyrus at this precise moment.  Is
there any way to get around this for adding a new cyrus user?  I've only
ever used cyradm for this task.

If I do have to upgrade, the cyrus version in the Arch AUR is still at
2.5.10 -- presumably this upgrade won't break anything?  Do I need to
upgrade to 2.5.x before upgrading to 3.0?

Thanks.


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus



Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus


IMAP.c: loadable library and perl binaries are mismatched

2017-04-19 Thread Patrick Goetz
I'm running cyrus 2.4.17 on a couple of Arch linux servers, and Arch is 
an aggressively updated rolling release distro.


I don't have to add new users very often, but ran cyradm today and got 
the following error message:


[root@www sbin]# cyradm --user administrator localhost
IMAP.c: loadable library and perl binaries are mismatched (got handshake 
key 0xdb00080, needed 0xdb80080)



I'm hoping to not have to upgrade cyrus at this precise moment.  Is 
there any way to get around this for adding a new cyrus user?  I've only 
ever used cyradm for this task.


If I do have to upgrade, the cyrus version in the Arch AUR is still at 
2.5.10 -- presumably this upgrade won't break anything?  Do I need to 
upgrade to 2.5.x before upgrading to 3.0?


Thanks.


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus


Re: Error: same message appears twice

2017-04-19 Thread Robert Stepanek
On Wed, Apr 19, 2017, at 10:51, Frederik Himpe wrote:
> Sometimes I see in the logs messages like this: "same message appears 
> twice 2394 2395". Looking at the source code, it does not appear to be
> a big problem, but I am not sure. Does this indicate a real problem?
> Should I run cyrreconstruct on the affected mailbox, and which options
> do you recommend?

When a new message is appended to a mailbox, Cyrus checks if the hash
(SHA1) of the message content matches the latest stored message in this
mailbox. This log message is printed when the hashes match. Since you
see this log message only sometimes, I wouldn't think it's a problem. It
indicates that some client might call APPEND for the same message twice
or more often, though.

I can't imagine that cyrreconstruct will make a difference, except if
your mailbox index is broken. 

Cheers,
Robert

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Error: same message appears twice

2017-04-19 Thread Frederik Himpe
Sometimes I see in the logs messages like this: "same message appears 
twice 2394 2395". Looking at the source code, it does not appear to be
a big problem, but I am not sure. Does this indicate a real problem?
Should I run cyrreconstruct on the affected mailbox, and which options
do you recommend?

-- 
Frederik Himpe


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus