cyrus 2.3.14 on opensuse 11.1 x64 and lmtp errors

2010-09-27 Thread Josef Karliak 

  Hi guys,
  when I got email looked like this:

Received: (qmail 10428 invoked by uid 30); 27 Sep 2010 08:17:11 -
Date: 27 Sep 2010 08:17:11 -
Message-ID: <20100927081711.10427.qm...@mx2fnhk.lfhk.cuni.cz>
To: karl...@ajetaci.cz
Subject: =?utf-8?B?Tm92w6kgaGVzbG8gayDDusSNdHU=?=
From: =?utf-8?B?d3d3LmhlcGluLmN6?= 
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-VBSHLD-SCLID: A10727E914A


VmHFoWUgbm92w6kgaGVzbG8gayDDusSNdHUgImZyYW50acWhZWsiIGplOiBUa0RnckcK

  cyrus lmtp reject email with error:
.. [public/lmtp] said: 554 5.6.0 Message contains invalid header  
(in reply to end of DATA command)



  What is going on ? On cyrus 2.2.12 is all ok. When subject don't  
contain "=?utf-8?B?Tm9" (I rewrote it to "test subject" for example),  
email is delivered.


  Imapd.conf contains:

reject8bit: no
rfc_ignore_8bit: yes
munge_8bit: no



  Any tips or kicking me to the right way ? :)
  Thanks.
  J.Karliak.


This message was sent using IMP, the Internet Messaging Program.



bin82aPzScetH.bin
Description: Veřejný PGP	klíč

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

Re: cyrus and DBERROR complains.

2010-09-27 Thread Adam Tauno Williams 
On Sun, 2010-09-26 at 14:11 +0200, Josef Karliak wrote:
> Hi guys,
>on SLES 10 x64bit I see following complains in the syslog:
> Sep 26 12:44:36 email1 master[3805]: about to exec /usr/lib/cyrus/bin/lmtpd
> Sep 26 12:44:36 email1 lmtpunix[3805]: executed
> Sep 26 12:44:36 email1 lmtpunix[3805]: DBERROR db4: Logging region out  
> of memory; you may need to increase its size
> Sep 26 12:44:36 email1 lmtpunix[3805]: DBERROR: opening  
> /var/spool/imap/config/deliver.db: Cannot allocate memory
> Sep 26 12:44:36 email1 lmtpunix[3805]: DBERROR: opening  
> /var/spool/imap/config/deliver.db: cyrusdb error
> Sep 26 12:44:36 email1 lmtpunix[3805]: FATAL: lmtpd: unable to init  
> duplicate delivery database

Duplicate delivery database errors, I believe, are not fatal; the
message should still be delivered.

>"/var/lib/ldap/DB_CONFIG" contains:
> set_cachesize 0 1500 1
> set_lg_regionmax 262144
> set_lg_bsize 2097152
> set_flags DB_LOG_AUTOREMOVE
>But we do not use ldap, where is a right config for it ? Could you  
> kick me to the right way ? :)

??? That has nothing to do with the above.  The delivery database is
probably someplace like /var/lib/imap/deliverydb.  

The simplest solution is to not use BDB; set "duplicate_db" to
"skiplist" in /etc/imapd.conf

BDB is rarely, IMO, worth the headache.
-- 
Adam Tauno Williams  LPIC-1, Novell CLA

OpenGroupware, Cyrus IMAPd, Postfix, OpenLDAP, Samba


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

Re: competition

2010-09-27 Thread Adam Tauno Williams 
On Wed, 2010-09-22 at 18:18 +0200, Jeroen van Meeuwen (Kolab Systems)
wrote:
> >> Kolab Systems is thinking of such SQL databases for integration purposes,
> > > where the performance penalty now lies within having to use the IMAP
> > > protocol to gain access to the underlying metadata (seen status, message
> > > indexes) in distributed groupware environments where Cyrus itself is not
> > > the only component that needs access to such information (but would still
> > > remain authoritative, of course, and would be the only component with 
> >write
> > > access to most tables).
> >> While not necessarily the best approach, it seems worth exploring.
> >What makes you think the query parsing and other overheads of SQL will 
> >be faster than IMAP?
> >I'd be interested in any numbers that you might have to support the effort.
>  The scenario is integration, not extension of Cyrus -which in and of itself 
> works 
> perfecly fine and reliable for us. We're not seeking to improve Cyrus'
> performance with *SQL db backends.

But, this assumes the data that Cyrus stores in that DB would be useful
outside the context of the Cyrus' processes.  I've lightly played with
the idea, and not gone any further - the data available isn't really
very useful.

> Imagine the following scenario; a client polls 3rd party application for a 
> list of
> mailboxes and the content's status very regularly -basically what it's 
> interested 
> in knowing is whether anything changed.

Doesn't condstore solve this issue inexpensively?  [maybe I
misunderstand condstore].  I thought it was equivalent to WebDAV/CalDAV
ctags (which are mightily nice).

> Each 3rd party app will seek to cache the 
> results somehow, for improved performance interacting with its clients and as 
> to not continuously put load on the Cyrus server.

Which is what WebDAV/CalDAV ctags are for.


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

Cyrus 2.4 release will be slightly delayed

2010-09-27 Thread Dave McMurtrie 
Good morning,

We're trying to add as much of Bron's recent rewrites as possible into 
the Cyrus 2.4 release, and at the same time make sure we put out a 
stable, quality release.

As such, we're running up against our initial 9/30 deadline and we'd 
like to put a little bit more time into testing what we're planning to 
roll out as Cyrus 2.4.  We're going to extend our release date out to 
10/11/2010.

If you missed the e-mail that Rob Mueller sent out earlier, you can read 
about the changes that will be going into this release at:

http://www.cyrusimap.org/mediawiki/index.php/Cyrus_2.4_Changes

Thanks,

Dave
-- 
Dave McMurtrie, SPE
Email Systems Team Leader
Carnegie Mellon University,
Computing Services

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

Re: competition

2010-09-27 Thread Jeff Eaton 

> Better to just use an internal DB codebase (like skiplists) that has
> nothing to do with Sleepycat.  But then someone has to write and maintain
> this code.
>
> I think the best compromise I've heard yet is to use something like
> skiplists by default and make the use of libdb an optional feature like the
> use of mysql.

I'd be in favor of "deprecating" the use of BerkeleyDB in Cyrus.  Making
at least the default for new installations to be all-skiplist would be a
good step in that direction, as well as encouraging people to move away
from BDB where possible.

Ideally, I'd suggest making the default behavior of "./configure; make;
make install" to _not_ link in BDB at all unless --with-bdb is explicitly
given.  As I recall, you have to jump through a few hoops to get a build
of Cyrus to not link in the BDB libraries, even if you're not using them.

All of that said, it's probably worth directing future Cyrus DB backend
work away from BDB and more to improving SQLite or other integration.

-jeaton


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

Re: cyrus 2.3.14 on opensuse 11.1 x64 and lmtp errors

2010-09-27 Thread Patrick Goetz 
On 09/27/2010 05:39 AM, Josef Karliak wrote:
>
>
> What is going on ? On cyrus 2.2.12 is all ok. When subject don't contain
> "=?utf-8?B?Tm9" (I rewrote it to "test subject" for example), email is
> delivered.
>

It sounds like your email header contains 8-bit letters.  This is a 
violation of RFC2882, which says that ASCII-only (7-bit).  You can 
configure /etc/imapd.conf to accept messages like this by setting
   reject8bit: no

but this is not recommended and will likely subject you to more spam.


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

How to migrate away from BDB

2010-09-27 Thread J. Roeleveld 
Hi All,

Following the discussion about DB-backends for Cyrus (See thread 
"competition") I was wondering what the best way is to move away from using 
BDB and start using something else (like "skiplist")

I wasn't able to find a specific howto for this during a brief Google-search.

Many thanks,

Joost

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

Re: How to migrate away from BDB

2010-09-27 Thread Mark Nipper 
On 27 Sep 2010, J. Roeleveld wrote:
> I wasn't able to find a specific howto for this during a brief Google-search.

I recalled that the Debian package for Cyrus had some
decent instructions on this.  You can see them at:
---
https://mail.incase.de/svn/cyrus22/trunk/cyrus-imapd-2.2.13/debian/README.Debian.database

That will get you started.  I have this at the bottom of
my imapd.conf:
---
# bypass BDB hell
annotation_db: skiplist
duplicate_db: skiplist
mboxlist_db: skiplist
ptscache_db: skiplist
quota_db: skiplist
seenstate_db: skiplist
subscription_db: skiplist
tlscache_db: skiplist
---

So those were all of the different databases I converted
to skiplist to avoid any potential problems.

-- 
Mark Nipper
ni...@bitgnome.net (XMPP)
+1 979 575 3193
-
He hoped and prayed that there wasn't an afterlife. Then he
realized there was a contradiction involved here and merely
hoped that there wasn't an afterlife.
 -- Douglas Adams

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

high-availability Cyrus (i.e. glusterfs)?

2010-09-27 Thread Tomasz Chmielewski 
How do you manage your Cyrus installations highly-available?

I though a minimal example could be like below:


   internet
  |
server1 - server2


There would be Heartbeat/Pacemaker running on both servers. Its role would be:

- assign "Cyrus IP" to a given server,
- start Cyrus where "Cyrus IP" is up.


Still, we need to have Cyrus database, mail storage accessible for both 
servers. I though using glusterfs for it would be a good idea (assuming Cyrus 
only runs on one of the servers at a given time).

However, something doesn't work with it very well when Cyrus data is on a 
glusterfs mount point (if I move it to a local disk, everything works well):

Sep 28 01:10:10 omega cyrus/master[21504]: ready for work
Sep 28 01:10:10 omega cyrus/master[21728]: about to exec /usr/sbin/ctl_cyrusdb
Sep 28 01:10:10 omega cyrus/master[21729]: about to exec 
/usr/lib/cyrus/bin/notifyd
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR db4: Program version 
4.2 doesn't match environment version
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: dbenv->open 
'/shared/var/lib/cyrus/db' failed: Invalid argument
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: init() on berkeley
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: checkpointing cyrus databases
Sep 28 01:10:10 omega cyrus/notify[21729]: DBERROR db4: Program version 4.2 
doesn't match environment version
Sep 28 01:10:10 omega cyrus/notify[21729]: DBERROR: dbenv->open 
'/shared/var/lib/cyrus/db' failed: Invalid argument
Sep 28 01:10:10 omega cyrus/notify[21729]: DBERROR: init() on berkeley
Sep 28 01:10:10 omega cyrus/notify[21729]: executed
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: archiving database file: 
/shared/var/lib/cyrus/annotations.db
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR db4: txn_checkpoint 
interface requires an environment configured for the transaction subsystem
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: couldn't checkpoint: 
Invalid argument
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: sync 
/shared/var/lib/cyrus/db: cyrusdb error
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR db4: 
DB_ENV->log_archive interface requires an environment configured for the 
logging subsystem
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: error listing log 
files: Invalid argument
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: archive 
/shared/var/lib/cyrus/db: cyrusdb error
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: archiving database file: 
/shared/var/lib/cyrus/mailboxes.db
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR db4: txn_checkpoint 
interface requires an environment configured for the transaction subsystem
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: couldn't checkpoint: 
Invalid argument
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: sync 
/shared/var/lib/cyrus/db: cyrusdb error
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR db4: 
DB_ENV->log_archive interface requires an environment configured for the 
logging subsystem
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: error listing log 
files: Invalid argument
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: archive 
/shared/var/lib/cyrus/db: cyrusdb error
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR db4: txn_checkpoint 
interface requires an environment configured for the transaction subsystem
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: couldn't checkpoint: 
Invalid argument
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: sync 
/shared/var/lib/cyrus/db: cyrusdb error
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR db4: 
DB_ENV->log_archive interface requires an environment configured for the 
logging subsystem
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: error listing log 
files: Invalid argument
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR: archive 
/shared/var/lib/cyrus/db: cyrusdb error
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: done checkpointing cyrus 
databases



-- 
Tomasz Chmielewski
http://wpkg.org

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