Isode's M-Link will (for "trusted" components) allow forging of local addresses by components. (It says so in the public documentation, so I think I can still say that).
But a component doing XEP-0033 isn't going to be useful, I'm afraid. There's two purposes to XEP-0033: 1) Bandwidth saving. But actually, if you try out compressing a set of stanzas before and after "processing" with XEP-0033, you'll find it doesn't help much (I recall it actually makes things worse). 2) Processor saving. If your XMPP server is using a fairly slow stanza parsing method, it could be that this is sensible, particular for large number of recipients. But in this case, there's no point in running '33 as a component, because it'll then incur more stanza processing by using '33 than without, as Matt Wild has already said. In any case, implementing one-to-many sending is fine - it's just that you want to do this by just sending to many one-to-one in the vast majority of cases. If you have sufficient numbers to worry about (2) above, then it seems unlikely that components are going to help at all - you'd need this core. Dave.
