Before this patch, cyrus was already able to detect a configuration
file change,
but only at the end of a connection. And any process waiting for a
new connection was ignoring the change during the next connection,
until they have finished.
In other word, after a configuration change, any
On Wed, Apr 02, 2008 at 11:28:07AM +1030, Stephen Carr wrote:
Dear List
I get the following type of error (see below) during replication that
appeared after upgrading from 2.3.8 to 2.3.11.
This occurs occasionally and yet the emails are synced and it occurs for
various user accounts.
I
On Wed, Apr 02, 2008 at 09:51:50PM +1100, Bron Gondwana wrote:
On Wed, Apr 02, 2008 at 11:28:07AM +1030, Stephen Carr wrote:
I get the following type of error (see below) during replication that
appeared after upgrading from 2.3.8 to 2.3.11.
BAH - upload_messages_from() is broken.
Will
On Wed, Apr 02, 2008 at 07:19:07AM -0400, Ken Murchison wrote:
Bron Gondwana wrote:
On Wed, Apr 02, 2008 at 09:51:50PM +1100, Bron Gondwana wrote:
On Wed, Apr 02, 2008 at 11:28:07AM +1030, Stephen Carr wrote:
I get the following type of error (see below) during replication that
appeared after
Bron Gondwana wrote:
On Wed, Apr 02, 2008 at 07:19:07AM -0400, Ken Murchison wrote:
Bron Gondwana wrote:
On Wed, Apr 02, 2008 at 09:51:50PM +1100, Bron Gondwana wrote:
On Wed, Apr 02, 2008 at 11:28:07AM +1030, Stephen Carr wrote:
I get the following type of error (see below) during
On Wed, Apr 02, 2008 at 11:28:07AM +1030, Stephen Carr wrote:
Apr 2 10:31:14 brooks sync_client[23049]: Hit upload limit 0 at UID
101775 for user.XXX, sending
Btw - you can get the same effect as applying the patch by putting
the following in your imapd.conf:
sync_batch_size: 4294967295
Bron Gondwana wrote:
On Wed, Apr 02, 2008 at 09:51:50PM +1100, Bron Gondwana wrote:
On Wed, Apr 02, 2008 at 11:28:07AM +1030, Stephen Carr wrote:
I get the following type of error (see below) during replication that
appeared after upgrading from 2.3.8 to 2.3.11.
BAH - upload_messages_from()
On Wed, Apr 2, 2008 at 10:30 AM, Simon Matter [EMAIL PROTECTED] wrote:
Before this patch, cyrus was already able to detect a configuration
file change,
but only at the end of a connection. And any process waiting for a
new connection was ignoring the change during the next connection,
Matt Garretson [EMAIL PROTECTED] wrote:
Along similar lines, any well-written Procmail recipe which redirects
mail typically checks for, or adds, an X-Loop header before
forwarding anything.
Yes, it's an old solution.
The crucial difference is that if one writes a bad procmail recipe,
the
On 02 Apr 2008, at 09:00, Joseph Brennan wrote:
The crucial difference is that if one writes a bad procmail recipe,
the message loops round and round until one of the MTAs considers
the hop count exceeded and bounces it to sender, but if one writes
a bad sieve rule, the message _is silently
On Wed, Apr 02, 2008 at 07:46:33AM -0400, Ken Murchison wrote:
Bron Gondwana wrote:
On Wed, Apr 02, 2008 at 07:19:07AM -0400, Ken Murchison wrote:
Bron Gondwana wrote:
On Wed, Apr 02, 2008 at 09:51:50PM +1100, Bron Gondwana wrote:
On Wed, Apr 02, 2008 at 11:28:07AM +1030, Stephen Carr wrote:
Dear List
I have applied the patch on our server and I regret to infom you it does
not fix the problem.
I still get 1 error line this when 2 emails are being delivered at
almost the same time.
Apr 3 08:42:29 brooks sync_client[4402]: Hit upload limit 0 at UID 22186
for user.AAA, sending
Dear Ken
I killed master and restated it but forgot to kill sync_client so it may
have been running the unpatched version.
I have manually restarted sync_client and after 30+ minutes had no
errors and in that period I know one user got 8 emails at almost the
same time.
It also seems the
On Thu, 3 Apr 2008 13:11:22 +1030 (CST), Stephen Carr [EMAIL PROTECTED]
said:
Dear Ken
I killed master and restated it but forgot to kill sync_client so it may
have been running the unpatched version.
Sounds viable. If you're starting sync_client from outside your cyrus
instance then you
14 matches
Mail list logo
