2 Has anyone gotten email to work? 3 Jim Michael posted 10 Years Ago I have so far been unable to get Rock to send communications via our Sendgrid account (port 587, SSL, smtp.sendgrid.net, correct credentials). The communication says it has been "queued" but never arrives at SendGrid. What's curious is that Rock exceptions ARE being emailed via SendGrid, so the setup seems to be right... it's just that Tools | New Communication does not work for me. Also, not sure if this is related but I don't understand the relationship between Admin Tools | Communication Settings | Communications Transport | SMTP settings (where my SendGrid info shows up) and Admin Tools | General Settings | Global Attributes (attributes 75-79) which appear to be SMTP-related but in my case are not set to my SendGrid credentials or port. I DID try setting these to the correct SendGrid values without any effect. (I also discovered a repeatable exception... if you edit either SMTP User Name or SMTP Password here, then try to edit SMTP Use SSL attribute, it throws an exception)
Ken Roach 10 years ago Chris, can you please confirm which version of the beta this fix will be included in?I still have pending emails with version Rock McKinley 0.3 (beta).
David Turner 10 years ago With version 0.3, your new emails should be working. If you still have pending emails sent prior to updating to v 0.3, take a look under Admin Tools > System Settings > Jobs Administration and make sure the 'Send Communications' job is active and configured correctly.
Jim Michael 10 years ago My experience with this is that v0.3 fixed the issue and new communications go out fine, but the ones that had already been queued prior to 0.3 (about 10 messages) never went out and still say pending. I just chalked that up to them being "stuck" from the prior bug.
David Turner 10 years ago The "Send Communication" job does have an "Expiration Period" setting that determines how many days back a send will be attempted. By default that is 3 days, so if your communicaiton was created more than 3 days prior to the job starting to run (v0.3 update), those would not get sent.