When using SMTP you would have to uncomment and change
//$CONFIG->emailer_transport = 'sendmail';
to
$CONFIG->emailer_transport = 'smtp';
I think it won't use SMTP otherwise at all regardless what you have set in the $CONFIG->emailer_smtp_settings array. As for the values in the array are you using the very same you have used with the plugin before on the older Elgg version? Connection class might be 'plain' instead of 'login'. And you might also have to define 'ssl' and 'port' (twice?) depending what the smtp mail server requires. I never tried SMTP myself so I can't give any other first hand advice.
As for sendmail it shouldn't be necessary to make any settings at all as long as sendmail it correctly set up on your server. If the test works as explained in the docs but no email notifications are sent on site I wonder if you use an email address as site email that's not matching your domain. In this case sendmail might block it (as anti-spam measure). There's also the question if the receiver of the email notification has enabled emails as allowed notification method in his notification settings. In case of verification emails the question is if the email goes out but gets blocked somewhere on the way to the receiver or ends in the spam folder of the receiver.
Well, I managed to get sendmail to work. I probably had messed up some comment line.
But out of curiosity, I tried every SMTP setting I could and didn't get it to work. 'plain' and 'login'; ssl and not ssl; different ports etc.
also tried different combinations of uncommenting/changing the $CONFIG->emailer_transport = 'smtp';
and $CONFIG->emailer_sendmail_settings = '';
Anyways, sendmail is working now. Thank you!
So now again Elgg doesn't send any emails. I've tried to send several validation emails and notifications into many different addresses and different domains. None come through or go into Spam-boxes.
I'm using Sendmail because SMTP wouldn't work at all.
The email test http://learn.elgg.org/en/stable/appendix/faqs.html?highlight=email#missing-email
is again working just fine.
In the meanwhile I've upgraded Elgg 4.1 into Elgg 4.1.1. Might that have caused problems?
You have the following options:
1. In your custom plugin, register an event handler as on example below
elgg_register_event_handler('update', '<entity type>', '<my_event_listener>');
function my_event_listener($event, $object_type, $object) {
// add code for notification on river
}
2. Unregister the "pages/edit" action and register your own, so you can include any changes you wish.
But I should suggest the 1st solution
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.