[QUOTE=thinksmart12;12872]Looks great so far. The installation was successful.
One thing though. The Spam and Ham training folders do not seem to “train” from every email.[/QUOTE]
Are you using the global setting? If so, the same behaviour is in 2.1.3
What do you mean in 2.1.3?
I think you mean SiteWorx and not ScriptWorx. But no, v.3.0 does not have a SiteWorx DNS editing feature. Good chance it will be in a future version though.
yes I do, pardon me.
@thinksmart12: When you enable the global bayes database, you won’t get an individual counter per user, at least I don’t.
Hi,
Just one question, the RC4 is 10 days old and there is only 2 thread pages 
So I could conclude this last RC seems to be very good.
Any idea about a target date for the final release ? do you have some kinds of milestones before this ?
Just to be uptodate :-p
Pascal
I’d love to test this… only problem is my server/installation is dieing (slowly), so I have no RPM database anymore (thanks to yum messing it up) <_<
Hopefully I will be able to replace the server soon, and then I can test it - it looks good so far, from what I’ve seen and heard
[QUOTE=IWorx-Paul;12764]The syntax is the same as with the TXT record. You can use TXT records or SPF record type in the DNS interface, and the format is the same
[/QUOTE]
Ok thanks Paul, it is important to confirm this as v=spf1 means that the dns record type is a TXT one. So the ok, you just export the SPF record exactly as the TXT one.
It’s how I understand this, indeed.
To generalize your note we could say that on a box there is most the time few IPs. One is the main IP of the server (which is the IP the mail will be sent from) and others are shared or dedicated to few accounts.
So in a “template” perspective I think it is good to have :
Target: v=spf1 a mx a:FQDN ~all
Correct ?
About this, if I remember well, the default FQDN mail server name is the default FQDN you gave to the boxe ?
The A record isn’t it added by default when you define, in nodeworx, the default FQDN ?
If yes for both, so by default, only for a dns template point of view, we should have :
Host:domain.com Target: v=spf1 a mx a:FQDN ~all
Host:FQDN Target: v=spf1 a -all
By “yourisp.com” do you talk about my ISP or talk about my FQDN host name, right ?
So then the “bounce message” spf records would go under the yourisp.com zone, and there would be one for clust01.yourisp.com. There is probably a short cut method to use to specify multiple servers, for *.yourisp.com, but check the SPF documentation.
So - using the DNS template system on the server clust01.yourisp.com, you’d add a record to the DNS template Zone, that looks like
dns-template.com SPF v=spf1 a mx a:clust01.yourisp.com ~all
As described above, you don’t need all those SPF records for each domain. You need one SPF record that allows all the nodes in the cluster to be “valid” senders. So one SPF record that looks like
dns-template.com SPF v=spf1 a mx a:clust01.yourisp.com a:clust02.yourisp.com ~all
Then, in your zone for “yourisp.com” you create an SPF records like
clust01.yourisp.com SPF v=spf1 a -all
clust02.yourisp.com SPF v=spf1 a -all
This handles the “bounce message” scenario - which is arguably less important than the “main” domain SPF record.
Yes it is exactly what I understand with SPF !
So to conclude :
At least and the most important is this SPF template :
[B]dns-template.com SPF v=spf1 a mx a:FQDN-of-the-node1.com a:FQDN-of-the-nodeX.com ~all[/B]
And this one in the FQDN zone (for all nodes like you described)
[B]clust01.yourisp.com SPF v=spf1 a -all
clust02.yourisp.com SPF v=spf1 a -all
[/B]
This SPF stuff can get complicated huh
Well my first understanding + your notes and explanations now allow me to be sure to understand what I plan to do 
Thanks a ton Paul !!
Pascal
Hi
I have open a ticket about a theme problem after the upgrade to RC4
Indeed even if I have the default iworx login page theme, once connected I stay on an old theme. So I don’t have the same menu/functionalities than the v3 and if I try to change the theme from the old menu (the one in v2.1.3) it (of course) doesn’t work
Pascal
Hi
Questions about THEMES
Before v3 we had created 1 custom theme. All our siteworx accounts used this custom theme, called carat.
Today we have created 3 customs themes. One for us and 2 default for ALL our RESELERS (as example, one working with no link and another to allow them to custom this theme)
Our new theme has the exact same name than the old one created on v2, the one used by all Siteworx accounts.
In iworx.ini we have also updated the templates default to have this theme for the login page (nodeworx and siteworx)
Ok, Everything works fine. But :
If I connect under a siteworx account it is not our theme which is used but the default Interworx one. But if I look at the siteworx features I can see that IT IS the name of our theme which is choosed !
Of course if I validate the siteworx accounts, then reconnect to the siteworx account panel, then I have our theme !
So even if the siteworx accounts features shows our theme name, it looks like we have to validate every siteworx accounts to apply the update and so have our theme rather than the interworx one ?!?!
Is there a quick way to update ALL siteworx accounts under ONE theme ?
Thanks
Pascal
Dedicated Domains per SiteWorx
If the following has been asked please forgive me, I did not see it anywhere.
If a SiteWorx (3.0) account has a dedicated IP assigned to it, and the same SiteWorx account has, say two active secondary domains.
I take then the Secondary Domains will use the same dedicated IP address?
And I assume if someone wanted the Secondary domains to have their own decided IP address a NEW SiteWorx account would need to be created to for fill the request for dedicated IP address?
If the above is TRUE, what would be the best way to move a Secondary Domain to its own primary SiteWorx account?
I don’t know if this has been brought up; but can I run the same backup-script via cron as I do now?
Aka; will the backups be domain.com.date.tar.gz on a remote host without having to change the syntax of the backup-script being run now? (reading a config-file)
[QUOTE=IWorx-Paul;12760]
NOTE: … We don’t expect the offical release to be more than a week away from now. …
Paul[/QUOTE]
Just to have some news as this post is 17 days old 
Is there some problems with the final release ?
What about the Template question I’ve made ?
when final release will be out, will I have to update every accounts, even if the custom template has the exact same name in V2 and V3 ?
I just ask to allow us to plan an action when final release will be out
And, no and no, I don’t ask when final release will be out
I 'd just like to know if everything is cool for you (iworx team) and goes well or if you have encountered little problems which might become more hard than supposed to be ! 
Pascal
No major problems Pascal, we’re just finishing up the documentation for the new features, and have a couple small bugs to fix, and then we’ll be good to go. We will give you a couple days notice before the release will be auto-updated.
Is there a quick way to update ALL siteworx accounts under ONE theme ?
The theme info is stored in the database now for each user, so there’ll be an “easy” way, but it’ll require running an SQL command to do it - I’ll see about making at least a command line way to do this without having to do it 100% manually via SQL.
If the following has been asked please forgive me, I did not see it anywhere.
If a SiteWorx (3.0) account has a dedicated IP assigned to it, and the same SiteWorx account has, say two active secondary domains.
You won’t be able to add secondary domains to accounts on a dedicated IP. That may change at some point, but that’s how it works right now.
And I assume if someone wanted the Secondary domains to have their own decided IP address a NEW SiteWorx account would need to be created to for fill the request for dedicated IP address?
Yep, given that dedicated ips won’t have secondary domains, a new siteworx account is indeed in order for these domains.
If the above is TRUE, what would be the best way to move a Secondary Domain to its own primary SiteWorx account?
Two options.
Paul
No major problems Pascal, we’re just finishing up the documentation for the new features, and have a couple small bugs to fix, and then we’ll be good to go. We will give you a couple days notice before the release will be auto-updated.
Good to hear
The theme info is stored in the database now for each user, so there’ll be an “easy” way, but it’ll require running an SQL command to do it - I’ll see about making at least a command line way to do this without having to do it 100% manually via SQL.
Ok, so in fact, as I enter this theme as default in iworx.ini it is shown in the siteworx features account, but as long as I don’t “save” these feature the database isn’t updated with this theme for these users ?
So, it means that, by default, in the database the them for users is the default interworx one ? right ?
Ok
Thanks Paul
Hi
Here is the last modified FR language for v3.0.1. We’ve made some little corrections
Pascal
fr3.0.1.d.zip (81.2 KB)
I just noticed that account backups from NodeWorx do not work in this version.
Can you be a little more descriptive about the problem? How are you initiating backups? What exactly isn’t working?
On my server it works, both full and structure_only !
Pascal
I login to Nodeworx using the master account, then go to Backup / Restore under the SiteWorx menu. I check all of the boxes for each domain, and it says that the backups were successfully initiated, but nothing happens after that. It still says “No Backups.” I am choosing the option “Full Backup.”
Do you have large accounts on the box? The backup command gets executed in the background, so if you have large accounts that are being backed up, the display may not reflect new backups immediately. Try reloading the page every few minutes or so, and they should start appearing. Otherwise, open a ticket, and we’ll check it out.
Socheat