Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 3 subscribers
  • Views 29709 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Recipient Verification with Exchange 2013

toltol
Using callout doesn't work anymore. As mentioned here

exchange 2013 recipient filtering

the recipient filter works different as in Ex2010:

I have also noticed that Recipientfiltering doesn't work exactly the same way as in EX07/EX10.
When enabled, you should get an 550 5.1.1 User unknown after the ending period (see below)


mail from:
250 2.1.0 Sender OK
rcpt to:
250 2.1.5 Recipient OK
data
354 Start mail input; end with .
Write some Text Here
.
550 5.1.1 User unknown


Is this a known issue for development?


This thread was automatically locked due to age.
  • 0 in reply to Louis-M

    Louis, are your users in multiple OUs?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Yes they are and that caught me out in the beginning too.

    I was told that everybody was in the same OU and configured the base OU as such. Everybody got email but certain groups (outside of the base OU) got rejected.

    I then set the base OU as DC=mydomain; DC=com and everything works.

    The majority of the time, the spam filter kicks it out for RBL's etc as expected. But if the mail does get past, everybody gets the mail they should and the odd attempt says "recipient not in directory" which is 100% correct in my case. So it's definitely working on my SG 310's on 9.4

Unfiltered HTML