Messaging: cron/messaging headaches

Messaging: cron/messaging headaches

by seinna gausman -
Number of replies: 9

hi!

nobody in our school is reciving notifications! i have looked through the moodle documentation and find it a little confusing to say the least as a newbie....i have had the hosting company set up cron for me and this is the code they set:

 

*/1 * * * *

/usr/bin/php /home/howtomak/public_html/academy/admin/cli/admin/cron.php 

 

this seems to be correct based on the documentation i saw, yet we are still not recieving notifications...can anyone shed any light on this for me? please? lol

 

thanks

Average of ratings: -
In reply to seinna gausman

Re: Messaging: cron/messaging headaches

by ben reynolds -

Hi Seinna,

Question 1: Do you mean that people are logged into Moodle, and, while logged in, they are not getting a message?

Question 2: Or, do you mean people are not logged into Moodle, and Moodle is not sending emails to those people?

If Question 2 = "yes," then you want to check (in 1.9) Site Administration >  Server > Email in (2+) Site Administration > Plugins > Message Outputs> Email to make sure you have set up email properly.

The documentation is here http://docs.moodle.org/22/en/admin/setting/messagesettingemail

In reply to ben reynolds

Re: Messaging: cron/messaging headaches

by seinna gausman -

thanks for your reply ben!

 

i am not sure what the "correct" settings should be! ;(

this is what i have so faar (cut and paste)

 

 

 
SMTP usernamesmtpuser
Default: Empty

If you have specified an SMTP server above, and the server requires authentication, then enter the username and password here.

SMTP passwordsmtppass
Unmask

If you have specified an SMTP server above, and the server requires authentication, then enter the username and password here.

SMTP session limitsmtpmaxbulk
Default: 1

Maximum number of messages sent per SMTP session. Grouping messages may speed up the sending of emails. Values lower than 2 force creation of new SMTP session for each email.

No-reply addressnoreplyaddress
Default: noreply@howtomakeadesignerhandbag.com

Emails are sometimes sent out on behalf of a user (eg forum posts). The email address you specify here will be used as the "From" address in those cases when the recipients should not be able to reply directly to the user (eg when a user chooses to keep their address private).

Character setsitemailcharset
UTF-8EUC-JPGB18030GB2312ISO-2022-JPISO-8859-1SHIFT-JIS
Default: UTF-8

All the emails generated by your site will be sent in the charset specified here. Anyway, every individual user will be able to adjust it if the next setting is enabled.

Allow user to select character setallowusermailcharset
Default: No

Enabling this, every user in the site will be able to specify his own charset for email.

Newline characters in mailmailnewline
LFCRLF
Default: LF

Newline characters used in mail messages. CRLF is required according to RFC 822bis, some mail servers do automatic conversion from LF to CRLF, other mail servers do incorrect conversion from CRLF to CRCRLF, yet others reject mails with bare LF (qmail for example). Try changing this setting if you are having problems with undelivered emails or double newlines.

 

any suggestions? Thanks!

In reply to seinna gausman

Re: Messaging: cron/messaging headaches

by ben reynolds -

Hi,

I don't see that you have set an SMTP host, which would be done in the very top box that isn't included in your c&p. The instructions for that box are

"Give the full name of one or more local SMTP servers that Moodle should use to send mail (eg 'mail.a.com' or 'mail.a.com;mail.b.com'). To specify a non-default port (i.e other than port 25), you can use the [server]:[port] syntax (eg 'mail.a.com:587'. If you leave it blank, Moodle will use the PHP default method of sending mail."

I suspect that, if you are counting on the PHP default method to work, your internal email is probably being stopped because it does not come from a trusted server. (BUT, I'm not an expert on these things.)

I would consult with whoever is in charge of your institution's email server to see if Moodle is sending messages that are being labeled spam and to get the SMTP server to work with Moodle.

In reply to ben reynolds

Re: Messaging: cron/messaging headaches

by seinna gausman -

wow..lol

i know some html/css stuff and i set this moodle school up, but i really dont know so much it could fill an ocean,lol. i dont know what a smtp host is or what smtp stands for. i will look for some moodle documentation that explains it all. jeeze, why cant anything simple, just be simple? lol

 

thanks thoughsmile

In reply to ben reynolds

Re: Messaging: cron/messaging headaches

by seinna gausman -

okay so i see that SMTP is:

"Short for Simple Mail Transfer Protocol, a protocol for sending e-mail messages between servers. Most e-mail systems that send mail over the Internet use SMTP to send messages from one server to another. In addition, SMTP is generally used to send messages from a mail client (or a program like Moodle) to a mail server."

great...

so now what? what would the address i enter into box one look like? as im sure its not my personal email or anything...is it the ip adress of my server? comnined with some other info? i just find this all so confusing with no clear directions written for somebody who is new to it!

In reply to seinna gausman

Re: Messaging: cron/messaging headaches

by ben reynolds -

Our smtp server is "smtp.johnshopkins.edu" So, you're looking for something like that. Call whoever is in charge of your email.

Yes, it is very confusing at first. The learning curve for Moodle is pretty steep, but you can do it!

In reply to seinna gausman

Re: Messaging: cron/messaging headaches

by Itamar Tzadok -

Try also the 'Support email' setting in site administration | server | support contact. If it's empty, entering a valid email address may do the trick without touching the smtp settings. The mailer looks for a valid address and if for some reason it can't read the default and the field is empty it declines the request. smile

Average of ratings: Useful (1)
In reply to Itamar Tzadok

Re: Messaging: cron/messaging headaches

by ben reynolds -

I just learned something new!

Thanks, Itamar.

In reply to Itamar Tzadok

Re: Messaging: cron/messaging headaches

by seinna gausman -

sorry i took so long to respond itamar but thank you so much for your help...we never did figure out how to make the cron go out automatically and we do it manually via the web...better than nothing, but we had other issues to deal with so I will be coming back to this and referring to your post.

 

thank you again for your reply!

 

all the best!