I enabled flagging for forum comments and after flagging a comment, the following error message shows up: Unable to send e-mail. Please contact the site admin, if the problem persists.

Thanks,
Gene

Comments

vm’s picture

at the top of an issue creation you have this note:

If you are reporting a bug, it needs to consist of three things:
What are the steps required to reproduce the bug?
What behavior were you expecting?
What happened instead?
Please include as much information as you can: OS, webserver name and version, PHP version, Drupal version, Drupal path, and everything else you might feel is relevant. There is no such thing as a bug report that is too detailed.

While what you've posted indicates the problem you are having it doesn't explain anything about the server OS that is in use.

version of PHP
version of Apache

is this on a live server ? or on a local machine ?

JacobSteelsmith’s picture

Just looking into this a bit.

It looks like this error is coming from mail.inc on line 135 from the drupal_mail() function. The drupal_mail_send() function is called from drupal_mail in this case, so the error is actually generated based on the value returned from drupal_mail_send().

If the installation uses a custom mail backend, the function drupal_mail_wrapper() can generate this error. I can't find this function or any documentation on it.

If the installation does not, this is being generated from php's mail function. It might be useful to create a php page that uses mail() directly. You might also check Admin -> Logs -> Status Report and click on your php version number to view phpinfo(). Look for mail settings and post those.

genelu’s picture

Oh, sorry about that. Noob error. :)

Steps to recreate error: 1) Install Flag_Content - 6.x-1.x-dev 2) leave a comment to a forum topic 3) Click on "flag this" 4) Error
Behavior Expected: After clicking on "flag this", I was assuming that there would be feedback confirming on item being flagged.
What Happened Instead: Error message reading > Unable to send e-mail. Please contact the site admin, if the problem persists.

Here's the rest of the information in regards to my install and yes, it's on a live server:
Drupal 6.0
Access to update.php Protected
Configuration file Protected
Cron maintenance tasks Last run 1 day 8 hours ago
You can run cron manually.
Database updates Up to date
Drupal core update status Up to date
File system Writable (public download method)
GD library bundled (2.0.34 compatible)
Module and theme update status Up to date
MySQL database 5.0.45
PHP 5.2.5
PHP memory limit 128M
PHP register globals Disabled
Unicode library PHP Mbstring Extension
Update notifications Enabled
Web server Apache

kbahey’s picture

Are you sure this is not a server-wide/site-wide issue?

Can other modules send email? I mean when a new user registers, or when the contact form is used?

genelu’s picture

I just created a test account using my gmail and the welcome email came through.

Also, just wanted to make one more note about this issue: Even though I get the error message "Unable to send e-mail. Please contact the site admin, if the problem persists.", the following message follows "The comment was flagged for the administrator". Hope that helps...

dries arnolds’s picture

I've got exactly the same problem as Genelu. My server has the almost same specs. I'm running multiple websites with Drupal 6 that don't have the issue. It seems to be isolated to Drupal 6.

Other mail functions work well.

zilla’s picture

any resolve on this? i was just about to put this module on my drupal6 install until i hit this thread and saw that the issue was still open...

garg_art’s picture

Drupal 6.1
I have the same problem on my flag-content implement. Have to disable it now.

zilla’s picture

bummer. any luck figuring this out? i don't know enough about the module myself, may try to install later and isolate the error if possible...

are there any errrors isolating files or file lines in the logs for people experiencing this?

kbahey’s picture

Status: Active » Fixed

Fixed. Wait for tomorrow's tarball of 6.x-1.x-dev.

zilla’s picture

thanks!

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.