Mantis Bug Tracker - Forums

To fix this we croned the email_send_all() in a small web page, then set $g_email_send_using_cronjob = ON;. Now our cron job runs, sends the emails, then segfaults. But at least the users no longer receive weird errors...

We are having issues with our system (1.1.0a3). Any time there is a call to email users-we are getting seg fault errors as shown below.

[Thu Feb 14 09:10:38 2008] [notice] child pid 14911 exit signal Segmentation fault (11)

Commenting out the lines that make the call to email functions remove ...

Thanks for the response.

It appears that $g_mail_save_from = ON; is already set in our system. I looked at little deeper and found this in mail_api.php:


if ( $t_mail_use_reporter ) {
// Always report as mail_reporter
$t_reporter_id = user_get_id_by_name( $t_mail_reporter );
$t_reporter = $t ...

I do agree that trying to educate users is a bit of a lost cause. I am going to forward your post to our sys admin.

Many thanks for your suggestions!

We have email parsing running successfully. However, when a bug is updated via email, the note that is added to the bug does not include any information regarding who sent the email, and displays as "Mail (reporter)". (Reporter being the security level that Mail is set to.)

My question is: is there ...

After some research here is what I came up with:

When you receive and update from Mantis, it will the project and task id in the subject line. Ex- [Project 0000059]. The information in the [ ] is what Mantis uses as the issue id.

If you respond/create an email message with subject that includes ...

Is there a way to attach an email to an issue so that each time the issue gets updated that user will be notified? This would be an email that is external to the Mantis user system.
We are on Mantis 1.1.0a3.

Thank you.