Page 1 of 1

Unit Notifications Bouncing

Posted: Sun Aug 30, 2009 7:34 pm
by wrigjef
I have half a dozen email addresses that are bouncing back to me (as unit admin) after sending a notification from the ward website. I cross checked the registered units and asked a few of these members to verify their address, they said it looked good so I sent them a test email directly from my gmail account. They are responding saying the email address is correct. I can not understand why they are bouncing from the system. Help

Posted: Sun Aug 30, 2009 9:35 pm
by russellhltn
What do the bounce messages say? Since the message claims to be from you, but is being sent by church servers, some email providers reject them.

Posted: Mon Aug 31, 2009 8:26 am
by calebpusey
RussellHltn wrote:Since the message claims to be from you, but is being sent by church servers, some email providers reject them.
Russell is correct in this, the emails are sent by the Church on behalf of the user, many email providers (including gmail) will reject these as Spam or Malicious emails.

The solution to the issue for the time being is to build a list of emails for the various users that need to be contacted. It can be quite arduous at the stake level with 1000+ people, however they are currently working on a new version of the Local Unit Website. Read more about it here:

http://tech.lds.org/wiki/index.php/LUWS ... uggestions

Here is one

Posted: Thu Sep 03, 2009 12:49 am
by wrigjef
2:16 AM (27 minutes ago)

Message from yahoo.com.
Unable to deliver message to the following address(es).

<syndyry@yahoo.com>:
This user doesn't have a yahoo.com account (syndyry@yahoo.com) [0]

--- Original message follows.

Return-Path: <c2webadmin@gmail.com>
X-YMailISG: OlvK16oWLDv6HTvasZSQZBwEJOpLknilnIiIxr3HYvGnNoHykGm4oDzlBGvISuGMtlE1kR0sQI.rV3aLucLWnGPUFzzJuWAPFzsfwZjYmr5UpTHM36dRJf7SUD4O1aOFQaj6XBLu85nW4R4GW6oCtTrdEHSsvmN2Uow0fK.jaUUBPKQDv6.5Gnx0EjV439zpywppNHchdb0Gos2T__5COdh2e7MgOHoxfyfWV.Y7jAWHKKE3uvwAFzEYNg5t8_gwalpB_Tq2HNzZgt_.pX0oYQoAfZ9jJqpjcyY.RTPdzPqYgNSPDnZSxD817BKBtq3N3972a5ou36HFSPeSoWYntwOLxcfgYHYhW_1hsBoLKhu0wB3JOuriYJplUHwPgIVEQnNkt.BhjkXKWw--
X-Originating-IP: [216.49.178.92]
Authentication-Results: mta140.mail.re4.yahoo.com from=gmail.com; domainkeys=neutral (no sig); from=gmail.com; dkim=neutral (no sig)
Received: from 216.49.178.92 (EHLO mail2.gmhwh.org) (216.49.178.92)
by mta140.mail.re4.yahoo.com with SMTP; Wed, 02 Sep 2009 23:16:08 -0700
Return-Path: <“>
Received: from chqpvua1283.ldschurch.org ([10.97.1.83])
by mail2 (8.14.3/8.14.3) with ESMTP id n830fOdB005089
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Wed, 2 Sep 2009 18:41:24 -0600
Received: from 10.98.40.114 (smtp-relay.wh.ldsglobal.net [10.97.246.15])
by chqpvua1283.ldschurch.org (8.14.1/8.14.1) with SMTP id n830fNJH024049;
Wed, 2 Sep 2009 18:41:23 -0600
Message-Id: <200909030041.n830fNJH024049@chqpvua1283.ldschurch.org>
X-Mailer: TCL EMail Library 1.7
To: c2webadmin@gmail.com
From: Jeff Wright <c2webadmin@gmail.com>
Subject: New calendar item for stake/ward website
Date: Wed, 2 Sep 2009 18:41:23 -0600
X-Proofpoint-Virus-Version-Internal: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2009-09-02_05:2009-09-01,2009-09-02,2009-09-01 signatures=0
X-Proofpoint-Spam-Details-Internal-: safe
X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2009-09-02_09:2009-09-01,2009-09-02,2009-09-02 signatures=0

This is to inform you of the Youth Temple Trip which will happen on 12/01/2010. If you would like more information, please see the Web site.


*** MESSAGE TRUNCATED ***

Posted: Thu Sep 03, 2009 2:29 am
by russellhltn
wrigjef wrote:Message from yahoo.com.
Unable to deliver message to the following address(es).

<syndyry@yahoo.com>:
This user doesn't have a yahoo.com account (syndyry@yahoo.com) [0]
The email address is invalid. There's no such person as syndyry@yahoo.com. The account may have been canceled, or it may have been misspelled.

Just to be sure I tried to send a test message to that same email with identical results.

You've got three choices:

- Toss this back to the user a have them fix their email address.
- Ignore the problem.
- Disable the account.