I have a somewhat unusual setup. My hosting provider disallows the localhost loopback so the only way I can set up cron to run is via a script which invokes the php parser directly to run cron.php
Since MailQ relies on $_GET['q'] or the request_uri() to determine if it should or should not declare its drupal_mail_wrapper() function, when my system runs cron, MailQ's wrapper gets in the way. The result is that emails are never sent but are continually re-queued with a blank mailkey.
My fix is the attached patch for others in the same situation I'm in, but I'm also wondering you can think of a better fix. Otherwise, thanks for the great module!
Comments
Comment #1
joausaga commentedsuscribing
Comment #2
zyxware commentedCan you please try the latest release - http://drupal.org/node/1333638. You will have to uninstall the existing module and install the new version as there is no upgrade path as it is.
The 2.x branch is a rewrite in that it uses a different strategy to handle the queued mails and no longer uses $_GET['q'] to identify if it is a cron run.
Comment #3
anish_zyxware commented