Re: Reject large emails

2008-02-13 Thread Konrad Mauz
On Wed, Feb 13, 2008 at 12:27:11PM +0200, Nikos Gatsis wrote:
> Joseph thank you for your answer.
> We use sendmail. Do you know how to set up sendmail.mc to reject those 
> emails?
> Thank you

Hi Nikos,

ind sendmail.mc you can use

define(`confMAX_MESSAGE_SIZE',`10485760')dnl

to set the max message size to 10 MByte.

Regards,

Konrad

-- 
Konrad Mauz 
Rechenzentrum
Hochschule Technik, Wirtschaft und Gestaltung
Braunegger-Strasse 55, D 78462 Konstanz 
e-mail: [EMAIL PROTECTED]
Tel.:   +49 7531 206-472
Fax.:   +49 7531 206-153

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


Re: How to repair a broken seen state file

2008-07-07 Thread Konrad Mauz
On Mon, Jul 07, 2008 at 08:31:59AM -0500, Gary Mills wrote:
> I'm seeing errors like this regularly in our messages log:
> 
>   Jul  4 11:43:37 castor imap[16398]: [ID 514311 local6.error] DBERROR: 
> skiplist recovery: 058C should be INORDER
>   Jul  4 11:43:37 castor imap[16398]: [ID 729713 local6.error] DBERROR: 
> opening /imap/conf/user/O/inqarts.seen: cyrusdb error
> 
> It's always for this one file.  All the others are fine.  It's a
> skiplist database.  The ownership is correct.  A reconstruct on the
> mailbox has no effect on the file.  Can I just remove the file, with
> no ill effects?  Can I fix it somehow?  We're running cyrus-imapd-2.3.8.
> 
> -- 
> -Gary Mills--Unix Support--U of M Academic Computing and Networking-
> 
> 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

Hi Gary,

perheps the skiplist.py tool from

http://oss.netfarm.it/python-cyrus.php

can help you to restore the corrupted seen file.

Regards,

Konrad

-- 
Konrad Mauz 
Rechenzentrum
Hochschule Technik, Wirtschaft und Gestaltung
Braunegger-Strasse 55, D 78462 Konstanz 
e-mail: [EMAIL PROTECTED]
Tel.:   +49 7531 206-472
Fax.:   +49 7531 206-153

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


Cyrus IMAPd 2.3.15 - Fatal error: cyrusdb backend berkeley-nosync not supported

2009-09-10 Thread Konrad Mauz
Hi all,

I've tried to upgrade Cyrus from 2.3.8 to 2.3.15. 
I compiled 2.3.15 on the same machines with the same configure call:

./configure --prefix=/usr/cyrus --enable-nntp \
   --enable-murder --enable-replication \
   --enable-listext --enable-netscapehack --without-bdb

But wenn I tried to restart imapd and pop3d process generate a lot
of error messages like:

Sep 10 06:44:11 mailsrv master[10325]: service pop3 pid 11258 in READY state: 
terminated abnormally
Sep 10 06:44:11 mailsrv imap[11259]: Fatal error: cyrusdb backend 
berkeley-nosync not supported
Sep 10 06:44:11 mailsrv pop3[11260]: Fatal error: cyrusdb backend 
berkeley-nosync not supported
Sep 10 06:44:11 mailsrv lmtpunix[11261]: FATAL: cyrusdb backend berkeley-nosync 
not supported
Sep 10 06:44:11 mailsrv imap[11262]: Fatal error: cyrusdb backend 
berkeley-nosync not supported
Sep 10 06:44:11 mailsrv pop3[11263]: Fatal error: cyrusdb backend 
berkeley-nosync not supported
Sep 10 06:44:11 mailsrv master[10325]: service imap pid 11259 in READY state: 
terminated abnormally
Sep 10 06:44:11 mailsrv master[10325]: service pop3 pid 11260 in READY state: 
terminated abnormally
Sep 10 06:44:11 mailsrv master[10325]: service lmtpunix pid 11261 in READY 
state: terminated abnormally
Sep 10 06:44:11 mailsrv master[10325]: service imap pid 11262 in READY state: 
terminated abnormally
Sep 10 06:44:11 mailsrv master[10325]: service pop3 pid 11263 in READY state: 
terminated abnormally
Sep 10 06:44:11 mailsrv imap[11264]: Fatal error: cyrusdb backend 
berkeley-nosync not supported
Sep 10 06:44:11 mailsrv pop3[11265]: Fatal error: cyrusdb backend 
berkeley-nosync not supported

The relevant part in /etc/imapd.conf:

# DB Settings
mboxlist_db: skiplist
seenstate_db: skiplist
quota_db: skiplist
duplicate_db: skiplist
annotation_db: skiplist
ptscache_db: skiplist
subscription_db: flat
tlscache_db: skiplist

I can not find any reference to a berkley db, so I don't know why the daemons 
thow errors about
the missing berkeley support. The only to dbs which are berkeley-nosync by 
default are:
duplicate_db and tlscache_db, but I have them set to skiplist in my config.

Can anyone tell me, which db defaultsetting is berkeley-nosync and not 
overwritten in my imapd.conf?

Regards,

Konrad

PS: the old imapd binary are not linked with berkeley db - checked with ldd


-- 
Konrad Mauz 
Rechenzentrum
Hochschule Technik, Wirtschaft und Gestaltung
Braunegger-Strasse 55, D 78462 Konstanz 
e-mail: km...@htwg-konstanz.de
Tel.:   +49 7531 206-472
Fax.:   +49 7531 206-153

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


Re: Cyrus IMAPd 2.3.15 - Fatal error: cyrusdb backend berkeley-nosync not supported

2009-09-10 Thread Konrad Mauz
On Thu, Sep 10, 2009 at 09:10:57AM +0200, Konrad Mauz wrote:
> Hi all,
> 
> I've tried to upgrade Cyrus from 2.3.8 to 2.3.15. 
> I compiled 2.3.15 on the same machines with the same configure call:
> 
> ./configure --prefix=/usr/cyrus --enable-nntp \
>--enable-murder --enable-replication \
>--enable-listext --enable-netscapehack --without-bdb
> 
> But wenn I tried to restart imapd and pop3d process generate a lot
> of error messages like:
> 
> Sep 10 06:44:11 mailsrv master[10325]: service pop3 pid 11258 in READY state: 
> terminated abnormally
> Sep 10 06:44:11 mailsrv imap[11259]: Fatal error: cyrusdb backend 
> berkeley-nosync not supported
> Sep 10 06:44:11 mailsrv pop3[11260]: Fatal error: cyrusdb backend 
> berkeley-nosync not supported
> Sep 10 06:44:11 mailsrv lmtpunix[11261]: FATAL: cyrusdb backend 
> berkeley-nosync not supported
> Sep 10 06:44:11 mailsrv imap[11262]: Fatal error: cyrusdb backend 
> berkeley-nosync not supported
> Sep 10 06:44:11 mailsrv pop3[11263]: Fatal error: cyrusdb backend 
> berkeley-nosync not supported
> Sep 10 06:44:11 mailsrv master[10325]: service imap pid 11259 in READY state: 
> terminated abnormally
> Sep 10 06:44:11 mailsrv master[10325]: service pop3 pid 11260 in READY state: 
> terminated abnormally
> Sep 10 06:44:11 mailsrv master[10325]: service lmtpunix pid 11261 in READY 
> state: terminated abnormally
> Sep 10 06:44:11 mailsrv master[10325]: service imap pid 11262 in READY state: 
> terminated abnormally
> Sep 10 06:44:11 mailsrv master[10325]: service pop3 pid 11263 in READY state: 
> terminated abnormally
> Sep 10 06:44:11 mailsrv imap[11264]: Fatal error: cyrusdb backend 
> berkeley-nosync not supported
> Sep 10 06:44:11 mailsrv pop3[11265]: Fatal error: cyrusdb backend 
> berkeley-nosync not supported
> 
> The relevant part in /etc/imapd.conf:
> 
> # DB Settings
> mboxlist_db: skiplist
> seenstate_db: skiplist
> quota_db: skiplist
> duplicate_db: skiplist
> annotation_db: skiplist
> ptscache_db: skiplist
> subscription_db: flat
> tlscache_db: skiplist
> 
> I can not find any reference to a berkley db, so I don't know why the daemons 
> thow errors about
> the missing berkeley support. The only to dbs which are berkeley-nosync by 
> default are:
> duplicate_db and tlscache_db, but I have them set to skiplist in my config.
> 
> Can anyone tell me, which db defaultsetting is berkeley-nosync and not 
> overwritten in my imapd.conf?
> 

I missed the the new feature "statuscache" and statuscache_db ( since version 
2.3.11 ).
The db statuscache_db is by default berkeley-nosync.

Thanks to Simon Matter for this usefull hint.

Regards,

Konrad

-- 
Konrad Mauz 
Rechenzentrum
Hochschule Technik, Wirtschaft und Gestaltung
Braunegger-Strasse 55, D 78462 Konstanz 
e-mail: km...@htwg-konstanz.de
Tel.:   +49 7531 206-472
Fax.:   +49 7531 206-153

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


Sieve redirect with over quota mailbox

2006-11-08 Thread Konrad Mauz
Hello everybody,

when a user has the following sieve script actived,
mails to the user are stored in his local mailbox
and forwarded to the external address.

redirect "[EMAIL PROTECTED]";
keep;

If the user is over quota, the mail is not delivered
to his local mailbox ( OK ), but neither forwarded to
the external addressi ( NOT OK ?!? ). Is this a bug or a feature?
I can work around this problem by adding the external addresses
to the aliases files. I want to know if this is the correct way
to solve the problem.

Regards,

Konrad Mauz


my imapd.conf ( cyrus 2.3.7 )


# Admins
admins: cyrus 

###
# Login
allowplaintext: 1
sasl_pwcheck_method: saslauthd
sasl_mech_list: login plain

##
# Cyrus Features
duplicatesuppression: 1
expunge_mode: delayed
reject8bit: 0
munge8bit: 1
servername: mailsrv
singleinstancestore: 0

# Directories
configdirectory: /srv/cyrus/imap
partition-default: /srv/cyrus/spool1
defaultpartition: default
fulldirhash: 0
hashimapspool: 1
sievedir: /srv/cyrus/sieve


# case insensitiv user
# names
username_tolower: 1
lmtp_downcase_rcpt: 1

# DB Settings
mboxlist_db: skiplist
seenstate_db: skiplist
quota_db: skiplist
duplicate_db: skiplist
annotation_db: skiplist
ptscache_db: skiplist
subscription_db: flat
tlscache_db: skiplist
skiplist_unsafe: 1

# Quota Settings
quotawarn: 90
quotawarnkb: 5000


-- 
Konrad Mauz 
Rechenzentrum
Hochschule Technik, Wirtschaft und Gestaltung
Braunegger-Strasse 55, D 78462 Konstanz 
e-mail: [EMAIL PROTECTED]
Tel.:   +49 7531 206-472
Fax.:   +49 7531 206-153

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


quota for folders

2003-10-20 Thread Konrad Mauz
Hello,

is it possible to setup the quota only for (sub)folders of inbox:

user.test-> no quota, all mail must be delivered
user.test.bar-> quota
user.test.foo-> quota
user.test.sent-mail  -> quota

but i dont want to set up quota for all subfolders only once.


background: i would like to migrate a midrange mailserver with about
4000-5000 users. the feature above is a mandantory, so it would be
nice, if anyone can give me a hint, if this works or not.

tia
    Konrad
-- 
Konrad Mauz Rechenzentrum Fachhochschule   
Braunegger-Strasse 55, D 78462 Konstanz 
e-mail: [EMAIL PROTECTED]
Tel.:   +49(0)7531-206-472  


Re: quota for folders

2003-10-20 Thread Konrad Mauz
Hallo Patrick,

sorry for asking silly questions, but can you tell me how?

it would be nice, if you can explain it with the example
below.

the user should have no quota on user.test but
a quota of 50 MB for the subfolders of inbox.

If the user creates another folder, the quota must
also count for this new folder?


> >user.test-> no quota, all mail must be delivered
> >user.test.bar-> quota
> >user.test.foo-> quota
> >user.test.sent-mail  -> quota

-- 
Konrad Mauz Rechenzentrum Fachhochschule   
Braunegger-Strasse 55, D 78462 Konstanz 
e-mail: [EMAIL PROTECTED]
Tel.:   +49(0)7531-206-472  


Re: Mailbox Case sensitive

2003-10-20 Thread Konrad Mauz
Hello Samuel,

I'm just new to this list, but I think the parameter

lmtp_downcase_rcpt: yes

in /etc/imapd.conf 

should be the way to lowercasing the users during mail delivery

Regards,

Konrad

On Mon, Oct 20, 2003 at 03:51:51PM +0100, Samuel Luxford-Watts wrote:
> I am using SuSE 8.2, Exim 4 and Cyrus. Everything works great except if
> someone types the user portion of the address in the wrong case. Is there
> any way of turning this functionality off? or do I have to write an address
> re-writing rule for exim?

-- 
Konrad Mauz Rechenzentrum Fachhochschule   
Braunegger-Strasse 55, D 78462 Konstanz 
e-mail: [EMAIL PROTECTED]
Tel.:   +49(0)7531-206-472  


Re: silly question: how does mail get in the sent folder?

2004-11-25 Thread Konrad Mauz
On Thu, Nov 25, 2004 at 03:57:21PM +0100, Jochen Staerk wrote:
> I know that POP&IMAP are used for fetching mail, and SMTP is used for 
> sending mail, what bothers me is the question: what protocol is used for 
> moving mail, like from folder A to folder B? I suppose that is still IMAP?

Yes, the client uses the IMAP protocol to move mails from one folder to
another folder.


> 
> Another thing, how do "sent" folders work? When I send mail, that goes 
> to my postfix. I understand there is something called LMTP in postfix 
> for local delivery, that hooks up with cyrus. When I send a mail, does 
> LMTP inform cyrus that this mail also belongs in my "sent" folder?
> 
> I've used UW IMAP before, and there was no such thing as LMTP, was SMTP 
> used for this situation, then? How does mail get delivered to cyrus, is 
> cyrus listening to a SMTP-port (a LMTP-Port?) for Postfix to connect to, 
> does Postfix connect with some special IMAP commands or does postfix 
> just place some files in some folders?
> 
> How comes theses files can have a different format from that used with 
> UW IMAP (standard Unix MBOX), then?

No, no... postfix has nothing to do with your sent ( or sent-mail )
folder. This folder is managed by your mail client.

When you send a mail, your client makes a copy of your mail an save it
in the folder, which is configured to hold your sent mails.

This has nothing to do with cyrus, uw-imap or postfix.

Regards

Konrad

-- 
Konrad Mauz Rechenzentrum Fachhochschule   
Braunegger-Strasse 55, D 78462 Konstanz 
e-mail: [EMAIL PROTECTED]
Tel.:   +49(0)7531-206-472  
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


number of imapd processes never decrease

2015-09-16 Thread Konrad Mauz

Hi,

on monday I updated our cyrus mailsystem to version 2.5.6 ( coming from 
2.3.x ). The upgrade process was successfull.



Problem 1: The number of imapd processes increases during the day ( 
normal! ) but keep increasing during the night ( not normal ).

I have a graph attached.
Cyrus is running an a recently updated Ubuntu 14.04. lts server. Is 
there anything I can do?


Problem 2: In my start-stop script i sent SIGTERM to the master process. 
The master exists, but sometimes most imapd process lists as "defunc" 
with "ps -ef". They never exits an must be killed with kill -9 or by a 
server reboot. Is this the wrong way?


Regards,

Konrad

cyrus.conf:

START {
  # do not delete this entry!
  recover   cmd="ctl_cyrusdb -r"

  # this is only necessary if using idled for IMAP IDLE
  idled cmd="idled"
}

# UNIX sockets start with a slash and are put into /var/imap/socket
SERVICES {
  # add or remove based on preferences
  imap  cmd="imapd" listen="imap" prefork=10 maxchild=3000
  imaps cmd="imapd -s" listen="imaps" prefork=10 maxchild=3000
  pop3  cmd="pop3d" listen="pop3" prefork=5 maxchild=100
  pop3s cmd="pop3d -s" listen="pop3s" prefork=5 maxchild=100
  sieve cmd="timsieved" listen="sieve" prefork=1

  # these are only necessary if receiving/exporting usenet via NNTP
#  nntp cmd="nntpd" listen="nntp" prefork=0
#  nntpscmd="nntpd -s" listen="nntps" prefork=0

  # at least one LMTP is required for delivery
  lmtpunix  cmd="lmtpd" listen="/srv/cyrus/imap/socket/lmtp" 
prefork=1 maxchild=5


# this is only necessary if using notifications
  notifycmd="notifyd" listen="/srv/cyrus/imap/socket/notify" 
proto="udp" prefork=0

# syncserver   cmd="sync_server" listen="csync"
}

EVENTS {
  # this is required
  checkpointcmd="ctl_cyrusdb -c" period=30

  # this is only necessary if using duplicate delivery suppression,
  # Sieve or NNTP
  # -X 60 -> expunged mails are unexpungable for 60 days
  # -D 60 -> deleted forlders are undeleable for 60 days
  # -E 7 -> delete entries in des duplicate database older then 7 days
  delprune  cmd="cyr_expire -D 60 -X 60 -E 7" at=0400

  # this is only necessary if caching TLS sessions
  tlsprune  cmd="tls_prune" at=0400
  squatindexcmd="squatter -i -v -s" at=0500
}



--
Hochschule Konstanz - Rechenzentrum
Konrad Mauz km...@htwg-konstanz.de
Tel: +497531206-472, Fax: -153
http://www.htwg-konstanz.de/rz.html



smime.p7s
Description: S/MIME Cryptographic Signature

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: number of imapd processes never decrease

2015-09-17 Thread Konrad Mauz

Am 17.09.2015 16:18, schrieb Vladislav Kurz:

On Thursday 17 of September 2015 you wrote:


I would consider how many users you have connected as well as each type of
device. If you are running some type of AS setup, each device will
maintain an open connection and cause a process to happen. How many users?

What do you mean by AS setup? Autonomous system? nothing like that.
Clients use thunderbird, outlook, mobile phones, webmail.


I think Paul mean AS = Active Sync.



I don't know the exact number of imap users, because some users still use pop3
(which has short-lived connections). Currently there are about 200 imapd
processes. (Plus another 60 "imapd -s").

I think every client is going to be turned off, rebooted, or out of battery
from time to time. So I feel like there are some processes "forgotten",
keeping the connection with nobody on the other end.


I think this too. Yesterday afternoon I changed the imapd.conf 
configoption "tcp_keepalive" from 0 to 1.
The number of imapd processes dropped from 2800 ( yesterday 7:00am ) to 
arround 1000 ( today 7:00am ).


When I understand tcp keepalive correctly, the systems now checks from 
time to time ( every 2 hours by default on linux systems ) with an ACK 
package

if the tcp connection endpoint is still reachable.

I am neither an cyrus nor an tcp/ip expert, so a comment from an expert 
would be nice.


Regards,

Konrad







--
Hochschule Konstanz - Rechenzentrum
Konrad Mauz km...@htwg-konstanz.de
Tel: +497531206-472, Fax: -153
http://www.htwg-konstanz.de/rz.html




smime.p7s
Description: S/MIME Cryptographic Signature

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: 2.4.17 --> 2.5.3 Some mail folders no longer accessible

2015-09-22 Thread Konrad Mauz

Am 22.09.2015 12:01, schrieb Patrick Goetz:

Upgrading from 2.4.17 to 2.5.3 resulted in one very strange problem.
Some of the users have a large number of nested mail folders.  After the
upgrade, exactly one user found that some of his folders (say 3 out of
30) are now inaccessible.  In Thunderbird they show up, but are greyed
out.  If you try to subscribe to the folder, the subscribe checkbox is
missing.  In roundcube they aren't visible at all.


Hi Patrick,

have you checked the contents of the subscription file for that user and
if all the entries in the subscription file are really valid mailfolders?


Regards,

Konrad



This is pretty clearly a permissions problem of some kind.  The question
is how could this happen and what's the least painless way of going
about resetting the permissions so that he has access to these folders
again?

We're not doing anything fancy; for example, there are no shared
folders; independent email addresses are configured for shared mail
content and configured in the MUA.  The problem folders are in an
unshared account.

Also, the manifestation of the permissions problem isn't consistent
across the affected folders.  As reported by the user:

Archives Staff:  grayed out, cannot see email
Archives Staff Retreat:  not grayed out, cannot see email, when you
click on it, it says the action cannot be completed because the account
does not exist
General Convention Office:  not grayed out, can see email, when you
click on it, it says the action cannot be completed because the account
does not exist.

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





--
Hochschule Konstanz - Rechenzentrum
Konrad Mauz km...@htwg-konstanz.de
Tel: +497531206-472, Fax: -153
http://www.htwg-konstanz.de/rz.html




smime.p7s
Description: S/MIME Cryptographic Signature

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

sync_clients bails out - failed to order folders correctly

2020-09-30 Thread Konrad Mauz
Hello list,

I had a working replication between to cyrus 3.0 servers running.

The sync_client is started once a day.

In the last days the sync_client bails out with 

do_folders: failed to order folders correctly

every time on a  specific mailbox of a specific user.

I can't see that there is a problem with the mailbox ( cyr_expire and squatter 
are running correctly ).

How can I get the sync_client work again?

thanks in advance and kind regards,

Konrad
-- 
Konrad Mauz - Rechenzentrum HTWG Konstanz
Tel: +497531206472 - Fax: +497531206153
E-Mail: km...@htwg-konstanz.de
Web: http://www.htwg-konstanz.de/rz.html


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: Cyrus 2.5.9 imapd children count grows and exceeds limit

2016-09-11 Thread Konrad Mauz via Info-cyrus

Am 12.09.2016 um 05:01 schrieb Andy Dorman via Info-cyrus:

Hi everyone.  We have 14 Debian servers running the current Debian
release of Cyrus imap 2.5.9.

We upgraded from 2.4.18 to 2.5.9 on Aug 28, upgraded the cyrus.conf &
imapd.conf to rename the deprecated options and switch from skiplist to
twoskip for all our dbs. Our cyrus.conf and imapd.con (minus comments)
is at the end of this email.

We now have 4 of the 14 servers where the number of imapd processes
slowly grows and usually within 12-14 hours reaches the imapd process
limit (currently set to 100).  From what we can tell watching the
process list, the old processes are never shut down after reaching their
usage limit (which is the default).

The difference between the 4 with the problem and the others have to be
the mail clients.  Each server supports a different group of mail
domains and users, so I suspect some of the users on the problem servers
are using one or more mail clients that are not well behaved, but I have
no indication of what they are doing wrong.

While we had this problem intermittently with 2.4.18 (once or twice a
month on a random server), it is much worse since the update to 2.5.9.
We now have to restart imapd on all the problem servers almost twice a day.

If it matters, we have tried both idled and polling and have not seen
any difference.

So has anyone else seen an issue like this?  Does anyone have any
suggestions on how to debug?

We have examined syslog and do not see any strange reports outside of
the normal berkeley DBERROR messages we always see due to bdb compiled
into the debian Cyrus release.



Hi Andy,

try to set

tcp_keepalive: 1

in imapd.conf.

Regards,

Konrad




--
Hochschule Konstanz - Rechenzentrum
Konrad Mauz km...@htwg-konstanz.de
Tel: +497531206-472, Fax: -153
http://www.htwg-konstanz.de/rz.html



smime.p7s
Description: S/MIME Cryptographic Signature

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