There few CiviCRM extension that use third party to send bulk emails or transactional emails.
Alternatively there are many SMTP providers that provides good bulk mailing service like Sendgrid, CiviSMTP etc. Here is the list of SMTP providers that CiviCRM bulk mailings are supported.
My issue was with the resource URL.
Update the following file: example.org/wp-content/uploads/civicrm/civicrm.settings.php
Approx. line 82: $civicrm_setting['URL Preferences']['userFrameworkResourceURL'] = 'https://example.org/wp-content/plugins/civicrm/civicrm';
I had put an SSL certificate on via my host (SiteGround), just before this issue ...
Original Answer Below - New Answer: Siteground has created a number of rules and restrictions to avoid you using their services for bulk mailing. May be worth looking into another host.
The 80 recipients siteground is referring to is if you were to send an email with 80 recipients using traditional email. Thats not how CiviMail works - its sending all ...
Almost every time I've seen CiviCRM fail to load a portion of the screen, it's been a permission issue on the templates_c folder.
I can give the standard fix if you have command line access: Navigate into the templates_c folder and run chown -R <name of web user> . However, every control panel has a different way of handling this - and if the ...
You'll need database access and grant all permissions to the user 'pascrm49_drupa86'@'localhost' for the 'pascrm49_civicrm' database.
grant all on 'pascrm49_civicrm' to 'pascrm49_drupa86'@'localhost';
Theres probably an official direction somewhere but this is just to get you out of a bind if your civicrm install is broken.
I presume that you are talking about bulk mailings. I have got this working for small volumes hosted on Siteground. I had a lot of problems originally with subfolders though can't remember the details. My solution was as follows.
Outbound use mail() and in Administer>>CiviMail>>Mail Setting, set Mailer Batch Limit to 100 and Mailer Cron Job Limit to 1. With ...
This turned out to be something adding a blank line in the cron output (see comments above). Since it's not clear what is adding it or how to track it down, a workaround is to adjust the cron command slightly:
your-cron-command | grep "."
which will remove all blank lines from the output, so if the output is just a newline then after the grep the output ...