Quite a lot of info has been posted to the following web page:
http://www.microsoft.com/exchange/support/e2k3owa.asp
David
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Martin
Blackstone
Sent: Saturday, November 22, 2003 9:07 AM
To: Exchange
I have done it, but with SSL (I made a self-signed cert with my own CA,
actually on the same server) and basic auth. I haven't tried it with
NTLM auth, so I can't say whether that should work or not. I would go
with SSL and basic for your testing, since that mirrors real-world
anyway.
David
Did you select Basic Authentication on the client?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Troels Majlandt
Sent: Monday, October 13, 2003 5:09 AM
To: Exchange Discussions
Subject: RPC over HTTP - username/password are refused
Hi there !
I have
See Q324021. You'll need to modify it a bit, but it shows you the
general framework.
-Original Message-
From: Dale Geoffrey Edwards [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 16, 2002 10:52 AM
To: Exchange Discussions
Subject: RE: bounce*@domain.com catch all alias
Rules Wizard,
You might find some info linked from
http://www.microsoft.com/exchange/evaluation/compare/default.asp to be
interesting or useful to you.
David
-Original Message-
From: Smith Joseph [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 12:25 PM
To: Exchange Discussions
All,
Our
The only messages that end up in the badmail folder should be NDRs that are in
response to NDRs. Because an NDR has no return address (on purpose), when you can't
deliver an NDR, you have to do something special. Exchange 2000 puts such messages in
the badmail directory.
I can't recommend
That's correct. Here is how you should remember it:
- If the Exchange 2000 system is the authoritative system for the
domain, and if an incoming recipient doesn't exist in Exchange 2000, it
should be NDR'd, then: put the domain into a recipient policy and check
the box that says This Exchange
Microsoft will be hosting a chat on Exchange 5.5 to Exchange 2000
Migrations on April 30 and it is open to all customers. It will be at
10:00 AM - 11:00 AM Pacific Time or 17:00 - 18:00 GMT. You can learn
more by visiting: http://microsoft.com/technet/itcommunity/chats/
The chat will be staffed
Create a Message Filter entry for the domain that is in the From:, then
apply it to the virtual servers that accept mail from the Internet as
described in Q261087.
David
-Original Message-
From: Mark Levesque [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 11, 2002 12:39 PM
To:
Is this a person who is not an Exchange user, but receives mail from
Exchange systems? The default for Exchange is to wrap lines at around
70 characters for outbound plain text messages. You can turn it off.
This is a setting on the IMS in 5.5, or the Internet Message Format in
Exchange 2000
FYI this registry key was introduced in 5.5 SP1.
David
-Original Message-
From: Finch Brett [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 19, 2002 12:00 PM
To: Exchange Discussions
Subject: RE: Q article confirmation
Yeah but I'm fed up with calling PSS, that's why I thought I
What you should do is to create one SMTP connector for each smart host,
set its source to be the E2K server that the MX records point it, add
all of the address spaces that you want to accept for relay to the
Address Spaces tab, and check the box on that tab that says Allow
inbound relay to these
There are 3 categories that you want to synchronize between orgs:
1) User information (so you can have a synchronized GAL). That article
talks about how to do that using the ADC. This is one of the two things
that the ADC can do, synch users, groups, contacts, etc. See Q264482
for how far you
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q279860
http://www.microsoft.com/TechNet/security/mail/excrelay.asp
-Original Message-
From: Bravo, Liliana [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 10:08 AM
To: Exchange Discussions
Subject: Msx5.5 versus SPAM
,
it seems unlikely that it can be a loop, and since it comes back within
a couple of minutes, it seems as though it is not using those SMTP
settings.
-Original Message-
From: David Lemson [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 22, 2002 1:53 PM
To: Exchange Discussions
Subject: RE
The Delivery Report timeouts are set on the SMTP Virtual Server that
would generate it. It doesn't matter what kind of connector is used.
-Original Message-
From: Morrison, Gordon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 7:43 AM
To: Exchange Discussions
Subject:
1) no it doesn't
2) he can't have it anyway
-Original Message-
From: Chris Scharff [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 9:56 AM
To: Exchange Discussions
Subject: RE: Forcing encrypted RPC connections with Outlook client.
Perhaps the DMS version of the client
Oops, sorry about the brief tone, I meant that to go to only Chris :-)
Elaborating on 2) - the DMS version of Outlook is only available to
authorized US DoD customers.
David
-Original Message-
From: David Lemson [mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 16, 2002 8:20 AM
Unless I'm seriously misunderstanding what you're saying, that is...
- Original Message -
From: David Lemson [EMAIL PROTECTED]
To: Exchange Discussions [EMAIL PROTECTED]
Sent: Tuesday, February 12, 2002 8:10 PM
Subject: RE: win.dat attachments
The key string is Exchange Rich Text or Outlook
I recommend reading this white paper, which details the steps you need
to go through:
http://www.microsoft.com/Exchange/techinfo/deployment/2000/E2KFrontBack.
asp
David
-Original Message-
From: Varghese, Wilson [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 25, 2002 10:26 AM
To:
I believe they're suggesting that you use POP or IMAP and SMTP as the
protocols from Outlook to the server. Of course, you could do the same
with Exchange, but look at the functionality difference.
David
-Original Message-
From: Milton R Dogg [mailto:[EMAIL PROTECTED]]
Sent: Saturday,
I would suggest calling Microsoft Product Support Services. If your server is really
named COMMS, then you probably need professional assistance on this issue.
-Original Message-
From: Haris Dechapunya [mailto:[EMAIL PROTECTED]]
Sent: Saturday, January 19, 2002 1:47 PM
To: Exchange
Try Exchange 2000 SP2. (on the server, not the machine running the ESM
console)
I'm not positive that it will fix the situation you are hitting, but
several issues related to counts being off were fixed in SP2.
David
-Original Message-
From: Cook, David A. [mailto:[EMAIL PROTECTED]]
No. The only reason that checkbox on the IMC is there is in case you
have clients that are pre-Outlook 98. If you do, you may want to strip
S/MIME so that those clients don't get confused. Nowadays, this is
almost never an issue. The default has changed in Exchange 2000 to
allow S/MIME.
It depends what bad spammer email address means. If the part of the
address to the right of the @ sign truly does not exist in DNS (e.g.,
zjeorheorejreohre.net), then it should get thrown away very quickly as
soon as the queue is processed. However, if the part to the right side
of the @ sign
Do not underestimate the power of a dictionary attack. Especially if
the alias of the DL is less than 8 characters long, it is not hard to
manage a brute-force attack.
-Original Message-
From: Blunt, James H (Jim) [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 07, 2002 3:12 PM
To:
Here are the facts:
- The setting on an Exchange server This is a Front End Server in ESM
has no effect on SMTP. It only affects POP, IMAP, and HTTP. The design
of Exchange is that all Exchange servers are inbound servers for SMTP.
Outbound SMTP is controlled via SMTP Connectors.
- Some
The Exchange 2000 / Windows 2000 SMTP Service default is 15 and can be
modified using \inetpub\adminscripts\adsutil.vbs. The metabase key to
see is smtpsvc/1/HopCount. With the informatio we have, Microsoft and
Exchange does not believe that a limit like 100 is appropriate.
However, if you
28 matches
Mail list logo
