Thank you for including me here.
Probably our use case goes against the grain of the normal trend in email clients. We have a large international presence in many countries, and are not interested in communications with anyone outside our organization (through citadel). We have run our own mail servers for over 10 years in a very secure fashion, only enabling mail from known domains, or select email addresses, and refusing all others.
We decided to switch to Citadel, because we could make each use of the ability to "turn off" internet email, and still allow our users to communicate with each other through their email clients. We currently have 2 different secure domains which only function for internal communication, and have no intention of mailing the "outside world."
There have been times where, due to power outages and other such mishaps where the server has gone offline, making secure communication unable to take place, which caused us to consider a second machine / domain which would contain a matching userbase and would be interchangeable with the other domain in case one of the locations went down. We were not trying to duplicate inboxes, although that would be a nice feature to have, not essential. The users are all kept within an LDAP tree, which contains basic info from which to populate the vcard in citadel (which I have to manually do at this point, in order to allow for my users to have the proper information within the Citadel system, according to our protocol for setting up users. I basically create a template file which maps out the different user registration lines and fills in the proper info and then logs them in for the first time and issues a registration then logs out, to take care of the required first login for ldap users).
I think to sum up my concerns:
We need the ability for citadel to recognize communication from another citadel server, and reject anything not coming from a local user within citadel, under either domain. The usernames would be the same, but the email address could be either domain. Would it be possible to make an optional component be server to server federation of SMTP, with a special code or some type of way of only authenticating a known machine to be able to send messages to? Basically, one machine per domain, with the ability to receive outside mail from only the other machine.
I can live with the global address book being unfederated. It would be nice for an LDAP version of Citadel to be able to search the LDAP as an address book source.
Anyways, I am sure there is more to say, but this can at least prompt questions and such. I am also willing to test out custom builds or patches to bring this about. Please let me know how I can help.
