In short: Check authentication, content, sending reputation and recipient-side filtering. A message reaching Spam does not necessarily mean the server failed to deliver it.
Check the authentication result
View the message headers at the receiving provider and look for SPF, DKIM and DMARC results. Correct failures or alignment problems before repeatedly testing. Make sure every legitimate sender is represented in the domain's authentication setup.
Review the message
- Use a recognisable From name and a valid reply address.
- Avoid misleading subjects, URL shorteners and unnecessary attachments.
- Include a plain-text alternative in formatted mail.
- For marketing mail, send only to people who expect it and provide a working unsubscribe route.
- Do not test by sending the same near-identical message repeatedly.
Check account and domain reputation
Compromised mailbox credentials, old mailing lists and sudden volume changes can damage reputation. Reset exposed passwords, stop unauthorised sending and investigate the source before resuming normal mail.
Configure SpamAssassin for incoming mail
In SiteWorx, open Administration > Mail Options > Spam Settings. Prefer delivery to the Spam folder while tuning thresholds; immediate deletion makes false positives impossible to recover.
When asking for help
Provide the full headers from one representative message, the sender and recipient, timestamp with timezone, sending method and any bounce response. Remove message content that contains secrets, but preserve the diagnostic headers.
Further guidance
See the InterWorx guides for SpamAssassin settings and mail filters.
Unexpected mail from your account
If the mailbox is sending messages you did not create, treat it as a security incident rather than only a spam-placement problem. Follow I think my mailbox has been compromised — what should I do? before requesting reputation or blocklist remediation.
