Hello Fellow CCK nuts,
We're using a form that collects data and then sends email to our company admin/s and the clinic. [ using Seblod CCK / Version 3.10.0 + J! 3.6.5 ]
It was sending email perfectly, but now has stopped sending a copy to the clinic.
In fact, it seems it only sends email where the recipient email includes the same domain as the site.
We're using SMTP and the config test email sends fine.
I may consider an upgrading Seblod and test on a copy of the site, but we didn't add any new components or make site changes -- and the client would not know how to.
Appreciate any suggestions to search far and wide, hi and lo
To be clear, when using fields to trigger emails, you use, e.g. "trf_clinician" NOT #trf_clinician# -- correct? which is what I have.
Ask your hoster if they changed their email sending policy, if it worked before something must have changed on the hosting side. If you are going to update your installation be aware that Joomla has stricter email rules in newer versions so you need to carefully examine your setup e.g. To and From addresses need both to be specified and they need to be different.
Klas, Is it allowed to trigger email for the following scenario?:
User fills out the form then Seblod CCK generates an email where the FROM email is the "user_email" field and the TO is: info@the-site-domain.com.
Thus in that scenario, admins monitoring info@the-site-domain.com could just reply to the User in their email client program.
For some reason, that form does NOT seem to be working. Thus, the question is... will Joomla (v. 3.6.5 in our case) allow an email generated that is NOT part of same the-site-domain.com? Or is that considered spam?
Thx much!
What you describe should work, there must be something that changed on the hosting side and is preventing it to work, I suggest you contact your hoster.
After some experimentation, it appears my versions DO pre-empt some emails from being triggered, perhaps by being labeled spam even tho they are legitimate. This must have happened with our last upgrade and admins didn't realize it until now.
The scenario I described above was not accepted by either Joomla or Seblod -- not sure. Perhaps it was deemed spam-spoofing.