Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Migrating Exchagne 2007 to 2013

Posted on 2014-09-03
5
Medium Priority
?
60 Views
Last Modified: 2014-11-20
Hello Experts,

We are in the process of migrating users from Exchange 2007 to 2013 in our environment.  We have only moved a select few test users at this time to get all of the problems worked out.  Recently we've noticed that users on the new Exchange 2013 server have problems sending excel documents to our users still on the Exchange 2007 server.  Below are the type of error messages we are receiving.  From the 2013 server we can send those same messages to outside email addresses.

Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
Remote Server returned '550 5.7.1 Requested action not taken: message refused'

Does anyone have any ideas?

Thanks
0
Comment
Question by:MMIC
  • 3
  • 2
5 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40301444
The error means what it says - the message was refused. Therefore the problem is probably with the Exchange 2007 server. I presume that users can send between themselves on the Exchange 2013 server?

The fact that they can send the other way is actually completely immaterial to the problem. With Exchange 2007 and higher, sending and receiving are separate things, so it is perfectly possible to work one way and not the other.

Simon.
0
 

Author Comment

by:MMIC
ID: 40301455
To add to this question excel documents under about 20k go through to our users with no problems.  Over that size and we get a bounce back.
0
 

Author Comment

by:MMIC
ID: 40301466
Simon, Yes the users can send between themselves on the Exchange 2013 serer.  I know it is possible for them to work one way and not the other as well as this is obviously happening.  I would like to know what setting it could be to make it work both ways.
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 2000 total points
ID: 40306160
I don't think this is a size issue. It is more likely third party interference. Anything between the servers? Antispam or AV tools?

Simon.
0
 

Author Closing Comment

by:MMIC
ID: 40454992
you were right.  this all had to do with symantic antivirus on the old exchange server.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question