Solved

Selective relay for MS Exchange 2003

Posted on 2013-02-05
5
457 Views
Last Modified: 2013-02-06
Hi All,

I have a Exchange 2003 front/back end setup and I have a requirement that we allow external members of a distribution list to send to everyone in the dist. list, even other external members. That's relaying, so I'm trying to figure out a way to allow this to happen and not make both of my Exchange servers open relays.

My testing so far indicates that making the internal server an open relay doesn't work because the external server refuses to relay the external recipients. I don't want to make the external server an open relay because we'll get blacklisted.

Does anyone have ideas on how to solve this problem?
0
Comment
Question by:rdropp
  • 3
5 Comments
 
LVL 11

Expert Comment

by:hecgomrec
Comment Utility
If these people are not "on the go" I can suggest you to authenticate or validate the relay for their IP addresses.

Another solution is to get them authenticated in your domain and select on your connector that only authenticated users can relay.

Good Luck
0
 

Author Comment

by:rdropp
Comment Utility
Unfortunately, they are at large external instutitutions and universitites. I don't think I can reliably identify a single IP address or even a range for their email servers and authentication is also not feasible either.
0
 
LVL 12

Accepted Solution

by:
FDiskWizard earned 500 total points
Comment Utility
I'm trying to make sure I'm understanding your requirements.

Anyone on the list needs to be able to email the distro list? right?

That isn't exactly relaying... That's a distro list sending to members of the list.

Just thought of something and looked at one of our internal lists to verify. I think under the Exchange General TAB you select: "Accept Messages...  ONLY FROM:  "
and add the Distro List so that members of the list can send to it.
0
 

Author Comment

by:rdropp
Comment Utility
It's a good point and helped solve the problem. The issue was that the expansion server was left as the default "any server in the organization", and we had the accept messages field set to "from everyone" . The problem is that the front end server is both faster and locked down, so it did most of the expanding and rejects all mail from non-internal addresses. Setting the expansion server to the internal server fixed the problem, since it can access the dist list and see that it's not relaying (as you correctly point out).

I've also reset the accept messages field to  the distribution list only, so that it's less likely to become a mini spam vector.

Thanks!
0
 

Author Closing Comment

by:rdropp
Comment Utility
It was a thoughtful question and suggestion that led me to the solution, even though it didn't directly solve it. I really appreciate it.
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This video discusses moving either the default database or any database to a new volume.

743 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

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now