Developer forum

Hi,

Additionally to this post: until last week we never had problems with this, that's why we are wonderingen if there where any changes at your side.
Hope we can find a solution together.

Best regards
Gerard

Hi guys

It might be related to the SMTP that you are using. It can be reported as a spam host. When sending out newsletters, people will report the mail, and if done enough, the SMTP will be reported as a spam relay - you can check if your current SMTP server is active in databases at various services, this one as the most popular: https://www.spamhaus.org/lookup/

It is a good idea to use services like SendGrid for distributing newsletters - they have teams and services monitoring potential spam reports.

Also wording, missing spf records and other things can be the cause. But it depends on the receiving mail service what rules they aplpy and why things get marked as spam. But usually it happens because the mail looks a lot like spam.

BR Nicolai

Hey,

We tested the mailing quite often to make sure it arrives in the correct mailbox. Althought it looks like the mailings goes to spam only for the e-mail domains that we used for the intensive testing. 
Can it be that due to testing the mailing arrives in spam for the hole domain ending on @inextenzo.com for example?

If the from domain in the mails does not have SPF records endorsing the sending SMTP, they will have a chance of being marked as spam.

So you cannot test with another domain in the from address than you want to go live with without ensuring the right SPF records.