First of all I love this module--I only hope I can get it to work.

I was able to send out an e-mail to one person but when I try to send an e-mail out to my entire list (about 170). It seems to process for a while (maybe 1-2 minutes) and then takes me to IE's default "can't find the page" message. As far as I know no e-mails were sent, but I can't tell for sure.

I checked drupal's logging system and there's no error.

I called my host (Bluehost but I know others have this policy) and apparently they have a limit on the number of e-mails that can be in the bcc field (10).

Any ideas?

Am I stuck with using something like phplist? (I hope not.)

Thanks.

-JV

Comments

jvinci’s picture

jvinci commented

I should have thought of this before, but I changed the limit on the number of recipients per e-mail to 10.

And this time I got a 500 server error. When I checked the logs in C-panel here's what is says:

SUEXEC error_log:
--------------------------------------------------------------------------------
[2008-11-17 22:03:47]: uid: (907/alumn) gid: (908/alumn) cmd: fcgiwrapper

Does that mean anything to anybody? "alumn" is my user ID for the webhost (I altered it since this is a public board).

Again, any help would be appreciated.

-JV

jvinci’s picture

jvinci commented

Despite the 500 Server Error a number of my e-mails were received (I estimate 30-40). I will check with my web host on the error.

jvinci’s picture

jvinci commented

Server error seems to have been caused by fastCGI, which (according to my host, bluehost) doesn't handle large files very well.

Now, the module seems to send out all 180+ emails, but now I'm getting an error that says (note I've replaced my domain or account id with "[mydomain]"):

Warning: MySQL server has gone away query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (15, 'php', 'MySQL server has gone away\nquery: SELECT * FROM node_type WHERE type = 'mass_contact' in /home/[mydomain]/public_html/portal/includes/database.mysql.inc on line 174.', 2, '', 'http://[mydomain].org/portal/mass_contact', 'http://[mydomain]/portal/mass_contact', '198.49.157.11', 1227549853) in /home/[mydomain]/public_html/portal/includes/database.mysql.inc on line 174

There were additional errors as well but they were similar to this one.

jvinci’s picture

jvinci commented
Title: Possible conflict with web host's Bcc field limit? » Script is taking too long and SQL is timing out.
Category: support » bug

Here's the response from my hosting company:

[this error] mean[s] the script is running longer then 60 seconds. With MySQL everything has to run within 60 seconds or the server will go away. So you need to find a way to make the page reload after every couple items being processed. See if your script has an option to send the items out in batches.

Any suggestions?

-JV

jvinci’s picture

jvinci commented
Priority: Normal » Critical

I've changed the Priority to Critical because, without some sort of page refresh mechanism, this module is unusable with hosts that restrict BCC recipients.

-JV

soccernyc’s picture

soccernyc commented

I too am having the same exact issue as jvinci. I am NO longer able to send out any emails without receiving the "500 server error". I too also have BlueHost. PLEASE HELP this module is vital to my online community.

scotese’s picture

scotese commented
Version: 5.x-2.4 » 6.x-1.0-beta2

This module was working fine until the last update - now I too receive the 500 Server Error.

soccernyc’s picture

soccernyc commented

Please help, I really need this module to work. 500 server error is unfixable.

slimgrin’s picture

slimgrin commented

I'm having the same sort of error: Page not found.

Some people on my list are getting it b/c I've had some replies but I didn't get mine...

oadaeh’s picture

oadaeh commented

@jvinci: Does this happen whether you save a copy as a node or not?

@scotese: the versions that were updated were 6.x-1.x-dev and 5.x-2.x-dev not the 6.x-1.0-beta2 version you set this issue to. Which version are you using? If you are using 6.x-1.x-dev, maybe you could try 6.x-1.0-beta2 and see if your problem goes away. If you are using 6.x-1.0-beta2, then it is on your end, as nothing has changed in that code since October 2008.

oadaeh’s picture

oadaeh commented

No responses in over a year. Is this still an issue?

oadaeh’s picture

oadaeh commented
Category: bug » support
Priority: Critical » Normal
Status: Active » Closed (cannot reproduce)