Closed
Bug 4232
Opened 26 years ago
Closed 25 years ago
E-mails referring to new bugs entered are not being sent to a component's owner
Categories
(Bugzilla :: Bugzilla-General, defect, P3)
Tracking
()
VERIFIED
INVALID
People
(Reporter: paulo, Assigned: justdave)
Details
I am using Bugzilla at my site for evaluation purposes.
After entering a new bug, no e-mail is sent to a component's owner.
The table components is properly populated with owners' e-mails.
The files mail and no-mail are created empty and with the right permissions.
What does the executable processmail does?
Thank you
Comment 1•26 years ago
|
||
Yes, this is what processmail does. It gets executed whenever a bug is created
or changed, and causes mail to be sent.
Does mail get sent anywhere? It should also get sent back to the submitter. Is
that happening?
Comment 2•25 years ago
|
||
Reassigning to dmose@mozilla.org, who now has front-line responsibility for
all Bonsai and Bugzilla bugs.
Comment 3•25 years ago
|
||
Reassigning back to me. That stuff about me no longer being the front-line
person responsible for Bugzilla and Bonsai turned out to be short-lived.
Please pardon our confusion, and I'm very sorry about the spam.
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Comment 4•25 years ago
|
||
Paulo Cesar de Oliveira wrote:
>
> Dear Sirs,
>
> The problem I have reported was solved. It was related to
> UNIX permissions regarding the files mail, nomail and maillock
> at the <bugzilla_home>/data directory.
>
> I am sorry to disturb you. Thanks,
>
> Paulo
Comment 5•25 years ago
|
||
Verified on Terry's word, the reporter erred.
Status: RESOLVED → VERIFIED
QA Contact: matty
Assignee | ||
Comment 6•23 years ago
|
||
moving to Bugzilla product
reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE
Assignee: terry → justdave
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•