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

Spoofed email addresses can send to Exchange 2000 Distribution Lists

Within Exchange 2000 I know it is possible to limit what users that can send to a distribution list (Exchange General/Message Restrictions/Accept Messages/Only From).

Thanks to one of the many viruses (beagle) I found an interesting hole.

If you spoof an email address that is allowed to send to the distribution list, it will send it to the distribution group. Not a good thing when it can go out to the entire company...

I have searched several places and can't find a fix for this. Maybe I'm searching the wrong places.

Is there a way to prevent spoofed addresses from sending to Exchange 2000 Distribution lists?
0
menhouse
Asked:
menhouse
  • 4
  • 3
  • 3
  • +1
1 Solution
 
dstoker509Commented:
No, it is a new feature for Exchange 2003.

http://www.microsoft.com/exchange/evaluation/features/default.asp
"Distribution lists restricted to authenticated users. You can allow only sending from authenticated users or specify which users can or cannot send mail to specified distribution lists. " 
0
 
David WilhoitSenior Consultant, ExchangeCommented:
Well, you can disallow your domain on the inbound email server.

Say you blocked *@yourdomain.com from being able to be a sending address from outside your org. Then when anyone spoofs the address, it would just get dropped. Are you using any kind of email filter tool?

D
0
 
menhouseAuthor Commented:
Kidego

What type email filtering are you looking for? I have a Symantec Antivirus Gateway on the outside that scans for spam and viruses before it hits the mail server. I actually had thought of doing what you are saying out there. Guess I was hoping that Microsoft had a fix or something simple I had missed. Seems like a very large hole.

0
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

 
timianoCommented:
Under security for the distribution group there is a property called send to, just set it so only domain users/authenticated users can send to that mail address, therefore requiring authentication, and anything from the outside world will not be able to authenticate.

Timiano
0
 
David WilhoitSenior Consultant, ExchangeCommented:
No, not really a hole. I mean, who should really think of having to block their own domain from being a sender from the other side?? The spammers have gotten very good, and the viruses are more sophisticated now. I believe SAG can do the domain name blocking for you, test it out.

Timiano, is that functionality available in E2K? I don't have it in front of me, I'm on E2K3 now....

D
0
 
timianoCommented:
Kidego,

In AD users and computers, find group, properties, security,....in the ACL Send to...make sure everyone doesn't have that permission, and restrict it to authenticated users/domain users, or similar group.

Timiano
0
 
timianoCommented:
and yes sorry, in E2k
0
 
David WilhoitSenior Consultant, ExchangeCommented:
cool, just asking. I need to build an E2K box for all the questions that get posted on it.... :)

D
0
 
menhouseAuthor Commented:
I realize that I'm most likely a rookie compared to you guys, but I do have the security set as timiano has recommended. I am still finding that a user that is specified to be able to send to the DL doesn't have to be authenticated to be able to send to the list. Now this a distribution that was carried over from an Exchange 5.5 upgrade so maybe there is something there... I have run several tests and as long as the email address matches, it doesn't have to authenticate. From what I understand E2K3 does work that way.

If I'm wrong please correct me.

In the mean time I have done what Kidego recommended and it has corrected the problem The solution works, also cuts out all the spoofed garbage related to all these viruses that are flying around.

I'm okay with that solution, but if I can get E2K to do it properly I think that's a better solution. I'm just not seeing it.

Thanks guys


0
 
David WilhoitSenior Consultant, ExchangeCommented:
Exactly. It's a good way to keep out the crap. It resolves more than one issue. I'll bet if a user inside your network tried to send to that DL, unless they wer authenticated, it wouldn't send. That's because they are legit users, and are bound by the security.

D
0
 
menhouseAuthor Commented:
Exactly, Local users can't send to it, unless they have the proper credentials.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now