Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 01F1A1007D for ; Wed, 23 Oct 2013 15:01:31 +0000 (UTC) Received: (qmail 7704 invoked by uid 500); 23 Oct 2013 15:01:30 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 7685 invoked by uid 500); 23 Oct 2013 15:01:30 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 7677 invoked by uid 99); 23 Oct 2013 15:01:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Oct 2013 15:01:30 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Oct 2013 15:01:24 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=IHATws5/1DPB6Iqhw8Ea7eQiCKBkCYDjB639gxk6M4o=; b=mBZWIZ5AHqARrvSbkMTCSUktqdPNKDC3lvAiCtT3I6hf8qtzKRjEVNKCSOenGTV+FQX+/DCWPpMRu68E6PLw74mhbwtP9BYt0DPVlPHqb3YCVEAZqRVGvURCe+0LYMRwDcIWfdIP1liyGbgR4oCL+5ci9KhbWH6sV8wBT3mmGfE=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-2.v29.ch3.sourceforge.com) by sfs-alluradaemon-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VYzvj-0002qC-J6 for allura-dev@incubator.apache.org; Wed, 23 Oct 2013 15:01:03 +0000 Content-Type: multipart/related; boundary="===============8876827146787029956==" MIME-Version: 1.0 To: "[allura:tickets] " <6249@tickets.allura.p.re.sf.net> From: "Igor Bondarenko" Reply-To: "[allura:tickets] " <6249@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6249 Use a stable Sender: header in email notifications [ss4075] Message-ID:

Date: Wed, 23 Oct 2013 15:01:03 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============8876827146787029956== Content-Type: multipart/alternative; boundary="===============5242082651824411629==" MIME-Version: 1.0 --===============5242082651824411629== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Did you make changes to exim config, as I pointed out [here](https://sourceforge.net/p/allura/tickets/6249/#a60b)? Yep, they wouldn't. We can set `Sender:` to some site-wide address inside mail_util.SMTPClient.sendmail, if `sender` parameter isn't specified, or go ahead and fix all manual calls to `sendmail` and `sendsimplemail` to include sender parameter. Not sure which way is better. --- ** [tickets:#6249] Use a stable Sender: header in email notifications [ss4075]** **Status:** code-review **Labels:** support p3 42cc **Created:** Fri May 17, 2013 04:31 PM UTC by Dave Brondsema **Last Updated:** Wed Oct 23, 2013 02:17 PM UTC **Owner:** nobody Email notifications have varying From addresses (e.g. the ticket submitter). Notifications should have a `Sender:` header specified which refers to the system sending rather than the end-user we're doing it on behalf of. This should be a stable value so that it can be used in mail filters (e.g. mailman). Perhaps the tool's email address would work well. Test how common clients (e.g. gmail) display it and if it affects replies at all. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============5242082651824411629== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

Did you make changes to exim config, as I pointed out here?

Yep, they wouldn't. We can set Sender: to some site-wide address inside mail_util.SMTPClient.sendmail, if sender parameter isn't specified, or go ahead and fix all manual calls to sendmail and sendsimplemail to include sender parameter. Not sure which way is better.

[tickets:#6249] Use a stable Sender: header in email notifications [ss4075]

Status: code-review
Labels: support p3 42cc
Created: Fri May 17, 2013 04:31 PM UTC by Dave Brondsema
Last Updated: Wed Oct 23, 2013 02:17 PM UTC
Owner: nobody

Email notifications have varying From addresses (e.g. the ticket submitter). Notifications should have a Sender: header specified which refers to the system sending rather than the end-user we're doing it on behalf of.

This should be a stable value so that it can be used in mail filters (e.g. mailman). Perhaps the tool's email address would work well. Test how common clients (e.g. gmail) display it and if it affects replies at all.

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============5242082651824411629==-- --===============8876827146787029956==--