Closed
Bug 223362
Opened 22 years ago
Closed 22 years ago
unable to receive email notification when using a mailing list
Categories
(Bugzilla :: Email Notifications, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: jun.s, Assigned: preed)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461; .NET CLR 1.0.3705)
Build Identifier:
We created a user using a mailing list but wasn't able to receive any email
notification. Is there any email restrictions on bugzilla?
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
| Reporter | ||
Comment 1•22 years ago
|
||
Steps to Reproduce:
1. Create a new bugzilla account using a mailing list.
2. I did not receive the email confirmation.
| Assignee | ||
Comment 2•22 years ago
|
||
No and there are lots of people doing this.
If you're *really* running Bugzilla on Windows 2000, there are some mail-related
issues with that; read the install guide for details you have to address.
RESOLVED -> WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 3•22 years ago
|
||
When we try to send an email directly to our mailing list using our Outlook
email client we we're able to receive the emails. But when we use it in
bugzilla it didn't send any email notifications. I also tried creating a user
here in your site at "http://bugzilla.mozilla.org" using our mailing list
(Manila.APS.DBATeam@accenture.com), but we didn't receive the email
confirmation. Can we check the logs for bugzilla to see what actually happen
behind the scene on sending of the email notifications? Does it logs it as an
error?
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 4•22 years ago
|
||
Your mail server accepted the message:
Oct 23 02:21:09 mecha sendmail[19491]: h9N9L779019489:
to=<Manila.APS.DBATeam@accenture.com>, ctladdr=<apache@mecha.mozilla.org>
(48/48), delay=00:00:02, xdelay=00:00:02, mailer=esmtp, pri=30351,
relay=nbrmr1002.accenture.com. [170.252.248.71], dsn=2.0.0, stat=Sent
(h9N9LDdG024655 Message accepted for delivery)
And then we received a bounce back a few seconds later.:
Oct 23 02:21:17 mecha sendmail[19514]: h9N9LG79019514: from=<>, size=5070,
class=0, nrcpts=1, msgid=<200310230921.h9N9L7Fn019487@mecha.mozilla.org>,
proto=ESMTP, daemon=MTA, relay=nbrmr1002.accenture.com [170.252.248.71]
Here's the bounce message:
Return-Path: <MAILER-DAEMON@mecha.mozilla.org>
Received: from nbrmr1002.accenture.com (nbrmr1002.accenture.com [170.252.248.71])
by mecha.mozilla.org (8.12.8/8.12.8) with ESMTP id h9N9LG79019514
for <apache@mecha.mozilla.org>; Thu, 23 Oct 2003 02:21:16 -0700
Received: from mtahm1500.accenture.com (mtahm1500.accenture.com [10.10.100.246])
by nbrmr1002.accenture.com (8.12.10/8.12.10) with ESMTP id h9N9LKdG024703
for <apache@mecha.mozilla.org>; Thu, 23 Oct 2003 04:21:20 -0500 (CDT)
Date: Thu, 23 Oct 2003 02:21:07 -0700
Message-Id: <200310230921.h9N9L7Fn019487@mecha.mozilla.org>
From: Postmaster@accenture.com
To: bugzilla-daemon@mozilla.org
Subject: DELIVERY FAILURE: User Manila.APS.DBATeam
(Manila.APS.DBATeam@accenture.com) not
listed in public Name & Address Book
X-Archived: msg.XXNXkX6x@nbrmr1002
X-Archived: msg.XXyXkX6x@nbrmr1002
X-MIMETrack: Itemize by SMTP Server on MTAHM1500/Server/Accenture(Release 5.0.9a
|January
7, 2002) at 10/23/2003 04:20:05 AM,
Serialize by Router on MTAHM1500/Server/Accenture(Release 5.0.9a
|January 7, 2002) at
10/23/2003 04:20:12 AM,
Serialize complete at 10/23/2003 04:20:12 AM
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="==IFJRGLKFGIR20977UHRUHIHD"
Status: O
X-Status:
X-Keywords:
X-UID: 34147
--==IFJRGLKFGIR20977UHRUHIHD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Your message
Subject: mozilla.org Bugzilla Account Information
was not delivered to:
Manila.APS.DBATeam@accenture.com
because:
User Manila.APS.DBATeam (Manila.APS.DBATeam@accenture.com) not listed in
public Name & Address Book
--==IFJRGLKFGIR20977UHRUHIHD
Content-Type: message/delivery-status
Reporting-MTA: dns;mtahm1500.accenture.com
Final-Recipient: rfc822;Manila.APS.DBATeam@accenture.com
Action: failed
Status: 5.1.1
Diagnostic-Code: X-Notes; User Manila.APS.DBATeam
(Manila.APS.DBATeam@accenture.com) not listed in public Name & Address Book
--==IFJRGLKFGIR20977UHRUHIHD
Content-Type: message/rfc822
Received: from nbrmr1002.accenture.com ([170.252.248.71])
by mtahm1500.accenture.com (Lotus Domino Release 5.0.9a)
with ESMTP id 2003102304200559:187559 ;
Thu, 23 Oct 2003 04:20:05 -0500
Received: from mecha.mozilla.org (h-207-126-111-200-mozilla.sv.meer.net
[207.126.111.200])
by nbrmr1002.accenture.com (8.12.10/8.12.10) with ESMTP id h9N9LDdG024655
(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
for <Manila.APS.DBATeam@accenture.com>; Thu, 23 Oct 2003 04:21:14 -0500
(CDT)
Received: from mecha.mozilla.org (localhost.localdomain [127.0.0.1])
by mecha.mozilla.org (8.12.8/8.12.8) with ESMTP id h9N9L779019489
for <Manila.APS.DBATeam@accenture.com>; Thu, 23 Oct 2003 02:21:07 -0700
Received: (from apache@localhost)
by mecha.mozilla.org (8.12.8/8.12.8/Submit) id h9N9L7Fn019487;
Thu, 23 Oct 2003 02:21:07 -0700
Date: Thu, 23 Oct 2003 02:21:07 -0700
Message-Id: <200310230921.h9N9L7Fn019487@mecha.mozilla.org>
From: bugzilla-daemon@mozilla.org
To: Manila.APS.DBATeam@accenture.com
Subject: mozilla.org Bugzilla Account Information
X-Archived: msg.XXyXkX6x@nbrmr1002
X-MIMETrack: Itemize by SMTP Server on MTAHM1500/Server/Accenture(Release 5.0.9a
|January
7, 2002) at 10/23/2003 04:20:05 AM,
Serialize by Router on MTAHM1500/Server/Accenture(Release 5.0.9a
|January 7, 2002) at
10/23/2003 04:20:12 AM,
Serialize complete at 10/23/2003 04:20:12 AM
======================
======================
As you can see this is not our problem, nor is it Bugzilla's problem.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 5•22 years ago
|
||
Where can we find that log file in our Bugzilla server?
Updated•13 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
•