Blocks ::: block_quickmail
Maintained by Buddy Ethridge, Robert Russo
A block that provides selective, bulk emailing within courses. Developed by LSU.
Latest release:
3442 sites
99 fans
Current versions available: 6

Quickmail is a block that provides selective, bulk emailing within courses.


  • Multiple attachments
  • Drafts
  • Signatures
  • Filter by Role
  • Filter by Groups
  • Optionally allow Students to email people within their group.


Quickmail adopts the same license that Moodle does.


Quickmail was developed at Louisiana State University.

Potential privacy issues

The Privacy API is not implemented in this plugin.


Screenshot #0
Screenshot #1
Screenshot #2
Screenshot #3


Buddy Ethridge (Lead maintainer)
Robert Russo: Lead Maintainer
Philip Cali: Former Lead Developer
jason peak: Former maintainer
David Elliott: Former maintainer
It's me!
Chad Mazilly: Former Maintainer
Please login to view contributors details and/or to contact them

Comments RSS


  • It's me!
    Mon, May 28, 2018, 9:42 PM
    Hi Robin and Barbara, which versions of Quickmail are you using?
  • Tue, May 29, 2018, 5:51 AM
    Hi Chad,
    Running v.1.7.5 (2017122000) here.
  • Fri, Jun 8, 2018, 6:03 PM
    Hi Chad,
    Hoping you could help. My institution are running a bespoke themed version of moodle 3.4 which has the administration block on the right instead of the left. Quickmail seems to bump our admin blocks off to the footer in all views other than the quickmail 'compose new email' view. This is only view that allows other blocks to remain on the page in the standard moodle theme (Clean) and our theme. The other quickmail views take up the whole page width and therefore seems to push off other blocks . Any chance that all views can be like the 'compose new email' view, to allow blocks to share the space?
  • It's me!
    Fri, Jun 8, 2018, 9:27 PM
    Hello K, I can certainly help. Which version of Quickmail are you using? Is it possible that you could send me a screenshot of the problem? If so, you can email it to me directly at cmazilly@lsu.edu if you prefer.
  • It's me!
    Fri, Jun 8, 2018, 11:01 PM
    Hey K, I'm under the assumption that you are using a Quickmail ~1.7-ish version. I've just pushed up a new update, v1.7.6, that should fix the issue you reported this morning. Please let me know if not!
  • Wed, Jun 13, 2018, 4:58 PM
    Hi Chad, sorry for the delay. I wasn't expecting you to reply so quick. Will email you the details.
  • Wed, Jun 13, 2018, 9:28 PM
    Hi Everyone, We have the same issue as Robin. All emails that go out via Quickmail are sent to respective email addresses. However they come in "from: noreply@domain.edu ". Any suggestion would be very helpful. Thank you.
  • Wed, Jun 13, 2018, 9:28 PM
    ps. We are on v.1.7.1
  • It's me!
    Thu, Jun 14, 2018, 12:13 AM
    Hey Robin and David, I think I may have found the problem. There is a setting in the "outgoing mail configuration" section called "allowedemaildomains". I did a test email send without this field populated and I received the email from "noreply@...". I then populated that field with the site's domain, sent another email, and the email came from the appropriate address "admin@...". I think the solution would be to add the domains that you want to whitelist in this setting and you should be good to go. Please let me know if not!

    Barbara, regarding your comment about emails only being sent to 25 users, this is a known issue in the current version of Quickmail. To get technical for a second, when you hit send email, the block will send out the emails synchronously (ie: looping through each one until finished at which point the "email sent" page will show). If you're sending attempting to send an email to 1000+ people, this could take some time and likely lead to a page timeout which cuts off any further action.

    We deal with this same problem at our institution, however, we've developed a newer version of Quickmail which fixes this problem by offloading the email sends to tasks which run in the background. Now when you hit send you will see "your email will be sent asap". Emails are processed as often as cron runs so there may be a short lag in the time it takes to actually send. I'd encourage you to try it out! It could be a great fit for your case and packs a few extra features. It is ready to go as-is but I'm still doing some development on completely new features and want to get that done before I officially release it here.

    If you would like additional info or have any questions please feel free to comment here or email me directly at cmazilly@lsu.edu and I can help.
  • Thu, Jun 14, 2018, 1:08 AM
    Hi Chad,
    Thanks! I was just about to post my findings out but looks like you beat me to it. Yes, this was something that was changed on Moodle's end in version 3.2/3.3? I forget which of how it handles email. Unfortunately, I have not yet found a way to use wildcard to whitelist all domains but have used wildcard to whitelist the popular domains (.com/.ca/.org/.net).
    Thanks again!
  • Thu, Jun 14, 2018, 1:51 AM
    I would not whitelist everything otherwise you'll get flagged by spam filters. Your domain should never send "from" other domains. It's generally frowned upon in the email community and will get you landed on spam lists.
  • Thu, Jun 14, 2018, 2:50 AM
    Thanks Robert, well noted.
  • Thu, Jun 28, 2018, 6:42 AM
    Hello everyone, first of all thank you very much for this very useful block.
    I ask you a question: is there a way to allow its use according to the type of email address that each user has? Example: only used by those who have gmail.
    From already thank you very much.
    Best regards.
  • It's me!
    Tue, Jul 3, 2018, 4:52 AM
    Hey Veronica, interesting request but I don't think this is something we would add in. One option would be for you to create a group of the specific users (those with that email domain) and then you could send to them explicitly.
  • Tue, Jul 3, 2018, 5:40 AM
    Hi Chad, thanks for your reply. But I'm referring to the user who uses Quickmail. For this issue of security policies I need to prevent it from being used by those whose account does not match the server.
    Thanks again.
Please login to post comments