Everything looks fine except that in the plugin array there shouldn't be a ispconfig3_forward.

It is planed, but due to lack of time at the moment and that i have to write my own wrap for it, so that the user can have a forward and a mail account at the same time, talking about writing into the custom rule field for the moment until ispconfig solves this little issue.

PS: I will upload your translations and all other translations which people sent me to the svn server.

Yes, I know you've planned maing another forwarding plugin, hence I left it there... Roundcube won't activate plugins that aren't in the plugin folder so it's there when the new forwarding plugin comes out =)

Hi there, I tried to install your plugin (and roundcube, for this occasion), But I had some problems.
I've followed this howto : http://trac.roundcube.net/wiki/Howto_Install_fr
Here it was quite long (but I'm just too bad ). Don't forget to put "CGI" for php in the website category in ISPconfig 3.
In this same Howto, they tell us to rename some files and that didn't work, so I let the original name. After that, I saw that the rights of my files didn't let me try roundcube, So I put all in 755.
That was for the installation of roundcube.

The problems I have :
- I fall on a "soap error : The login failed, username and password was wrong." when I go on "General"
- "SERVICE CURRENTLY NOT AVAILABLE! Error No. [524]" on the forwarding item (but I think it's normal, isn't it ?
- the same soap error for "autoreply" and "spam(indésirables in french...)"

I hope it could help you, and if the problem is mine, don't hesitate to tell me !

Ok, I see now it was my fault, I didn't see the "co" command... (sorry, I never used svn before...)
Ok, the installation with svn works, and I've done the changes in config.inc.php.dist, but I fall on the same error.
I tried to rename the config.inc.php.dist to config.inc.php, but It changes nothing (do I really have to let the ".dist" ?)

First of all, I need to apologize to Horrific. I volunteered to be a Beta tester a while back and am just now getting around to installing the plugin. I will give some feedback once it is installed.

Anyhow, I followed the steps in Post #20. Things were going smooth until I log in to Roundcube. I see the Account tab under the Settings menu. When I click on three of menu options on the left (General, Autoreply, & Junk), the Roundcube error message appears at the top of the window.

The error message reads "Soap Error: Could not connect to host".

I eventually resolved the problem by copying the config.inc.php.dist file to config.inc.php. I don't recall seeing that step specified in the steps in Post #20. That copy step is pretty typical when dealing with Roundcube Plugins.

Additionally, since my test server setup has Roundcube installed as a vhost on the same physical machine as ISPConfig3, I had to use localhost instead of the FQDN in the plugin config file. If I used the FQDN, I still received the Soap Error message.

Code:

$rcmail_config['soap_url'] = 'http://localhost:8080/remote/';

Finally, the demo site that Horrific gave me a link for showed a lot more functionality than this plugin currently provides. I remember seeing the ability to interact with the SPAM filter settings more directly such as White/Black lists. Is that functionality planned for this plugin or am I expecting too much?

Generally, I like the start. I do wish there were more options and I anticipate they will be added as time allows.

First, I really like how the General tab shows the linked email addresses. I have some clients that like to use one email account as a catch all for a bunch of aliases. Sometimes, it gets hard to track them down in ISPConfig3. Having this displayed to the end user in one spot is useful in my opinion.

The password changer worked great. For an administrator, I really like the ability for users to change their passwords. It takes a lot of pressure off of me to do that and frees me up to do other important things. I would like to see the ability (either in Roundcube or ISPConfig3) for an email to request a password reset should they forget their password. I don't know how the workflow would happen yet, but at least they could initiate the process. Additionally, I am coming from Squirrelmail. The Squirrelmail Change Password plugin could be configured to force users to change their password after a fixed time interval. I liked that option as an administrator.

Autoreply worked as advertised and mostly as expected. When I enabled the Autoreply and sent a test message from a Hotmail account, I received an automatic response nearly immediately. When I disabled the Autoreply and sent a test message from a Hotmail account, I received an automatic response nearly immediately. I waited a bit and then sent another test message. An automatic response was not received. Is there a ISPConfig3 cron job on an interval that must run before the autoresponse settings take effect? If so, perhaps my first test after disabling was performed too quickly before that cron job had updated the system settings.

I tested the Junk settings. My test account had the Priority setting at 5. When I changed it to 6 in Roundcube, I saw the email account added to the Spam filter Users list with the priority set to 6. So it would appear it worked. Prior to the change in Roundcube, only the domain was listed in the ISPConfig3 Spam filter Users list. However, I have posted many times here seeking clarification on the Spam filter settings. I don't understand how the Priority setting is applied.

On my wish list of features, I would like to see users have the ability to white/black list settings for the Spam filter. I haven't thought it through yet, but some advanced users should have the ability to change their Spam filter policy setting. I don't know how you would limit which users would have the capability and which ones wouldn't.

Is there a ISPConfig3 cron job on an interval that must run before the autoresponse settings take effect? If so, perhaps my first test after disabling was performed too quickly before that cron job had updated the system settings.

Click to expand...

ISPConfig3 is using a Cronjob, it runs every minute. So every changes, password, autoreply, spamfilter, etc. are taking effect after 1 min.

On my wish list of features, I would like to see users have the ability to white/black list settings for the Spam filter. I haven't thought it through yet, but some advanced users should have the ability to change their Spam filter policy setting. I don't know how you would limit which users would have the capability and which ones wouldn't.

Click to expand...

Black/Whitelist for user isn't supported yet by ISPConfig3 as I know. Although the programs can do it, but then i can't use the remote functions of ISPConfig3 and I couldn't be sure if the plugin works then for every OS(I use Debian 5).

I haven't thought it through yet, but some advanced users should have the ability to change their Spam filter policy setting. I don't know how you would limit which users would have the capability and which ones wouldn't.

Click to expand...

You really think the users would know what it means? I mean the default policy names are not really the best explanation.

PS: When you have the https mod for the ISPConfig3 webinterface. Then the remote_url starts with https://....

Black/Whitelist for user isn't supported yet by ISPConfig3 as I know. Although the programs can do it, but then i can't use the remote functions of ISPConfig3 and I couldn't be sure if the plugin works then for every OS(I use Debian 5).

Click to expand...

In ISPConfig3, it appears that entries that are listed in the Spam filter User/Domain listing are compiled in a drop down box for the white/black list users. I'm not an expert, but my hunch is that if each user were listed, then they could have individual access to white/black lists.

You really think the users would know what it means? I mean the default policy names are not really the best explanation.

Click to expand...

I agree. As I mentioned, I still have a tough time understanding the settings as the administrator.

Going back to my force password change suggestion. When I used this setting in the past, it was with Squirrelmail on a different email server setup. That email server setup was a Virtual User setup using one of Falko's excellent tutorials on this site. But it was not an ISPConfig setup. There were some additional database fields that the Squirrelmail plugin referenced to determine if and when a user had to change the password. As a result, I anticipate implementing this suggestion may require some work on the ISPConfig side as well as the Roundcube plugin.