Blocking UCE relaying
Title: Blocking UCE relaying I am familiar with blocking UCE relaying on an Exchange 5.5 system but not in this particular example. Typically I just: go to the routing tab of the IMS, click on the Routing Restrictions button check "Hosts and clients with These IP addresses" and verify nothing is listed in the list boxes This works great in typical exchange environments. I have a customer who has a different setup. 90% of his clients are remote and connecting using POP3 clients. No VPN, no OWA. They typically connect using a local ISP and connect this way using a variety of e-mail clients. Different IP addresses each time. In this scenario, the above doesn't work. My guess would be that you need to check the "Hosts and clients that successfully authenticate" check box. And have the clients configure authentication credentials in their e-mail client. Since I haven't been in situation which required this before I thought I would run it past the list first. Any thoughts on this? TIA Chris Bodnar Network Engineer Essent Corporation 610-559- X:24 List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Blocking UCE relaying
Title: Message Chris, That's what we're doing here. The trick is to get all the users to set up the authentication prior to changing the server! Dave Warner Technology Coordinator, MCSE Traverse Bay Area Intermediate Schools -Original Message-From: MS-Exchange Admin Issues [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 4:08 PMTo: MS-Exchange Admin IssuesSubject: Blocking UCE relaying I am familiar with blocking UCE relaying on an Exchange 5.5 system but not in this particular example. Typically I just: go to the routing tab of the IMS, click on the Routing Restrictions button check "Hosts and clients with These IP addresses" and verify nothing is listed in the list boxes This works great in typical exchange environments. I have a customer who has a different setup. 90% of his clients are remote and connecting using POP3 clients. No VPN, no OWA. They typically connect using a local ISP and connect this way using a variety of e-mail clients. Different IP addresses each time. In this scenario, the above doesn't work. My guess would be that you need to check the "Hosts and clients that successfully authenticate" check box. And have the clients configure authentication credentials in their e-mail client. Since I haven't been in situation which required this before I thought I would run it past the list first. Any thoughts on this? TIA Chris Bodnar Network Engineer Essent Corporation 610-559- X:24List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Re: Blocking UCE relaying
Title: Message
What do you mean excatly py setting up the
authentication in Outlook express for example: I have the same situation for all
my Clients!
Sent by : [EMAIL PROTECTED] or [EMAIL PROTECTED]
- Original Message -
From:
Dave
Warner
To: MS-Exchange Admin
Issues
Sent: Tuesday, March 26, 2002 11:21
PM
Subject: RE: Blocking UCE relaying
Chris,
That's what we're doing here. The trick is to get all the users to set
up the authentication prior to changing the server!
Dave
Warner
Technology Coordinator, MCSE
Traverse Bay Area Intermediate Schools
-Original Message-From: MS-Exchange
Admin Issues [mailto:[EMAIL PROTECTED]] Sent:
Tuesday, March 26, 2002 4:08 PMTo: MS-Exchange Admin
IssuesSubject: Blocking UCE relaying
I am familiar with
blocking UCE relaying on an
Exchange 5.5
system but not in this
particular example.
Typically I
just:
go to the routing tab of
the IMS,
click on the Routing
Restrictions button
check "Hosts and clients
with These IP addresses"
and verify nothing is
listed in the list boxes
This works great in
typical exchange environments. I have a customer who has a different setup.
90% of his clients are remote and connecting using POP3 clients.
No VPN, no OWA. They typically connect using a local ISP and
connect this way using a variety of e-mail clients. Different IP addresses each time. In this scenario, the above doesn't work.
My guess would be that
you need to check the "Hosts
and clients that successfully authenticate" check box. And have the clients
configure authentication credentials in their e-mail client.
Since I haven't been in
situation which required this before I thought I would run it past the list
first.
Any thoughts on
this?
TIA
Chris Bodnar
Network
Engineer
Essent
Corporation
610-559-
X:24List Charter and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htmList
Charter and FAQ
at:http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
