On Fri, Sep 16, 2005 at 11:07:38PM -0400, Matthew Carroll wrote:
> Just to confirm, I restored one of the old mbox files onto my local
> system today and was unable to reproduce the problem. Perhaps we missed
> something during the upgrades whilst trying to fix this on our web
> server? I really do
> I will try
> restoring one of the mbox files from before the migration and test it
> locally to see if the problem is present then. I'll let you know what
> happens.
Just to confirm, I restored one of the old mbox files onto my local
system today and was unable to reproduce the problem. Perhaps
On Wed, Sep 14, 2005 at 12:11:03PM -0400, Matthew Carroll wrote:
> The bug affected all users I tested in the way described, i.e. once
> squirrel was used to delete a message in the inbox, the UID Bogus number
> set error came up. We had upgraded to 1:0.6.90-2 and I'm sure the daemon
> had been res
On Sat, Sep 10, 2005 at 11:14:57PM -0400, Matthew Carroll wrote:
> I believe I am experiencing this same problem, with squirrelmail access
> to user mbox files causing the error:
>
> ERROR: Bad or malformed request.
> Query: SEARCH UID 1:2490
> Server responded: UID SEARCH Bogus number set (near e
I believe I am experiencing this same problem, with squirrelmail access
to user mbox files causing the error:
ERROR: Bad or malformed request.
Query: SEARCH UID 1:2490
Server responded: UID SEARCH Bogus number set (near end)
I have upgraded to mailutils-imap4d 1:0.6.90-2 and the latest
squirrelma
5 matches
Mail list logo
