On 4/11/2013 2:42 PM, Robert Lopez wrote: > That was a fast response Jan. Thanks. Is the overall situation > suggestive of any misconfiguration here?
[please don't top-post] It appears you're generating a bounce for spam. Don't do that; the spam sender address is often forged causing your notice to go to some innocent third party. This makes you a backscatter source. As a backscatter source, your queue can become clogged with undeliverable bounces and your server may be blacklisted by others. With an after queue content filter, the only valid choice you have is to tag and deliver the message (or in some cases, discard it, but that's not legal some places and not good practice everywhere else). -- Noel Jones > > > On Thu, Apr 11, 2013 at 1:22 PM, Jan P. Kessler > <post...@jpkessler.info <mailto:post...@jpkessler.info>> wrote: > > Hi, > > >> And these are the logfile lines for our sending of the >> non-delivery notice we sent. One item in these log lines I do >> not understand at all is "relay=server50.appriver.com >> <http://server50.appriver.com>[204.232.236.138]:25". I do not >> understand where were that information is sourced. It looks to >> me that we sent the non-delivery to a wrong location. > > No, that is correct. Source of that routing information is the > MX record for the target domain: > > # host -t mx ors-cpa.com <http://ors-cpa.com> > ors-cpa.com <http://ors-cpa.com> mail is handled by 10 > server50.appriver.com <http://server50.appriver.com>. > ors-cpa.com <http://ors-cpa.com> mail is handled by 20 > server51.appriver.com <http://server51.appriver.com>. > > > > > -- > Robert Lopez > Unix Systems Administrator > Central New Mexico Community College (CNM) > 525 Buena Vista SE > Albuquerque, New Mexico 87106
