Well, it works Ok for me.
Not in production mode, but on a test system.

I think it is a good base to build on a more specific solutions, like adding colaboration packages, but that should be up to users to decide what to add on cause you can not possibly meet all of requests for features.

I do not know if you are waiting for new features requests that you might want to include, or there are some bugs, and there will always be some, even in stable release.

If I may quote from a web:

"What iRedMail is
•A fully fledged email server solution"

I can't really comment on how and why would ejabberd be a thing to consider when setting up iredmail system, cause it is an application to be used with instant messaging clients. Has nothing to do with anything how email works.

Any addon service, regardles how useful and popular is, needing it's own ports and packages, only lowers security and stability of what is supposed to be a stable emailing system.

That being said, would it not be better to have iredmail system, with features related to email services, as a stable and proven framework, focused on email, and all other services, like ejabbberd, to be an optional addon features, after iredmail system is setup.

"What iRedMail is
•A fully fledged email server solution"

Does your point of view mean that above is no longer true?

When you say "adding more functionality" do you mean email related functionality or "nothing-to-do-with-email functionality"?
In case of first, I agree that that would bring new people who wants fully fledged email system. In case of second, what will happen when a new group says that they want to replace jabber with something else?
Would you waste time discusing non-email-related issues running on a syste,that has to do only one, and a couple related, email related services?

When you say "The more folks help with testing" do you mean testing email server setup or testing services that are not email related?
If iredmail is really going to be a colaboration suite, it would be fair to declare that first.

I know that jabber is another form of communication. As well as any BB.
All I am saying it is not at all email type of communication.

What attracted people here are "A fully fledged email server solution", which translate to "if any issue, it would be only email related issue"
Not words like "A fully fledged all-kinds-of-communication server solution" which translate to "who knows what will confict with what"

Email administrators are not always interested in managing jabber type of service, nor do I think that most of them woould like to have it incorporated on a stable emailing system.

Me, for example, would first look for how not to install not-emal related services if this becomes a path of iredmail.
Do you really think that person responsible to administer a "fully fledged email system" what iredmail still claims to be, have a time to worry about service that has security fixes once a month?

As said, these days communication happens through many channels. As I also said, XMPP will be optional. Thinking a company just wants/needs email isn't true anymore ... a company and/or individual wants to have a communication package that can deliver on email, xmpp and maybe even groupware.

I don't see why you seem to be concerned ... think of IRM as of a communication package with email at its core and optional parts like XMPP. That's what corporations and/or individuals expect these days.

I believe in the adage don't put all your eggs in one basket; although add-on features like ejabberd is nice to have but the main focus should be to extend the email functionality e.g. UI to monitor and release quarantined emails, monitor and manage email related services which I believe will be included in the next release, right?, enable users to manage SPAM similar to Zimbra. As regards addons, IMO the right approach would be to enable administrators to use the iRedMail's LDAP schema as authentication mechanism to bind other services like Samba, FTP, Proxy and be able to manage those bound services through iRedMail or is this asking too much already

You can not compare a company like google, and their application coexistance with a iredmail project that would try to make such setup by using projects that have nothing in common. Next thing you will compare MSN and outlook ntegration with iredmail plus ejabberd.

I mean, google and MS teams will do as their bosses to ask in a goal of "Me, Me and only Me"
In open source world, each project, even if it is just a copmilation of open source packages like this one, has its own leader. And communication between leaders of unrelated projects sometimes do not work.
And I understand that email and messaging can be part of the same system but...

How are you going to prioritize?
What is more important, that email is scanned and proccesed properly, or that messenger services do their thing first?
Which one of unrelated/undependant projects would say "OK, we will lower our resource requirements, so that your services run better."
That is why in real world, each of such services do run in its own envoroment. So if there is a problem with jabber why even have opportunity to think that posfix people are messing server up?

However, if long term idea is to turn iredmail in to a groupware project, this is the right way to do it.

And ejabberd is messenger type service, does not need anything that email service does.
Not same protocols, ports, only user backend sharing via LDAP but...
What is going to be of iredmail people that do want to stay with mysql backend?

What does that mean for ejabber in 0.6? It will be available but optional right? You said so.

Ejabberd won't be shipped in iRedMail, even as an optional component.

As @011 suggested, i prefer to keep iRedMail as a pure email solution. And as i said in previous post, we MAY public integration tutorials later, include ejabberd, PureFTPD, OpenVPN, etc.

That means i have more time to spend on EMAIL solution, and save much time which should be spent on addition components.

I must apologize to you for my promise in email.

I think it's not a good idea to create or maintain an ALL-IN-ONE project/product, at least not NOW. Publicing integration tutorials should be better than integrating them directly. Integrations take me so much time to maintain (upgrade components, testing, etc) these 3rd party components and what most of users need is an email server solution. So, as @011 suggested, keep iRedMail as a pure email solution should be better.

And, community project doesn't mean 'user requests feature X, developers must implement it', but it means you can contribute to help to implement it.

iRedMail is almost a framework to help you integrate 3rd party components with OpenLDAP, it would be great that someone can maintain these 3rd party components integration scripts, such as Ejabberd, OpenVPN, PureFTPD, Samba, etc.

This is where you show why your understanding of projects like iredmail and alike fails.

This is a project that has its creator and the leader.
By the nature of the project community is welcome to contribute but it is not a democracy as you wish to see it.

Open source is full of examples where people did take a turn and made a fork-out of existing project and made it customized based on their needs. Those people woud be like yourself. However you would find that in iredmail case, at the moment, this is not possible.

On the other hand, iredmail can become modular, thus providing interface for add-on services.
And this is a first step when persuing requests like for ejabber, make plug-in frame, not for one, but for all.

Of two, if you do research, top one preveils. You figure out why cause I am not telling.