Hey Angelo,

Yes, that was correct

You can see your server response already shown connected and saved when run the cronjob.

May i know your user is it still can't get the email notification when new post is published?

Hi. Arlex,

I do not understand your question:
'May i know your user is it still can't get the email notification when new post is published?'

The email notification after posting do go out. I have received them. However, I do get a notification of the cronjob though, every time it is executed:

--2015-09-21 15:00:06-- http://myjoomla.com/index.php?option=com_easyblog&task=cron
Resolving stargue.com... #.#.#.#
Connecting to stargue.com|#.#.#.#|:80... connected.
HTTP request sent, awaiting response... 303 See other
Location: http://myjoomla.com/en-us/?option=com_easyblog&task=cron [following]
--2015-09-21 15:01:19-- http://myjoomla.com/en-us/?option=com_easyblog&task=cron
Reusing existing connection to stargue.com:80.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/x-json]
Saving to: `/dev/null'

0K 63.8M=0s

2015-09-21 15:01:21 (63.8 MB/s) - `/dev/null' saved [640]

The statement use for the cronjob is:
/usr/bin/wget -O /dev/null "http://myjoomla.com/index.php?option=com_easyblog&task=cron";

I am assuming the -O /dev/null is to sent the output (the text above) to /dev/null and thus I should not get an email as mentioned above. Or should I use this '>/dev/null 2>&1' instead of '/dev/null' or put '>/dev/null 2>&1' at the end of the cron statement as well?

Thank you for your assistance in advance.

Best regards,
Angelo.

Hello Angelo,

You should put the > /dev/null 2>&1 at the end of the cron statement. Please give it a try.

Thanks Nik. It seems to be working. So the full cron statement is:
/usr/bin/wget "http://myjoomla.com/index.php?option=com_easyblog&task=cron"; > /dev/null 2>&1

Best regards,
Angelo

You're welcome, glad to heard your issue resolved.