Hi there,

Thanks for the great module! Love that you can control how many messages to send at a time and the max attempts feature!

I was wondering if it's possible to do different actions based on different message types.

For example, we have mail coming from several sources:
* Contact form (Webform)
* Private Msg
* Views Bulk Operations - mass email

We'd like to send the private messages and contact form notifications right away, but queue up the views bulk operations emails because it's 100s at a time.

Thanks,
Andrey.

Comments

mr.andrey’s picture

mr.andrey commented

I just did a test run on one of our live sites, and unfortunately, without this feature, the module is unusable for us.

Problems:
* If someone sent a password reminder request, and because it was queued on cron, they will not get it for a while, and try it again, getting spammed by 10 password reminders afterward.
* Private Message could be read, and afterward, the user gets a notification for a "new" message that they already read.

Disabled the module for now.

I hope the selective queue feature will come into existence.

Best,
Andrey.

alxsvdr’s picture

alxsvdr commented

It's a great module. I also tested it for a couple of hours. I can't use it right now because we require some mails to be sent immediately: user registration, password reminder, and contact forms.

Best,

A. Saavedra

kriskd’s picture

kriskd commented

+1 for this feature request.

mrbubbs’s picture

mrbubbs commented

I'm thinking of implementing this for my site. The problem I'm having is how it should work.

My site only needs mail queueing for one section, which sends notification email for new forum posts. Anywhere else on the site that needs to send mail (e.g., password reset requests) would be okay to send mail immediately, as it would not be sent to a bunch of users.

Based on my site setup, I am going to modify MailQ to do the following:
- Look for the message to contain the params array (from drupal_mail). If there is no params with a key of mailq_priority, then don't add the mail to a queue, and send it out as normal with whatever mail wrapper is in use.
- If the message has a params key with mailq_priority, whose value is one of PRIORITY_LOW, PRIORITY_NORMAL, or PRIORITY_HIGH (MailQ priority names). then queue this email, with the specified priority.

This unfortunately requires modifying any modules sending email that needs to be queued. I'm okay with that, though. Maybe there is a better way for MailQ to determine if the mail should be sent immediately or queued. If so, please share!