notification emails end up in SPAM

[Aurélie Grignard]

Hello,

Every single email that IP board send to my member with a notification ends up in SPAM.

Even if the members have my email in their whitelist and even if they receive all the others email I send to them...

Still every single email from IPBOARD ends up in the SPAM folder.

What can I do to improve the delivery ?

Notification is key for the engagement on the forum and for my retention rate.

I really need to solve this asap.

thanks

 

[Randy Calvert]

This is an issue you need to address with whomever is hosting your mail. In most cases it’s because you don’t have SPF and DKIM setup, however that is outside of the IPB software. 

[Aurélie Grignard]

thank you @Randy Calvert

my SPF and DKIM is setup.. and I have a good delivery with my CRM.. the only emails that goes in spam are from IPBOARD

[Aurélie Grignard]

and also, while in the spam follower, there is an additional warning saying "this message content remote content"

 

[Randy Calvert]

Remember… IPB does not actually control delivery of email. It simply passes it to whatever outbound service you use. They control delivery of messages. You’ll need to work with whatever that service is. 

You might try sending via SMTP if your host allows it.  Only your host can tell you what the best way for you to be sending mail is. 

Edited December 16, 2022 by Randy Calvert

[Marc Stridgen]

You would need to contact your mail provider on this, to ask them to advise. While we send the email, we have no control over the actual email its sent from, nor the receiver

[gigantor]

5 hours ago, Aurélie Grignard said:

thank you @Randy Calvert

my SPF and DKIM is setup.. and I have a good delivery with my CRM.. the only emails that goes in spam are from IPBOARD

 

Are you relaying the email or sending directly?

It sounds like your SPF/DKIM does not include your IPBoard server's IP or selector.

 

[Marc Stridgen]

34 minutes ago, gigantor said:

 

Are you relaying the email or sending directly?

It sounds like your SPF/DKIM does not include your IPBoard server's IP or selector.

 

Im not sure why you believe it would need to include our IPs there?  This would be the case only if cloud hosted

[gigantor]

I meant his server IP on the SPF record.

Edited December 16, 2022 by gigantor

[Marc Stridgen]

17 minutes ago, gigantor said:

I meant his server IP on the SPF record.

Of course 🙂 

[gigantor]

17 hours ago, Marc Stridgen said:

Of course 🙂 

I keep forgetting that you guys are now hosting too...

 

[Marc Stridgen]

On 12/17/2022 at 5:38 AM, gigantor said:

I keep forgetting that you guys are now hosting too...

 

A few decades now 🙂 

[Lindor]

On 12/16/2022 at 11:26 AM, gigantor said:

 

Are you relaying the email or sending directly?

It sounds like your SPF/DKIM does not include your IPBoard server's IP or selector.

 

 

On 12/16/2022 at 12:24 PM, gigantor said:

I meant his server IP on the SPF record.

 

On 12/16/2022 at 12:41 PM, Marc Stridgen said:

Of course 🙂 

This settings will should be in the Help Guide! I has many tickets for this problem and is the first time that read this requirement.

[Jim M]

24 minutes ago, Lindor said:

 

 

This settings will should be in the Help Guide! I has many tickets for this problem and is the first time that read this requirement.

This is an email/hosting side issue rather than a software issue so while I understand your frustration here, your hosting/email provider should have instructed you about this when connecting with them over spam issues. We could add a reminder in the guide to talk with your hosting/email provider about spam issues but certain configurations like this would always be up to the hosting/email provider and something we cannot provide support for.

[Lindor]

14 minutes ago, Jim M said:

This is an email/hosting side issue rather than a software issue so while I understand your frustration here, your hosting/email provider should have instructed you about this when connecting with them over spam issues. We could add a reminder in the guide to talk with your hosting/email provider about spam issues but certain configurations like this would always be up to the hosting/email provider and something we cannot provide support for.

Well, for PayPal or Stripe connection you have a complete guide, the email is another one connection. I agree that you can't provide all hostings settings but you should create a list of IPS requirements to make functional the SMTP email setting.

[Jim M]

57 minutes ago, Lindor said:

you should create a list of IPS requirements to make functional the SMTP email setting.

Unfortunately, these aren't "IPS requirements", these are global email server requirements. Your email is being rejected by other email servers because your server is not authorized to send mail for your domain. We are actually successfully passing the email onto your email service and your email service is encountering the issue.

That is the difference between the PayPal/Stripe integration and Email. PayPal/Stripe have exact settings to work with our software. Whereas, realistically, the email server settings should be setup by your email/hosting provider already just to send any email from the service. It isn't a 1:1 integration like PayPal/Stripe so it isn't a one size fit all solution to resolve a spam issue.

However, your suggestion is heard and we can see what we can do to help clarify this in our guides.

[red power magazine]

We also have issues with notification emails being marked as spam. Our troubles also started about December 14. So much so that our host, SiteGround, shut off our email service. The SPF/DKIM was already setup on our server. 

[Jim M]

1 hour ago, red power magazine said:

We also have issues with notification emails being marked as spam. Our troubles also started about December 14. So much so that our host, SiteGround, shut off our email service. The SPF/DKIM was already setup on our server. 

You would need to contact your hosting or email provider to help you resolve the issue.

Email recipients marking your emails as spam is different than email servers blocking your emails due to lack of authorization. Recipients marking them as spam may be related to the content which is being sent or at worst, someone obtained your SMTP/server credentials and sending spam out via it. If it is the latter there and a great quantity is being sent, that could be why they disabled email sending.