This is because this plugin has not been released yet so even if we update it, we do not update the version yet.
OK. I've got it now! 
Now a little bit of offtopic. Do you have in plan a cloud version of imscp, the one that could work behind NAT?
You know the kind of cloud system that Amazon EC2, Rackspace's Openstack uses.
I miss imscp in the cloud environments that I use...
Quote
Re ;
Well, without further information, we cannot help you. Let me play like God: You should probably try the version from the incubator because this plugin as been updated to fit with the last Plugin API.
Well, you are one of the Gods of imscp. 
Indeed it was a version problem. I have install it from the git and everything works great.
When I saw that the version number was still 0.0.1, didn't cross my mind that was actually the updated one.
Thanks for the help!
The external mail server is working. But I still can't install the opendkim plugin.
I don't know if it's a version problem or some parts of the previous installation is still active somewhere.
thank you.
Hello,
I have just update the imscp from 1.1.0-rc4.6 to the latest version rc4.7 and I have encounter some problems.
First one was with the opendkim plugin that I was using and it was not disabled before I run the update script. The only thing I could do was to delete the plugin like Nuxwin suggested in this post, and to clean up the imscp database where I could find any entries of opendkim. Once everything was cleaned I couldn't reinstall it once again. When I try to install it from the imscp admin are, all I get is a white page in my browser.
The second issue is about the external mail server option. When I'm trying to add a second entry, I get a "beautiful" error 400, " /client/mail_external_edit.php?item=3;normal Bad Request!"
If you could help me somehow with this...Anny suggestion is welcomed and appreciated.
Thanks!
Good to know. Thanks!
That is what I was thinking about. The DNS part with the SPF and all that. Probably must be configured with the public ip.
Thanks for the answer.
Is there any specific setting or modification that I have to apply on the i-mscp so that it would work behind NAT?
Is there a problem with this release of i-mscp? I have install it on a fresh debian 7.1 and the email just don't work. Sending an email from a local account to another, this is what I get in the log.
oct 7 16:34:55 server3 postfix/pipe[3563]: B7C92414A5: to=<[email protected]>, relay=maildrop, delay=0.3, delays=0.13/0.03/0/0.15, dsn=5.1.1, status=bounced (user unknown. Command output: ERR: authdaemon: s_connect() failed: Permission denied Invalid user specified. )
Is there a way or could it be implemented a solution to use i-mscp in to an Openstack / Amazon EC2 enviroment.
As you probably know, the virtual machines inside this kind of cloud does not have a public IP. On the VM there is a private ip, and to acces the outside Internet uses a kind of NAT.
