[quote user="10330phoenix"]The original question wasn't just about the A/V or A/S components. You can actually upgrade the A/V components, you search the forums for details, however, if you're an NE customer any changes you make to replace individual components will not receive support from Zimbra.[/QUOTE]
I apologize if I misread the OP's question. I did not originally interpret that the OP wants to be able to update/upgrade any single component of Zimbra. On that point, I disagree with the OP. I'll comment on that below, however. My first interpretation is that it was primarily for AV. My concern is for AV because it is the most dynamic of the components with respect to definitions and engine updates. Definitions are a moot point and not at issue. However, in my experience, ClamAV engine updates appear to break Zimbra as soon as a new engine is released.
You are right, I *could* upgrade my AV component, except for three critical reasons stopping me:
1. Ubuntu 6.06 LTS Server (Zimbra server's platform) has GCC Bug PR28045 and cannot successfully complete the ./configure script for compiling ClamAV from source. (Upgrading my server is not a financially feasible option at this time, nor do I have the time to do so.)
2. I lose any support I might be allowed (no matter if it is NE or FOSS) by altering to a non-standard, non-supported configuration.
3. I don't have the expertise or time to research, test, and implement an upgrade to just ClamAV. At this point, I have taken the step of just disabling that service for my server. I have a whopping 3 mailboxes and about 6 aliases that are hosted by Zimbra because of its innovation and quality.
[quote user="10330phoenix"]How about the example of replacing the Postifx component of Zimbra? That would involve downtime for the whole mail system. The point about the integrated packages is they are modified to fit in with the Zimbra architecture, changing single components is more than just installing a single package, a complete install is somewhat trivial to do but obviously involves some unavailability of the mail system.[/QUOTE]
While my example of Exchange is not the strongest example out there, it is about as close as I can come because Exchange and Zimbra are about it when is comes to mail systems of this nature.
I am not really intending to suggest users be able to upgrade anything other than the ClamAV engine. I agree that it is impractical to upgrade other components like postfix or the imap daemon. Those components are really part of the core of Zimbra.
ClamAV is the part that seems to break things for me when it has an engine update. I do not upgrade every time there is a .01-incremented release of Zimbra partly because Zimbra "just works." I seem to hit Zimbra upgrades every .02-.04 versions apart. In addition, I do not have the luxury of the potential downtime in upgrading Zimbra and/or my operating system. While I do not have a large number of users, elderly parents tend to be constantly when their son's (my) mail server is down. It is also my primary form of electronic communication.
[quote user="10330phoenix"]If you have any suggestions on how the upgrade of individual components can be achieved then feel free to search bugzilla
for any current RFEs or file a detailed request of your suggestions.[/QUOTE]
This is a good idea. I should do that. I have a question regarding submitting RFE bugs. How technical does an RFE need to be? Are the staff members who triage and assign these "bugs" looking for an implementation or would being able to explain my concept clearly and succinctly be sufficient?