[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 770
  • Last Modified:

CDO message being rejected

I tried this question on the IIS list with no comments.  I just found this list so I'll withdraw from IIS and try here.

I am maintaining a web site developed in ASP.  Part of the application sendS automated emails when certain actions are taken by users, such as submitting an order.  The email is generated using CDO.  We recently started receiving email notifications that email sent to one domain was being rejected.  The error message is as follows.  The folks at the blocked domain can receive email from our domain if sent directly so it does not look like a spam filter problem.
The following recipient(s) could not be reached:

      johndoe@xyz.com on 7/23/2007 5:51 PM

            You do not have permission to send to this recipient.  For assistance, contact your system administrator.

            <propertycontrol #5.7.1 smtp;554 5.7.1 Header forgery attempt - rejected>
Only messages to xyz.com are creating this error.  All other recipients are receiving the system generated email.  Any suggestions on what to look at to resolve this would be appreciated.

1 Solution
Ask them to whitelist your email address, the one it comes from.
dougmurphAuthor Commented:
The "From" address for the message is inserted in the asp code that creates the message.  We have tried sending email directly from this account using Outlook/Exchange Server and it is not blocked.  When messages are created using CDO does the receiving mail server see the address of the creating smpt server or the From address?  I have looked at the mail header of the messages received properly and can not see where the receiving system would identify this message as one to reject.  The only unique item in the header, from the messages sent out of the web server, is that the sender is identified  as "X-Mailer: Microsoft CDO for Windows 2000".
This is an issue with your SMTP server, not the code.
Possible Causes:

"I've seen this happen in instances where you (as the sender) do not have reverse-DNS set up.  Some receiving mail systems will not accept mail without being able to perform a reverse-DNS lookup to confirm the mail is coming from a legitimate source.  

"You are trying to relay your mail through another SMTP server and it does not permit you to relay.

"The recipient might have mailbox delivery restrictions enabled. For example, a recipient's mailbox delivery restriction was set to receive from a Distribution List only and non-members' email will be rejected with this error.

"Also this issue might happen when the user tries to forward a contact with a vcard.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now