Mantis Bug Tracker - Forums

Create a user with viewer permissions (or whatever you like) and assign them to the project. For that user, change their email address to be whatever address you want for the mailing list. Now, so long as the project permissions allow sending 'new' emails to viewers, you should be set.

Just a quick thought: does the IIS user have permission to access that shared drive? Remember that Mantis itself, running under IIS, is essentially running as the IIS user...

Could you maybe just make the parent project private and then give all users 'reader' permissions on that parent project?

If you already have your WAMP environment set up, download the proper release from http://mantisbt.org/download.php .

For those projects that you don't want people to have 'write' access to, why don't you just set the 'report' access level to 'administrator' or something similar?

shadeoner wrote:So, is any way to make a new categorie ?

You could always just use custom fields and add it that way, couldn't you?

No need for any other commands. Once you've installed the web service, though, you need to write your client application to interface with the web service itself.

The MantisConnect files that you downloaded should have a prebuilt .NET library that you can use to write your client with (or you can ...

Off the top of my head, are you running through a proxy by any chance? We found that any time there were things like this happening it was because the user had not added the server to the proxy exception list.

"then it stops working"

What is "it", exactly? Mantis entirely or just the sending of emails?

For what it's worth, that should be:
$g_enable_email_notification = ON;

anyway, as it's case-sensitive.

OK, so now I'm clutching at straws :)

I wonder if it's a user thing? Maybe if you are logged into the network the Exchange server is giving YOU access but when the web server is trying to access it (Apache, IIS or something else, by the way?) then the user running the server is not given access ...

This may be a silly question, but are you sure that your Exchange server is set up to accept SMTP requests and/or to be used as a gateway (or whatever it's called... sorry, bad coffee day)?

Basically all that is required is that you:
a) have versions associated with your project; and
b) set the 'fixed in version' value when resolving a problem.

I believe that that is all that is required, anyway...

I don't suppose you're going through a proxy by any chance? We had these sorts of problems with whatever proxy was being used on our network at work (it was an authenticated proxy).

Once we told the browsers to bypass the proxy for the (local, internal) Mantis server, we had no more problems...

HansV: We always had trouble accessing Mantis through the proxy. I assume it was a MS one, seeing as we were an all MS shop... we ended up just setting our browsers to bypass the proxy for the Mantis server.

I don't know who was responsible for the problem, but I do know that we had all sorts of ...

So, in the HTML source of the 'broken' one, where is the default.css stylesheet supposed to be coming from? That is to say, what's the URL that is pointing to the stylesheet?

Also, does the stylesheet exist there at all?