<div>
<div class="content wysiwyg-content">
I am getting some bounces from an application that is not hosted at my site. &nbsp;An email is generated at the login phase. &nbsp;We are attempting to relay it from the hosting service and I fear that this may be a problem for some spam filters. &nbsp;I have sent test messages directly from myself and they are being delivered. &nbsp; 
 
Is there a way to safely relay an email message such as this and not be caught in the spam filters? 
 
 
Listed below is part of the message received. 
 
 
Received: from enterprise.filter (localhost.localdomain [127.0.0.1]) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;by 
&nbsp;oc-smtp1.mxpath.net (MXPath Final Delivery) with SMTP id AE3DC33698 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;for 
&nbsp;&lt;mhmg.cjarmon@med.nyu.edu&gt;; Thu, &nbsp;1 Apr 2010 15:16:18 +0000 (GMT) 
Received: from AAAHC-MAIL-ET.AAAHC.org (unknown [216.159.232.116]) 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(using TLSv1 with cipher AES128-SHA (128/128 bits)) 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(No client certificate requested) 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;by oc-smtp1.mxpath.net (MXPath Final Delivery) with ESMTP id 41E612BC21 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;for &lt;mhmg.cjarmon@med.nyu.edu&gt;; Thu, &nbsp;1 Apr 2010 15:16:18 +0000 (GMT) 
Received: from DEDR62 (67.199.120.63) by BreakTechRelay.aaahc.org (10.0.0.12) 
&nbsp;with Microsoft SMTP Server id 8.2.176.0; Thu, 1 Apr 2010 10:15:35 -0500 

</div>
</div>

I am getting some bounces from an application that is not hosted at my site. An email is generated at the login phase. We are attempting to relay it from the hosting service and I fear that this may be a problem for some spam filters. I have sent test messages directly from myself and they are being delivered. 

Is there a way to safely relay an email message such as this and not be caught in the spam filters?


Listed below is part of the message received.


Received: from enterprise.filter (localhost.localdomain [127.0.0.1])	by
 oc-smtp1.mxpath.net (MXPath Final Delivery) with SMTP id AE3DC33698	for
 <mhmg.cjarmon@med.nyu.edu>; Thu, 1 Apr 2010 15:16:18 +0000 (GMT)
Received: from AAAHC-MAIL-ET.AAAHC.org (unknown [216.159.232.116])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by oc-smtp1.mxpath.net (MXPath Final Delivery) with ESMTP id 41E612BC21
	for <mhmg.cjarmon@med.nyu.edu>; Thu, 1 Apr 2010 15:16:18 +0000 (GMT)
Received: from DEDR62 (67.199.120.63) by BreakTechRelay.aaahc.org (10.0.0.12)
 with Microsoft SMTP Server id 8.2.176.0; Thu, 1 Apr 2010 10:15:35 -0500

550 #5.1.0 Address rejected

Various techniques are used to prevent email spam (unsolicited bulk email). No technique is a complete solution to the spam problem, and each has trade-offs between incorrectly rejecting legitimate email (false positives) vs. not rejecting all spam (false negatives) - and the associated costs in time and effort. Anti-spam techniques can be broken into four broad categories: those that require actions by individuals, those that can be automated by email administrators, those that can be automated by email senders and those employed by researchers and law enforcement officials.

AntiSpam

An email client, email reader or more formally mail user agent (MUA) is a computer program used to access and manage a user's email. A web application that provides message management, composition, and reception functions is sometimes also considered an email client, but more commonly referred to as webmail.