cancel
Showing results for 
Search instead for 
Did you mean: 

External firm using SpamShield rejecting our mail

Jump to solution

A certain outside firm is rejecting our email messages.   A non-delivery report is not generated back to us.

The outside firm says that our IronMail system is not supporting the "550 callout verification"

I'm not familiar with this term.   Is this called something else in IronMail? 

Or is it not implemented in IronMail?   Is it available in McAfee Email Gateway, whenwe move to MEG?

1 Solution

Accepted Solutions
Highlighted

Re: External firm using SpamShield rejecting our mail

Jump to solution

If you are getting a DSN back I would say that the IronMail is properly dealing with the 550 message, no matter what the text of it is.  The SpamShield appears to be using callback verification (another term for callout verification).  I don't know much about the process other than the recieving server will try a connection back to your MX record to veriy the sender is real.

Do you have BATV turned on?  If so that may be breaking their side of things.  Try whitelisting the recipient's IP addresses for BATV if that is on.  That being said, I have found notes that many of the large implementers of callback verification caution against its use.

MEG will not support it in any different way, and there is no reason that it should.

2 Replies
Highlighted

Re: External firm using SpamShield rejecting our mail

Jump to solution

If you are getting a DSN back I would say that the IronMail is properly dealing with the 550 message, no matter what the text of it is.  The SpamShield appears to be using callback verification (another term for callout verification).  I don't know much about the process other than the recieving server will try a connection back to your MX record to veriy the sender is real.

Do you have BATV turned on?  If so that may be breaking their side of things.  Try whitelisting the recipient's IP addresses for BATV if that is on.  That being said, I have found notes that many of the large implementers of callback verification caution against its use.

MEG will not support it in any different way, and there is no reason that it should.

Re: External firm using SpamShield rejecting our mail

Jump to solution

I added the IP address that are using for outbound mail to our organization, whitelisted from "DNS Bounce Verification Protection", inbound rule.

Is that what you were suggesting?

The other organizaition seems to be using two addresses for their MX inbound mail, and a different address for outbound mail.

It's difficult to know what all of their outbound servers are, but I do see this one in the log:

... mailhost3.babcock.com:07032013 11:45:14|21|207.250.188.161-55282|1|102|DSN for spoofed message.|[]

More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator
  • Community Help Hub

      New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

    • Find Forum FAQs
    • Learn How to Earn Badges
    • Ask for Help
    Go to Community Help

    Join the Community

      Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

    • Get helpful solutions from McAfee experts.
    • Stay connected to product conversations that matter to you.
    • Participate in product groups led by McAfee employees.
    Join the Community
    Join the Community