Feature #114
Disable x-offlineimap-message-guid headers
| Status: | New | Start: | 11/21/2008 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Resolution: |
Description
Is it at all possible to disable the creation of the x-offlineimap-message-guid header in messages downloaded? Apparently, doing so puts a significant load on the Exchange server we use here, to the point that offlineimap users might have to be moved to a separate database server:
We are reaching out to you in hopes that you could help us out with a bit of a problem we've recently
encountered. It appears that you are using a tool called offlineIMAP which creates a unique
X-header for every message you download, usually in the form of "x-offlineimap-message-guid".
Exchange creates a new named property for each new non-standard x-header it sees on a per database
basis. We are limited to 32k named properties per database. If we reach this maximum the databases
will dismount and we will have to restore from backup and begin a remediation process, causing
unnecessary downtime for all residents of that database.Can offlineimap work without this header? Is it possible to disable it?
History
Updated by John Goerzen 472 days ago
Hi,
These headers are used to identify messages after an upload. It probably would be possible to rename them to all have a single X-OfflineIMAP: header, though this would have to be verified against other servers. There is nothing wrong, spec-wise, with the way OfflineIMAP is working at present.
I'd be happy to get a patch for this. I don't presently have time to implement it out of my volunteer time, but I would entertain a contract to do it if you're interested in paying to get the feature added to the codebase.
Updated by Gregory Smith 472 days ago
- File imap-single-x-header-v6.0.0.patch added
Here's a patch against 6.0.0.