Not sending emails
drupler - February 12, 2008 - 14:12
| Project: | Case Tracker |
| Version: | 6.x-1.0-beta3 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | zero2one |
| Status: | closed |
Jump to:
Description
I'm using 5.x-1.3-beta1 and everything seems to work except it is not sending emails. CT Mail is enabled, I get other Drupal mail messages fine, but I don't receive any updates from this module. I also don't see it trying to email in the log file (not sure if it would anyway) What am I doing wrong?
#1
Same problem here, emails are working for other modules & Drupal, but not for CaseTracker. And at the exim log, I don't send any try.
#2
It's not sending either after an update...
#3
Maybe nodeapi should simply add 'update' on the switch statement:
<?php
/**
* Implementation of hook_nodeapi().
*/
function casetracker_mail_nodeapi(&$node, $op, $teaser = NULL, $page = NULL) {
switch ($op) {
case 'insert':
case 'update':
if (in_array($node->type, variable_get('casetracker_case_node_types', array('casetracker_basic_case')), TRUE)) {
casetracker_mail_send($node);
} break;
case 'delete':
if (in_array($node->type, variable_get('casetracker_case_node_types', array('casetracker_basic_case')), TRUE)) {
db_query('DELETE FROM {casetracker_mail} WHERE nid = %d', $node->nid);
} break;
}
}
?>
#4
I have carried out this modification, but still cannot get CT Mail to send emails. Any more thoughts?
#5
Currently CT mail it's not sending email update to the currently comemnting user (around line 175 on casetracker_mail_send). We change this commenting the line as follow:
<?php
while ($result = db_fetch_object($results)) {
// if ($result->uid == $user->uid) { continue; } // don't fire to currently commenting user.
if (!$result->mail) { continue; } // don't fire blanks.
// if we get here a mail is send
$mail_status = drupal_mail('casetracker_mail', $result->mail, $subject, $body, $from, array('Message-ID' => $msg_id));
if (!$mail_status) { // mail failure doesn't actually tell us much, since PHP returns no error string, but hey, feel good, right?
watchdog('casetracker_mail', t('E-mail notification failed for %address.', array('%address' => $result->mail)));
}
}
?>
#6
The CaseTracker module sends e-mail notifications only to assigned user & case-creator user if the currently updateing/commenting user is not one of them.
I added support for case & comment modifications (updates).
The changes mentioned here didn't work because there was an missing $ before a variable.
This is fixed in the latest cvs (http://drupal.org/cvs?commit=105059)
Don't use the -dev release.
That release is not well done by the previous maintainer.
Can somebody tell me how to remove a bad dev-release and create a good one?
#7
Automatically closed -- issue fixed for two weeks with no activity.
#8
Hi... I am using casetracker-5.x-1.3-beta1 as "Recommended for 5.x"... and I seem to be having this same problem-casetracker doesn't seem to have email capability despite all modules being correctly installed. This issue was closed as fixed-please forgive if this was incorrect but I reopened-do I need to figure out how to fix from CVS or...? If I do need to get this from CVS, can anyone point me in the right direction re: how to do that?
Thanks...
CDB
#9
I'm using the dev version here and emails are send.
Are other emails send (contact, ...)
Maybe there is a problem with the outgoing smtp server.
#10
I've tried the recommended beta version and the dev version and neither will send emails. Also using OG which sends properly; not sure if there's a known conflict I'm unaware of. Any ideas? Seems like this is a recurring issue (or at least it's popped up again)
#11
I too am on 5.x-1.3-beta1 and it is not sending emails, to anyone. My Drupal site sends mail using the notify module just fine if it is turned on. This used to work and suddenly quit. I upgraded to 5.x-1.3-beta1 in the hopes it was fixed. Still no joy.
gil
#12
Hi Zero2one and thanks for the reply and your work on this module. I found that emails were being sent but only for comments-not for example on status updates-and only to the party NOT making the comment as you mention above. Is the module supposed to be sending emails on other types of updates? I have read posts on drupal.org that seem to imply both that it is and that it isn't. I really need to be able to send the case creator an email automatically upon status updates. Is this possible?
Thanks again.
#13
Yup, same issue here. Emails not going out on status update.
Best to all and thanks for the work.
Dan
#14
I seem to recall running this module some time ago and seeing a CT Mail when I looked in Admin/by-module. It's not there now. Do I remember that correctly?
#15
did anyone get this working? Same issue in that CT Mail will not send any emails?
#16
OK, we tried the fix as suggested, adding the $ variable....
Can this not be added as an update to a new version of the module. It did waste part of a day looking for a fix.
#17
Implemented this a while ago for a site, and now of course that they go to start using it - after much encouragement not to use email for tracking support issues - I'm seeing the same issues.
Site email works fine, but CT email doesnt seem to be getting sent.
Can anyone specify which file and line number the missing $ is on?
Many thanks - and for continuing to support this great module.
-mysty
#18
This is fixed in 5.x-1.x-dev. If anyone could test the dev tarball and verify that would be appreciated. Otherwise this will eventually be in the next beta,
#19
Automatically closed -- issue fixed for 2 weeks with no activity.
#20
Hi all,
I'm running Drupal 6, and no mails (at all) are sent out.
Any insight into getting this fixed is ofcourse appreciated.
Other Drupal emails, notifications etc are sent out without problems.
Cheers // Jaap.
#21
@JLelie you haven't posted enough details for me to know what to tell you. The casetracker module on it's own does *not* send email. It's generally recommended to use it with something like the notifications module to handle this.
Also please open a new issue instead of resurrecting issues that have been closed for ~6 months.