Using Blueyonder DNS I am seeing 62.49.146.170 as your primary MX record:-
C:\nslookup
Default Server: ns.cableinet.net
Address: 193.38.113.3
set type=mx
partition.co.uk
Server: ns.cableinet.net
Address: 193.38.113.3
partition.co.uk MX preference = 100, mail exchanger =
I am looking for some light reading/information to confirm the behaviour
with using OST's over a WAN link.
I have a remote office that connects to the main office over a 128k VPN
connection. This pipe is shared between 5 other users, including all their
internet traffic, so can get pretty slow at
always or let them choose the mode when
starting Outlook. When Outlook is off-line, it will always refer to the
OST.
Outlook 2003 with cached mode will improve this, but for now, this is a
pretty good option.
Aaron
-Original Message-
From: Gavin Hall [mailto:[EMAIL PROTECTED]
Sent
]
[mailto:[EMAIL PROTECTED] Behalf Of Gavin Hall
Sent: 19 September 2003 16:55
To: Exchange Discussions
Subject: RE: Use of OST's over WAN
Thanks I picked up on Martin's reference to Outlook 2003, currently looking
into it.
I realise that Outlook will always refer to the OST when Offline, but what
about
mode.
However with OL2003 in cache mode, it will always use the cached mail.
-Original Message-
From: Gavin Hall [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 9:03 AM
To: Exchange Discussions
Subject: RE: Use of OST's over WAN
Oh well, I think I've found the answer to my
I have an Exchange 2000 setup which is setup to relay certain email
addressees back-out to the internet, to their own personal ISP POP3
accounts. Since moving across from Exchange 5.5 I have been seeing several
mail failures within my Exchange Admin mailbox for these relay-addresses
where the
I have recently brought online a replacement Exchange2000 installation to
replace my Exchange5.5 install.
The system is running fine, although I notice the Exchange 2000
Systemmailbox account has over 1,000 items in it. I have seen
http://support.microsoft.com/support/kb/articles/Q253/7/84.asp
Can't you just delete them? They live in \system32\config and are called
appevent.evt, sysevent.evt and secevent.evt. You'll obviously need the
necessary privs to delete these files, alternatively fire up event viewer
and clear them out.
As the event log hasn't started I assume these files won't
8 matches
Mail list logo