user registrations are queued...looking for a way to specify which emails to NOT queued
| Project: | Queue Mail |
| Version: | 5.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Great module....currently using it one a high traffic site but I found a small issue with this module.
This is maybe an oversight of the module (or not), but user registration emails are queued. I would have preferred user registration emails to be sent right away.
If I am a user, and I register on the site, I will get a confirmation message saying "your login information and further instructions have been sent to your email address". Naturally, I check my inbox and no email is there.
I know I can set cron to run more often, I have it running hourly, so the user will get the email within the hour. But as its a high traffic site (approx 40,000 page requests per hour), I don't want to overburden the server with running cron every 5 mins....unless you can suggest a better way.
Is there a way to specify what emails are queued? I am under the assumption that ALL emails are queued.

#1
That is the design: everything is queued.
We can change that to have priorities (e.g. "immediate", or "delayed").
Then the email key can be checked and assigned immediate.
But someone has to come up with a clean patch for this that is simple, readable and maintainable.
#2
I have attached a patch that does this.
I created an admin area at admin/settings/queue_mail where admin can set which $mailkeys they want to be bypassed. Admins can enter a comma separated list of $mailkeys
I tested and it seems to work but feel free to test it out and report bugs and ways to improve (especially in areas of performance and efficiency).
#3
Any chance of someone posting a version with this patch applied?
#4
How would the site admin know what keys to type in? They have to look at the source code?
We need a better way.
Also, if this has a D6 version, it has more of a chance of getting in, rather on being on the older version only.
#5
Also interested. Thanks.