This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Mail bounces for users with invalid mail address | ||
---|---|---|---|
Product: | www | Reporter: | David Strupl <dstrupl> |
Component: | Bugzilla | Assignee: | Marco Walther <marcow> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jglick, johnjullion, mentlicher, mmirilovic |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
David Strupl
2010-03-24 09:32:03 UTC
The problem is, the email system does not know if a user's email had become invalid:-( At least not for the direct user->user emails, BZ is now using:-( For mailing lists, sympa sees the bounces, collects stats on those bouncing users and eventually unsubscribes them. For BZ (especially the NB variant), the emails are sent from an user to users and lists. So all bounces for recipient-users will go directly to the sending user:-( Those bounce-messages might flow through our MTA's but just as `normal' messages. Nothing could even try to analyze all messages and try to act on bounce-messages. A default BZ installation sends emails from `bugzilla-daemon' or some other artificial address, which would simply ignore those bounces. But NB chose to use the `submitting/changing' user as sender. So not much I can do here in general. For all the @sun.com addresses, we should probably think about a bulk-update in the DB at some point. Translate the good ones to their @oracle.com counterpart and point the dead ones to a dummy-address. Sorry, not much help on that:-( I think this is a duplicate but I cannot find the original; perhaps it was closed? (In reply to comment #1) > A default BZ installation sends emails from `bugzilla-daemon' or some other > artificial address, which would simply ignore those bounces. But NB chose to > use the `submitting/changing' user as sender. Well can we change this then? All I know is that Issuezilla in SourceCast worked fine in this respect - changes appeared in a mail client to come "from" the person making the change, yet we did not get bounce messages. So this behavior is a functional regression. This either works somehow or someone did some change since I have just received the following mail. And BTW the link at the very bottom of the mail does not work for me (404). Subject: List commits automatic bounce management Date: March 29, 2010 6:54:07 AM GMT+02:00 To: miloslav.metelka@sun.com, vitezslav.stejskal@sun.com, david@solutions.cz Return-Path: <commits-owner@editor.netbeans.org> X-Original-To: david@solutions.cz Delivered-To: david@solutions.cz Received: from localhost (localhost [127.0.0.1]) by server1.solutions.cz (Postfix) with ESMTP id 52CBAB04214 for <david@solutions.cz>; Mon, 29 Mar 2010 04:34:08 +0000 (UTC) Received: from server1.solutions.cz ([127.0.0.1]) by localhost (server1.solutions.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6mdXKVZd-Fke for <david@solutions.cz>; Mon, 29 Mar 2010 04:34:05 +0000 (UTC) Received: from mailout02.kenai.com (mailout.kenai.com [64.79.150.121]) by server1.solutions.cz (Postfix) with ESMTP id 315C0B041E9 for <david@solutions.cz>; Mon, 29 Mar 2010 04:34:04 +0000 (UTC) Received: from mail02.netbeans.org (nbxmlm01z1.network.org [10.25.120.154]) by mailout02.kenai.com (Postfix) with ESMTP id 2DBF81EEF6; Mon, 29 Mar 2010 04:54:15 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by mail02.netbeans.org (Postfix) with ESMTP id D5FCF5CCCF; Mon, 29 Mar 2010 04:54:14 +0000 (GMT) Received: from mail02.netbeans.org ([127.0.0.1]) by localhost (nbxmlm01z1 network.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id fiDnlMFP8lgI; Mon, 29 Mar 2010 04:54:08 +0000 (GMT) Received: by mail02.netbeans.org (Postfix, from userid 60005) id 361A65CCB1; Mon, 29 Mar 2010 04:54:08 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at server1.solutions.cz X-Virus-Scanned: amavisd-new at network.org Received-Spf: Pass (sender SPF authorized) identity=mailfrom; client-ip=64.79.150.121; helo=mailout02.kenai.com; envelope-from=commits-owner@editor.netbeans.org; receiver=david@solutions.cz Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7BIT X-Mailer: Sympa 5.3.3 Message-Id: <20100329045408.361A65CCB1@mail02.netbeans.org> ecause we received MANY non-delivery reports, the 4 subscribers listed below have been removed from list commits: jan.pokorsky@sun.com jiri.prox@sun.com marek.slama@sun.com pavel.flaska@sun.com Managing bouncing subscribers: http://editor.netbeans.org/sympa/reviewbouncing/commits So is this issue resolved? If so please close. I still get a few of these mails per week, depending on how much I have been doing in BZ; especially affects changes to old but popular bugs. still valid *** Bug 188008 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 178016 *** |