On 01/17/2017 05:21 AM, Eugene M. Zheganin via Info-cyrus wrote:
Hi,
I'm using cyrus-imapd for quite long, but recently I encountered an
issue with delivery: one of my mail servers is handling a significant
load of e-mails, and quite often I'm seeing line like this in the maillog:
Jan 17 12:35:
front. Good find Andy.
Bron.
On Tue, 17 Jan 2017, at 04:01, Nic Bernstein via Info-cyrus wrote:
Thanks for the heads-up. We'll get this fixed, it is the man page which
is correct.
-nic
On 01/16/2017 10:19 AM, Andy Dorman via Info-cyrus wrote:
On 01/13/2017 12:07 AM, ellie timoney via
ke it went
away sometime before 2.4.0
On Tue, Jan 17, 2017, at 09:41 AM, Bron Gondwana via Info-cyrus wrote:
Yep, it's gone away - sha1 is the only mode right now. We're going to
want to look at blake2 soon though I reckon.
Bron.
On Tue, 17 Jan 2017, at 03:48, Andy Dorman via Info-c
So the subject is the question...
Running cyr_info conf-lint against our imapd.conf indicates "guid_mode"
is gone and indeed, the imapd.conf man page doesn't mention it now.
But many older versions of the man page do mention it and I can not find
any mention in past release notes at
http://
On 01/13/2017 12:07 AM, ellie timoney via Info-cyrus wrote:
The Cyrus team is proud to announce the immediate availability of the
first release candidate from the Cyrus IMAP 3.0 series: 3.0.0-rc1.
As a release candidate, it is considered near-stable for production
usage. Interfaces, APIs, feat
le, so we can continue to look for interesting
patterns/deviations in the meantime.)
Cheers,
ellie
On Sat, Oct 1, 2016, at 12:00 AM, Andy Dorman via Info-cyrus wrote:
On 09/28/2016 09:59 AM, Andy Dorman wrote:
On 09/27/2016 07:08 PM, ellie timoney via Info-cyrus wrote:
I wonder if we can see wha
On 09/28/2016 09:59 AM, Andy Dorman wrote:
On 09/27/2016 07:08 PM, ellie timoney via Info-cyrus wrote:
I wonder if we can see what the old processes are actually doing...
Is there any chance you're able to obtain a backtrace of these?
You can use a command something like:
gdb -p pid /pa
On 09/27/2016 07:08 PM, ellie timoney via Info-cyrus wrote:
I wonder if we can see what the old processes are actually doing...
Is there any chance you're able to obtain a backtrace of these?
You can use a command something like:
gdb -p pid /path/to/imapd
where pid is the one of the ima
On 09/14/2016 05:21 PM, Tod A. Sandman wrote:
srwxrwxrwx 1 root root 0 Sep 14 06:10 /run/cyrus/socket/idle
However, our imapd.conf specified a different idle socket which was
also created when cyrus-imapd was restarted.
srwxrwxrwx 1 root root 0 Sep 14 06:10 /var/run/cyrus/socket/idle
Make su
On 09/13/2016 02:15 AM, Bron Gondwana via Info-cyrus wrote:
On Tue, 13 Sep 2016, at 10:44, ellie timoney via Info-cyrus wrote:
Note that it talks about the process being used for new connections.
Each imapd process serves one connection at a time (so if you have 50
client connections, you will h
On 09/13/2016 02:15 AM, Bron Gondwana via Info-cyrus wrote:
On Tue, 13 Sep 2016, at 10:44, ellie timoney via Info-cyrus wrote:
Note that it talks about the process being used for new connections.
Each imapd process serves one connection at a time (so if you have 50
client connections, you will h
open?
Cheers,
ellie
On Mon, Sep 12, 2016, at 01:01 PM, Andy Dorman via Info-cyrus wrote:
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 op
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 (m
On 08/26/2016 09:47 AM, Tod A. Sandman via Info-cyrus wrote:
I noticed after upgrading from cyrus-imapd-2.3.16 to cyrus-imapd-2.5.9 that the
"info" cyradm command no longer works: it prints out nothing. Furhermore,
after issuing the info command, no other commands print anything either. For i
missing what is going on here.
Andy Dorman
On 08/25/2016 06:19 PM, ellie timoney via Info-cyrus wrote:
Do you have "lmtp" defined in /etc/services?
On Thu, Aug 25, 2016, at 08:44 AM, Andy Dorman via Info-cyrus wrote:
We have a cluster of servers that provide external email security
Sorry to bother everyone again...
While researching the "Bad IPLOCALPORT value" log entry, I went ahead
and switched our dev server databases from skiplist to twoskip and ran
"reconstruct -V max" and "quota -f".
Now I am seeing the following behavior in our logs.
twoskip: invalid magic heade
We have a cluster of servers that provide external email security
filtering and then postfix delivers the safe email via lmtp to mailboxes
on the various servers in the cluster (using SASLauth of course).
I just updated our dev server to 2.5.9 and while email delivery seems to
be working fine,
On 07/15/2016 08:52 AM, Bron Gondwana via Info-cyrus wrote:
On Fri, Jul 15, 2016, at 23:46, Andy Dorman via Info-cyrus wrote:
So if the issue apparently lies with twoskip, can we keep our dbs using
skiplist and do the 2.4 -> 2.5 upgrade? Is it possible -h could revert
back to skiplist?
On 07/15/2016 08:11 AM, Bron Gondwana via Info-cyrus wrote:
So we've discussed this at length in #cyrus on freenode, and concluded that the
issue is that twoskip is doing far too many munmap / mmap calls during an
unlocked foreach (which is what the LIST command uses).
I've filed a bug:
https
19 matches
Mail list logo
