Form Block :: Use SMTP instead of PHP Mailer

Permalink
Even when I set email settings to SMTP in administrator area, the built in form block does not use SMTP to send the email. Atleast not as far as I can tell, because the emails still end up in spam. How can I stop emails from the built in form from ending up in spam?

On my own php mailers, I would make sure to post the FROM header as the site that was sending it, and this stopped alot of clients from marking it as spam for spoofing the from header. Shouldn't sending SMTP solve this, so that email is not marked as spam? As far as my understanding goes, sending mail SMTP means it won't be marked as spam, but perhaps I am misguided there.

So does the built in form block send using SMTP if its enabled?

ob7dev
View Replies:
ob7dev replied on at Permalink Reply
ob7dev
Update :: I see that changing the global mail settings does reflect the forms. I see that the SMTP settings work and I receive the test email send via SMTP when I test it.

But on my form, made before I set up SMTP, it gives an error. It does this only after switching to SMTP, as it sends fine using PHP mailer. The form errors out with: No Data received ERR_EMPTY_RESPONSE. Any ideas what this means?
ob7dev replied on at Permalink Reply
ob7dev
Yet another update: When I make a new form, it sends SMTP email just fine. For some reason my form created before SMTP was enabled does not send.

Final Update: OK I cleared cache and original form sends SMTP mail as well. So everything is working how it should, just needed to clear my cache.
mesuva replied on at Permalink Reply
mesuva
If you're flicking it over to SMTP and you're then finding the email in some sort of spam folder/filter, then concrete5 is successfully using SMTP to send the email.

But it's not as simple as using SMTP to avoid being marked as spam, there's a whole host of reasons why emails could still be picked up.

To name some:
- The actual SMTP server sending the email should be 'authoritative' to the domain name it's sending for. Often domains have a thing called an SPF record, which indicates what IP address are allowed to send emails. If your domain has one of these records but you're sending it from a different IP address there's a very high chance it'll be flagged as suspicious.
- The server IP address could be listed on a spam database as being particularly spammy. Spam filters will refer to these lists. If it's a shared server, some other user on the server could be sending out lots of spam, making the server look bad.
- The email message itself could look like spam, particularly if it's got certain keywords in it
- Depending on how you're viewing the email account, your email software itself might see the email as spammy and automatically move it between email folders.
ob7dev replied on at Permalink Reply
ob7dev
Thank you for your reply. So it turns out I just needed to clear the cache to get the form to work properly. Everything looks to be running smoothly. I appreciate your valuable feedback.

Thanks,
David
JohntheFish replied on at Permalink Reply
JohntheFish
For anyone with tough mailer requirements, recently approved is:

http://www.concrete5.org/marketplace/addons/mail-service-integratio...