On 6/2/2010 8:56 AM, Ralf Hildebrandt wrote:
* Robert Fitzpatrick<[email protected]>:
I am getting a lot of these for various domains...

Jun  2 07:21:08 esmtp postfix/smtpd[55535]: NOQUEUE: reject: RCPT
from mail.cypresspartners.com[72.242.211.227]: 450 4.1.8
<[email protected]>: Sender address
rejected: Domain not found;
from=<[email protected]>
to=<[email protected]>  proto=ESMTP helo=<mail.cypresspartners.com>

I assume these are legitimate rejects since the helo domain is
cypresspartners.com and I did not find an A record for that domain.
Is that correct?

No.

$ host onlinealert.bankofamerica.com
Host onlinealert.bankofamerica.com not found: 3(NXDOMAIN)
$ host -t mx onlinealert.bankofamerica.com
Host onlinealert.bankofamerica.com not found: 3(NXDOMAIN)


Yes, about what I expected from that particular message. But my real problem is a message being sent from BOA each morning and generating this error...

Your message did not reach some or all of the intended recipients.

 Subject:       LCM Summary
Sent:   6/2/2010 10:18 AM

The following recipient(s) could not be reached:

  [email protected] on 6/2/2010 10:19 AM
You do not have permission to send to this recipient. For assistance, contact your system administrator. <crprdnbrd10.bankofamerica.com #5.7.1 smtp;550 5.7.1 [email protected] Not Authorized To Send Internet E-mail>

[email protected] receives this error message in the Exchange mailbox each morning and I can find this message in our Postfix logs at the gateway. But I cannot find any attempt previous. I can send these on demand, so I did and just this message came through the gateway. What can I take from this error message to help me track down why BOA is, evidently, generating this message?

This is when we enter the recipient address in their alert system while loged in as [email protected]. There is no SPF record for lcmgroup.com. I'm assuming this has something to do with Exchange, but why can I not see the original attempt to send the message in my gateway logs?

Thanks for any help, Robert

Reply via email to