Apache OpenOffice (AOO) Bugzilla – Issue 76005
X-No-Archive headers
Last modified: 2021-05-27 19:28:21 UTC
User hank_leininger pointed out that, -- We carried a number of OpenOffice lists for a long time, since I think mid-2002. Our database inserter script automatically skips adding any mails with the X-No-Archive: yes header set. It looks like in mid-2005, something (list server or management software change maybe?) caused "X-No-Archive: Yes" headers to be added to every message going through the lists. Some mailing list management software (such as ezmlm) defaults to adding them to every email. This is unfortunate, as it makes it impossible to tell the difference between mails that the original poster really went out of their way to request their mails not be archived, or any regular list message that had the header added by the server. Is it intentional that the list server adds these headers? If not, would it be possible to modify the configs so that they do not? I would then re-insert the intervening mails, to catch up our archives. -- My belief is that we want OOo lists to be archived. But it would seem as if archiving would be accomplished no matter what. Support, would it be possible to evaluate altering the behavior? and what would be the consequences? As well, does the move to 4.5.x affect this particular behavior? thanks louis
Thank you for contacting CollabNet Customer Support. Based on the information that has been provided to us, we will initiate our research & provide you an update as soon as we have adequate information. Regards, Sindhu Support Operations.
In the Discussion Forum a facility has been provided by which we can add custom Header Format's for a specific mailing list . Moving this issue to the resolved later .
Updating the issue with the appropriate milestone .
Hi This feature is fixed in Rubicon and I have verified the same on a test box carrying the latest version. I shall close this case for now. Please feel free to re-open, if the functionality does not satisfy your expectation when site gets upgraded to Rubicon version of CEE. Regards, Vathsan Support Operations.
Re-opening the issue.
Marking the issue as Resolved LATER.
CollabNet Support is currently reviewing the issues under Resolved-Later. If the issues are fixed currently in any of the present CEE releases, then it will be marked as Resolved-Fixed. There might be a few issues which might not be in our future roadmap which might be closed as Wontfix unless it does not lie under any custom request.
This is fixed in CEE 5.0, hence marking as fixed