#1315 mail sending errors forwarded to all subscribers?

unreleased
invalid
nobody
sf-4 (350)
General
nobody
2015-02-21
2011-01-11
Mark Ramm
No

After updating a ticket a couple times through the web interface, I got this error message in my gmail account:

     Delivered-To: mramm@geek.net
     Received: by 10.220.161.212 with SMTP id s20cs252050vcx;
             Tue, 11 Jan 2011 12:06:03 -0800 (PST)
     X-pstn-nxpr: disp=neutral, envrcpt=mramm@geek.net
     X-pstn-nxp: bodyHash=773c4a94f3eb1029f91d0bb20e5ac6144cc861df, headerHash=fadc54789db21b8ba28428f22f27ef8aea6dee76, keyName=4, rcptHash=10941ccc1f8a4042760a81cd649f62a5f4ecec0e, sourceip=216.34.181.68, version=1
     Received: by 10.142.86.7 with SMTP id j7mr162125wfb.299.1294776363001;
             Tue, 11 Jan 2011 12:06:03 -0800 (PST)
     Return-Path: <>
     Received: from psmtp.com ([74.125.149.132])
             by mx.google.com with SMTP id l7si14151526wfa.100.2011.01.11.12.06.01
             (version=TLSv1/SSLv3 cipher=RC4-MD5);
             Tue, 11 Jan 2011 12:06:02 -0800 (PST)
     Received-SPF: neutral (google.com: 216.34.181.68 is neither permitted nor denied by best guess record for domain of source) client-ip=216.34.181.68;
     Authentication-Results: mx.google.com; spf=neutral (google.com: 216.34.181.68 is neither permitted nor denied by best guess record for domain of source) smtp.mail=
     Received: from source ([216.34.181.68]) (using TLSv1) by na3sys009amx248.postini.com ([74.125.148.10]) with SMTP;
        Tue, 11 Jan 2011 12:06:02 PST
     X-ACL-Warn: 
     Received: from sfu-scmprocess-2.v42.ch3.sourceforge.com ([172.29.42.192] helo=smtp.ch3.sourceforge.com)
        by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
        (Exim 4.72)
        id 1PckTf-0000ZO-NQ
        for mramm@users.sourceforge.net; Tue, 11 Jan 2011 20:06:00 +0000
     Received: from exim by sfu-scmprocess-2.v42.ch3.sourceforge.com with local (Exim 4.69)
        id 1PckTa-0001oR-Ls
        for mramm@users.sf.net; Tue, 11 Jan 2011 20:05:54 +0000
     X-Failed-Recipients: sf-overlords@users.sf.net
     Auto-Submitted: auto-replied
     From: Mail Delivery System <Mailer-Daemon@ch3.sourceforge.com>
     To: mramm@users.sf.net
     Subject: Mail delivery failed: returning message to sender
     Message-Id: <E1PckTa-0001oR-Ls@sfu-scmprocess-2.v42.ch3.sourceforge.com>
     Date: Tue, 11 Jan 2011 20:05:54 +0000
     X-Spam-Score: 0.9 (/)
     X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
      See http://spamassassin.org/tag/ for more details.
       1.0 RDNS_DYNAMIC           Delivered to internal network by host with
                                  dynamic-looking rDNS
      -0.1 AWL                    AWL: From: address is in the auto white-list
     X-Headers-End: 1PckTf-0000ZO-NQ
     X-pstn-neptune: 0/0/0.00/0
     X-pstn-levels: (S:56.61558/99.90000 CV:99.9000 FC:95.5390 LC:95.5390 R:95.9108 P:95.9108 M:97.0282 C:98.6951 )
     X-pstn-settings: 2 (0.5000:0.5000) s cv gt3 gt2 gt1
     X-pstn-addresses: from <Mailer-Daemon@ch3.sourceforge.com> [40/2]

     This message was created automatically by mail delivery software.

     A message that you sent could not be delivered to one or more of its
     recipients. This is a permanent error. The following address(es) failed:

       sf-overlords@users.sf.net
         SMTP error from remote mail server after RCPT TO:<sf-overlords@users.sf.net>:
         host mx.sourceforge.net [216.34.181.68]: 550 unknown user

     ------ This is a copy of the message, including all the headers. ------

     Return-path: <mramm@users.sf.net>
     Received: from [127.0.0.1] (helo=sfu-scmprocess-2.b.ch3.sourceforge.com)
        by sfu-scmprocess-2.v42.ch3.sourceforge.com with esmtp (Exim 4.69)
        (envelope-from <mramm@users.sf.net>)
        id 1PckTV-0001oK-Jt
        for sf-overlords@users.sf.net; Tue, 11 Jan 2011 20:05:49 +0000
     Content-Type: multipart/related;
        boundary="===============1487926123577244341=="
     MIME-Version: 1.0
     To: "[allura:tickets] " <1314@tickets.allura.p.re.sf.net>
     From: "mramm" <mramm@users.sf.net>
     Reply-To: "[allura:tickets] " <1314@tickets.allura.p.re.sf.net>
     Subject: [allura:tickets] #1314 HTTP GET to update_homepage is destructive
     Message-ID: <8ba02e1a569d5f90cdc856bd4e01cf9cfdbc04c4.tickets@allura.p.sourceforge.net>
     Date: Tue, 11 Jan 2011 20:05:49 +0000

     This is a multi-part message in MIME format.
     --===============1487926123577244341==
     Content-Type: multipart/alternative;
        boundary="===============8846668285700606759=="
     MIME-Version: 1.0

     --===============8846668285700606759==
     Content-Type: text/plain; charset="iso-8859-1"
     MIME-Version: 1.0
     Content-Transfer-Encoding: quoted-printable

     If that page's content is destroyed, I have a copy here: =

     https://sf-dbrondsema-5030.sb.sf.net/p/sales-demo/wiki/HomePageContent/

     ---

     Sent from sourceforge.net because you indicated interest in <https://source=
     forge.net/p/allura/tickets/1314/>

     To unsubscribe from further messages, please visit <https://sourceforge.net=
     /auth/prefs/>

     --===============8846668285700606759==
     Content-Type: text/html; charset="iso-8859-1"
     MIME-Version: 1.0
     Content-Transfer-Encoding: quoted-printable

     <p>If that page's content is destroyed, I have a copy here: </p>
     <p><a href=3D"https://sf-dbrondsema-5030.sb.sf.net/p/sales-demo/wiki/HomePa=
     geContent/">https://sf-dbrondsema-5030.sb.sf.net/p/sales-demo/wiki/HomePage=
     Content/</a></p>
     <hr />
     <p>Sent from sourceforge.net because you indicated interest in <a href=3D"h=
     ttps://sourceforge.net/p/allura/tickets/1314/">https://sourceforge.net/p/al=
     lura/tickets/1314/</a></p>
     <p>To unsubscribe from further messages, please visit <a href=3D"https://so=
     urceforge.net/auth/prefs/">https://sourceforge.net/auth/prefs/</a></p>
     --===============8846668285700606759==--
     --===============1487926123577244341

Discussion

  • Mark Ramm - 2011-01-11
    • custom_field__size: --> 2
     
  • Rick Copeland - 2011-01-20

    I'm fairly sure this is due to the fact that your return address is on the outgoing mail. Not sure there's anything we can do about mail servers sending rejection notices back to the commenter (assuming we want the sender to be in the from: field, as designed).

     
  • Mark Ramm - 2011-01-24
    • status: open --> invalid
     

Log in to post a comment.