There are many factors that are commonly used to determine spam weight, and they vary from system to system. It is difficult to say without knowing which system performs the classification and the factors that the system uses, and an example message.
However, the easiest way to look for a developer to check is the reliability of the message. If you have an HTML message - is it built correctly? Is there a text alternative part of the message? Is the content type correct? Having a poorly designed message can usually add weight to spam.
Also look for probable flags, such as inline javascript inside your message content ... which I would assume is a universal trigger. HTML letters should usually be composed using plain old HTML without a lot of bells and whistles.
One approach that you always need when developing email is to send the message to different systems such as GMail, Yahoo, HotMail .. and see the message headers yourself. Inside message headers, there are usually some tips to help you determine why it has been flagged as possible spam.
There are ways, as a rule, outside the control of the developer, how to reduce spam weight, and also about what you should know ... SPF records are probably the most common quick add-on that your IT guys should do, then domain keys, white lists, and many third parties who want to take your money to confirm your messages.
Good luck
source share