Integrating bugzilla with AD to avoid "duplicate" emails.

[John Smith]

Hi,

I've had a complaint from a user about receiving multiple mails from
bugzilla.

Our network is a Windows AD network. Bugzilla uses LDAP authentication, and
users are authenticated against the AD domain controller on login.

For convenience, some users asked me to set up email distribution groups as
users in bugzilla.
I manually added the groups, so li...@mydomain.com can be added to the CC
list of a bug, or be assigned a bug.

The issue arises where us...@mydomain.com is a member of li...@mydomain.com
and in cases where us...@mydomain.com has raised a bug (or is the assignee
of a bug) and li...@mydomain.com is on the CC list of the bug. Each time the
bug is updated, the user receives 2 emails from bugzilla.
I've looked at the message headers, and the 2 emails received have 2
distinct message-IDs, because bugzilla is sending them as 2 separate emails
(one to us...@mydomain.com and the other to li...@mydomain.com ).

I don't think it's as simple as the users setting their email preferences.
e.g. if us...@mydomain.com is the assignee of a bug, and list@mydomain is NOT
on the CC list, in that case the user will not get any email if preferences
are set to not mail them when they are assignee and new comments are added
to the bug.

One solution would be to go back to the previous way of working - only AD
users are set up in bugzilla, and bugzilla email preferences can be used to
select events for which email is sent. This means all users on a list need
to be added manually to the CC list as needed, which is not really workable.

The alternatives are better integration between bugzilla and AD / Exchange.
Is there any way to make bugzilla aware of AD distribution lists and not
send an email to a user if the user is already on a list getting the email?
Or is it possible to only send 1 email per bug update (in which case
Exchange detects that the mail is being sent to the list, and a user on the
list, and the user will only receive 1 copy).

Thanks in advance for any suggestions.

[Greg Ward]

On Mon, Feb 23, 2009 at 6:23 AM, John Smith <bugzi...@gmail.com> wrote:
> I've had a complaint from a user about receiving multiple mails from
> bugzilla.

[...]

> The issue arises where us...@mydomain.com is a member of li...@mydomain.com
> and in cases where us...@mydomain.com has raised a bug (or is the  assignee
> of a bug) and li...@mydomain.com is on the CC list of the bug. Each time the
> bug is updated, the user receives 2 emails from bugzilla.
> I've looked at the message headers, and the 2 emails received have 2
> distinct message-IDs, because bugzilla is sending them as 2 separate emails
> (one to us...@mydomain.com and the other to li...@mydomain.com ).

IMHO this is something that should be handled by the mail server.
Unfortunately, it sounds as if Bugzilla makes it impossible for the
mail server to detect this case by sending separate messages for each
recipient.

> Or is it possible to only send 1 email per bug update (in which case
> Exchange detects that the mail is being sent to the list, and a user on the
> list, and the user will only receive 1 copy).

Bingo. I think this sounds much cleaner. I suspect there may be
privacy/security concerns for public Bugzillas, though. Perhaps this
would need to be a configurable option.

Greg

[jessica]

This is happening at our site as well. Has anyone had any clever
ideas about how to avoid this problem? If I'm assigned a bug, and it's
a bug related to a customer case, bugzilla will be sending separate
email to me, and to cases. cases is an email list I am on. I wind up
with two emails. If bugzilla had sent one email to "jessica, cases,
anyoneelse, etc", then our mail server would do the work of sending me
just the one email.

I respect that for public bugzillas you might not want an email to go
out with a long "To:" list, so sure, maybe making this a configuration
option would work. You could either have an option to 'send just one
email with the addresses in the To:' or you could have an option to
"send just one email but with the addresses in the Bcc:". Then you
could prevent the problem for everyone even on a public server.

Something else I'd consider acceptable would be to tag each email in a
set with a specific header with a unique string, then the users could
have an email client side filter remove duplicates. not particularly
elegant but it seems like it would work. I might try hacking this
into our bugzilla if it looks do-able just to give our users a break
from the multiple emails.

Of course I'm also trying to figure a way to do the workflow
differently so we avoid the problem in the first place, but right now
this looks like it's going to keep happening..

--jessica

[maneesh...@gmail.com]

Is there a workaround to stop duplicate emails?

[Thorsten Schöning]

Guten Tag maneesh...@gmail.com,
am Donnerstag, 4. September 2014 um 05:01 schrieben Sie:

> Is there a workaround to stop duplicate emails?

Not really, mails get send to each recipient independently, check
BugMail.pm around line 208. You may have the option to use an
extension and hook to remove recipients depending on some criteria:

http://www.bugzilla.org/docs/4.4/en/html/api/Bugzilla/Extension.html
http://www.bugzilla.org/docs/4.4/en/html/api/Bugzilla/Hook.html#bugmail_recipients

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning E-Mail:Thorsten....@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/

Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow