Re: 5.99.13 released; important upgrade for 5.99.12 users

["Jean-Yves Avenard" <jyavenard@xxxxxxxxx>]

Hi


2008/5/11 John Goerzen <jgoerzen@xxxxxxxxxxxx>:
> That smells like it's almost certainly a server problem.  Running under -d
> imap -1 (remember to scrub sensitive data) may illuminate things.

yep it is... but unfortunately the reason is the way offlineimap
handles the synchronisation. I reported the problem a while back ,
stating than when syncing with Windows Exchange it will happen sooner
or later. in my case, it did happen.

the error shown on the exchange server is :
An unexpected exception
Microsoft.Exchange.Data.Storage.StoragePermanentException occurred
while processing a command for user Jean-Yves Avenard.
Microsoft.Exchange.Data.Storage.StoragePermanentException: Cannot get
ID from name. --->
Microsoft.Mapi.MapiExceptionNamedPropsQuotaExceeded:
MapiExceptionNamedPropsQuotaExceeded: Unable to get IDs from property
names. (hr=0x80040900, ec=-2147219200)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=174]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=140][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetIDsFromNames [86]
    Lid: 17082   ROP Error: 0x80040900
    Lid: 16993
    Lid: 21921   StoreEc: 0x80040900
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropGetIDsFromNames [86]
    Lid: 6363    StoreEc: 0x8004010F
    Lid: 6363    StoreEc: 0x8004010F
    Lid: 31229   Error: 0x0
    Lid: 6363    StoreEc: 0x8004010F
    Lid: 7867    StoreEc: 0x80040900
    Lid: 4475    StoreEc: 0x80040900
    Lid: 4603    StoreEc: 0x80040900
    Lid: 5323    StoreEc: 0x80040900
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x80040900
    Lid: 24529
    Lid: 18385   StoreEc: 0x80040900
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message,
Int32 hresult, Object objLastErrorInfo)
   at Microsoft.Mapi.MapiProp.GetIDsFromNames(Boolean
fCreateIfNotExists, NamedProp[] np)
   at Microsoft.Exchange.Data.Storage.InternalSchema.ResolveNames(MapiProp
mapiProp, NamedProp[] namedProperties, Boolean
allowUnresolvedInternetHeaders, MapiExceptionNamedPropsQuotaExceeded
originalException)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Storage.InternalSchema.ResolveNames(MapiProp
mapiProp, NamedProp[] namedProperties, Boolean
allowUnresolvedInternetHeaders, MapiExceptionNamedPropsQuotaExceeded
originalException)
   at 
Microsoft.Exchange.Data.Storage.InternalSchema.PropTagsFromPropertyDefinitions(MapiProp
mapiProp, StoreSession storeSession, Boolean
allowUnresolvedInternetHeaders, MapiExceptionNamedPropsQuotaExceeded
originalException, NativeStorePropertyDefinition[]
propertyDefinitions)
   at 
Microsoft.Exchange.Data.Storage.InternalSchema.PropTagsFromPropertyDefinitions(MapiProp
mapiProp, StoreSession storeSession, Boolean
allowUnresolvedInternetHeaders, IList`1 propertyDefinitions)
   at Microsoft.Exchange.Data.Storage.MapiPropertyBag.GetProperties(IList`1
propertyDefinitions)
   at 
Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.InternalLoad(PropertyDefinition[]
properties, Boolean forceReload)
   at 
Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.Load(PropertyDefinition[]
properties)
   at Microsoft.Exchange.Imap4.Imap4RequestAppend.Process()

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Unfortunately, the way offlineimap add IDs to the mail to check which
email has already been synced rather than using something like:
MapiExceptionNamedPropsQuotaExceeded

Microsoft Exchange can only reference up to 65,535 different
properties in an email header.
offlineimap creates a unique one every time an email is received, so
the day you have received more than 65,535 messages (happens quite
quickly these days with the amount of spam) any exchange based mail
server will refuse to accept the new email.

instead of creating a unique property ID per message, offlineimap
should do the much more standard approach like:
X-OfflineImap-ID: unique_message_property_id

Now, not too sure what to do unfortunately....

Jean-Yves