hours of email)???
Thanks
Greg Marr
_
Get less junk mail with ninemsn Premium. Click here
http://ninemsn.com.au/premium/landing.asp
_
List posting FAQ: http
received since the
reboot, the get a message which states Can't open this item. There are no
messages in the event log that suggest a cause so I would really apprecaite
any advice.
Cheers
Greg Marr
_
Get less junk mail with ninemsn
Microsoft PSS; they have engineers standing by
just to help you.
Ed Crowley MCSE+Internet MVP
Freelance E-Mail Philosopher
Protecting the world from PSTs and Bricked Backups!T
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Greg Marr
Sent: Monday, October 27
.
Ed
--- Greg Marr [EMAIL PROTECTED] wrote:
We have set up our OWA to require two-factor
authentication (SecurID)
which eliminates any key-logging concerns but this
system is not cheap
at approx $300 AU ($160 US) per user.
The upside is that you can use the same system
We have set up our OWA to require two-factor authentication (SecurID)
which eliminates any key-logging concerns but this system is not cheap
at approx $300 AU ($160 US) per user.
The upside is that you can use the same system to authenticate all of
your remote access users (dial-up, VPN, etc)
credentials left behind by one of
your users which is where we happen to draw the line in terms of
functionality/security.
Greg
-Original Message-
From: Greg Marr
Sent: Thursday, 18 September 2003 11:31 AM
To: Exchange Discussions
Subject: RE: OWA front end server - licensing and security
We have
Hi
Had a friend ring me asking for advice on the following situation:
A company with two sites and a SBS2000 server in each site wants to be able to use the
same mail domain for users at each site. They are both configured to use a dial-up
connection to connect to the internet and the mail
Hi
Am currently evaluating GFIs MailEssentials anti-spam product and would like to try
the Black List functionality. Does anyone have a recommendation for a good black
list???
Thanks in advance
Greg
_
List posting FAQ:
Hi all
A couple of days ago, I set up a SMTP connector on my E2K SP3 server so
that I can block external email access for some users. I configured it
as per the MS document and all seemed to be working fine.
Today though, no-one seems to be able to send mail to one particular
domain. We have a
Assuming you are talking about E2K, there is a white-paper at
http://go.microsoft.com/fliwink/?linid=4721 which lists the ports that
are required to be opened at the end of the document.
From my investigations though, it depends very much on what type of
firewall you are using as to where to
Sorry - that link should be http://go.microsoft.com/fwlink/?linkid=4721
-Original Message-
From: Greg Marr
Sent: Friday, 14 February 2003 09:43
To: Exchange Discussions
Subject: RE: OWA in DMZ Zone
Assuming you are talking about E2K, there is a white-paper at
http://go.microsoft.com
Hi
I am currently investigating setting up OWA through ISA server and have
seen various recommendations about how to do this. The two obvious
options are;
* to place the Front-End server in a DMZ and open all required ports to
the internal network or;
* to publish OWA through ISA server
Hi
Would appreciate it if anyone could point me towards some documentation
that would help me out with the planning and execution of incorporating
a 5.5 organisation into a E2K organisation. I have found some basic
documentation but nothing that goes into too much detail
Thanks in advance.
Hi
Would really love some advice on the following:
* had a single Exchange 2000 Ent server (SP3) and confirmed that
OWA was working;
* installed a new E2K server (SP3) and configured it to be a Front
End server;
OWA still works if you connect directly to the Back End server but
Hi,
Would really appreciate any advice on the following migration plan:
We currently have an Exchange 5.5 (SP4) server which is a BDC on a NT4.0
domain - lets call it NT4DOMAIN. We have already created a Windows 2000
domain (W2KDOMAIN) and have migrated about half of the user accounts from
15 matches
Mail list logo