After importing some sites with email, I noticed I was getting [SPAM] in the subject even though that was turned off. Looking at the new server the settings did match the previous server already, so all I did was hit the Submit button on the Spam Settings page and that fixed it.
My only guess here is the settings are being copied to the IW Database, but not actually pushed to the config file that control the email.
Helloâ
Can you provide a few more specifics regarding âeven though that was turned offâ? What, specifically, was turned off? Spamassassin in the SiteWorx account? The âRewrite message subjectâ setting? I will need to be able to try to reproduce, but Iâll need as many details a you can provide to be able to attempt doing so.
Thanks,
-Jenna
This is on the Spam Settings page (/siteworx/email/spamprefs)
Specifically what was âturned offâ was the âRewrite Message Subjectâ option.
It was set to âDo not change the message subjectâ.
I was getting stuff in my Spam folder with [SPAM]. So I went to the settings page on the new server to fix it, but realized it was already set correctly. Iâve had issues with copying wordpress sites with themes to new URLs and just opening the page and saving it fixes the issue, so I decided to give that a try here.
So I literally changed nothing on the settings page and just hit Submit and then the emails started coming in without [SPAM] after that.
Iâm not sure if that was the only setting not working, but that is the one I noticed.
Let me know if you have any more questions or any info I can provide.
Another related item to mail settings I just noticed, definitely fluke kind of random one, but thought I would share just in case it could help. This only affected one domain, so I think it has something to do with the fact that it has a pointer domain.
Source Server Remote Setup:
secondarydomain.com - Pointing to primarydomain.com - DISABLED
primarydomain.com - SiteWorx Account - ENABLED
âŚAfter Mass ImportâŚ
New Server Remote Setup
secondarydomain.com - Pointing to primarydomain.com - ENABLED
primarydomain.com - SiteWorx Account - ENABLED
Helloâ
What is disabled? Spamassassin?
Thanks,
-Jenna
Local Delivery Status under Remote Setup.
Iâm having an issue reproducing the [SPAM] bit (mostly because Iâm having an issue getting a spam message, but I was able to reproduce the pointer local mail bit, so Iâll submit a bug report for that, and fuss with the [SPAM] one a bit more. Thanks for the info! 
Lucky you, Iâve received 300 spam emails to the email in question in the last two weeks!
What if you just set your spam limit to like 1 (or less) to force it to trigger on a normal email?
Helloâ
Thatâs what Iâve been trying, lol. With fake accounts, it can be a bit of a pain. Iâm still trying some things, just wanted to let you know I was able to reproduce and created a bug report for the one thing you mentioned, while I continue arguing with my server(s, since itâs an import) for the other bit.
Thanks,
-Jenna
I was finally able to send myself some spam messages but I was unable to reproduce the issue you experienced.
I did find a bug where, after import, all of the settings under SpamAssassin Configuration revert themselves to the default on the Destination server (which is that [SPAM] is not added to the subject). So Iâm going to make a bug report for that.
However, after the import, spam messages sent to the Destination server did not have [SPAM] added to the subject, so that bit I was not able to reproduce at all.
Were you able to see that if you setup some specific spam settings they didnât carry over to the actual email system, but did show correct in the SiteWorx Spam settings page?
It seemed like mine reverted to default (and [spam] as default somehow), but when looking at that spam settings on the SiteWorx account itself, it was set to off.
So the setting showing in SiteWorx did not match the underlying configuration.
Then I hit the Submit / Save button and it did.
What I saw was that the settings were reverted back to default after import. Adding [spam] to the subject is not the default setting. The default setting is to not rewrite the subject.
I was never once able reproduce [spam] randomly added after import.
How I tested my actual findings is that I made changes to every setting and then did the import.
So this was the source:
And the destination:
The behavior after import matched the default settings listed on the Destination server.
Note: the above screenshots are from a different test than testing if [spam] was added after import. While I was trying to test the [spam] being added bit, I noticed that my change of making the spam threshold 1 didnât come over, so I did this test separately. Thatâs why the Source bit shows [spam] rewriting as enabled.
Did having [spam] randomly added after import happen with multiple accounts or just one/a few?
Thanks,
-Jenna
Out of curiosity, what browser do you use?
We just found a bug where Chrome shows the default settings, no matter what the settings actually are.
So if youâre using Chrome, it is possible that the settings on both the Source and Destination servers were set to add [spam] to the subject, and you just couldnât see that because Chrome always just shows the defaults. So the behavior was correct, the GUI in Chrome was just broken.
Thanks,
-Jenna
Did having [spam] randomly added after import happen with multiple accounts or just one/a few?
It happened on my two accounts I use myself. I have not moved any other accounts that have email yet. So maybe Iâll add an account for me on the current server with these other SiteWorx accounts so I can test how it works after move on these as well.
So if youâre using Chrome, it is possible that the settings on both the Source and Destination servers were set to add [spam] to the subject, and you just couldnât see that because Chrome always just shows the defaults. So the behavior was correct, the GUI in Chrome was just broken.
That wasnât the case for me because I was not getting [SPAM] in subject until after I moved to the new server.
Old Server
[SPAM] showed turned off on browser and DID NOT add spam to spam messages
New Server
[SPAM] showed turned off on browser and DID add spam to spam messages
I literally didnât even change anything on the new server, I just hit the Submit button to save what was on the screen already there and then the [SPAM] stopped being tagged on message.
Darn, I was hoping that could have been the issue. I still canât reproduce any kind of erroneously adding [spam] after import, though, so that bit does not seem to be systemic.
Iâll let you know how my future tests go and if Iâm able to reproduce again.
I think the only non-default setting for this account is the Custom score of 2 which did not copy to the new server. Also, like before on my other accounts, the Rewrite message shows to not put [SPAM] yet itâs adding it into the email anyway.
Also, a bigger issue that I didnât notice before, but guessing happen to the other accounts, most the Advanced SpamAssassin Custom Options didnât copy. The type Domain did, but all the user level ones are not showing anymore.
Are these supposed to copy over?
This appears to be a display issue on this page. It looks like a recent change (since 7.13.44) caused the query that we use to populate this page to default to grabbing the global settings instead of the individual settings for the domain.
The submission of the settings still only apply to the account/domain itself. So the bug only affects the values that originally populate the fields. We have a fix submitted for this issue.
The only part that weâve been entirely unable to reproduce is the appearance of [SPAM] on newly migrated accounts. Do you have [SPAM] set as the âRewrite Header Subjectâ in the global settings in NodeWorx? How to: Configure NodeWorx Spam Filtering â InterWorx documentation
I do not see anywhere where we are copying the user level configs in a backup, so their exclusion may be expected. I will double check this on Monday when I return to the office. If my additional testing shows that those do not get copied over, I will submit a feature request for such functionality (though obviously cannot promise any timeline on its completion).
Oh, this is a good thought on the global setting since this would be whatever default was setup when InterWorx was installed on the new server.
I see on /nodeworx/mail/spam under SpamAssassin Options the Rewrite Header Subject option is blank. There doesnât seem to be an option to disable / enable it, but it is blank. Looking below under the Advanced SpamAssassin Custom Options I see rewrite_header subject with scope global and the value is just empty, nothing there.
Should I try just deleting that completely from the Advanced area?
On the user level configs, that seems like a good idea to copy that, if there isnât some underlying reason that makes it more complex than is seems to do that.
The default âRewrite Header Subjectâ should be an empty value, so it sounds like youâve not changed anything.
Unfortunately, as I mentioned, I was not able to reproduce the issue where [SPAM] was added to subjects after migrating an account to another server and the account did not previously have that setting. If you still have the old server available, can you submit a ticket to the support desk (even though you donât qualify for direct support) and give us access to a server (via remote assistance) where the backup could be obtained by us? Iâd like to check the backup itself and see what it contains.
Weâll try again to reproduce once the office opens again tomorrow and let you know.
