Pages

Search

Front-End server question - Microsoft Exchange

Front-End server question - Microsoft Exchange

Front-End server question

Posted: 26 Feb 2005 09:18 AM PST

We are running Windows 2003 Ent. and Exchang 2003 Ent. Although I guess
that goes without saying due to the fact that we are setting up a Front
End/Back End environment. With that said, are you saying that you can only
have one Exchange Organization in the Forest? Even if we will be running
Enterprise editions of Windows and Exchange?

If not, which is best? One or two Exchange Organizations? We start
installing Monday!


Clayton



"Rodney R. Fournier [MVP]" <spam.die.nw-america.com> wrote in
message news:phx.gbl... 

OWA on port 8080? Possible?

Posted: 26 Feb 2005 05:41 AM PST

Thanks for the reply, Mark. But I don't quite follow your comment. Let me try
to clarify my question.

I want to keep the non-Exchange websites on the standard HTTP port (80) to
allow general internet users to access these sites without the need to append
port numbers to the URL (e.g.: www.mysite.com:8080). In contrast, I have only
a small group of Exchange users so I don't mind asking them to add a port
number (such as 8080) to the URL to reach the Exchange server.

Does anyone have experience moving the Excahange HTTP virtual directories
(i.e. the default IIS website) to another port? Furthermore, has anyone
succeeded in continuing to use host headers to distinguish sites on the
standard port while simultanseously enabling SSL for the Exchange website on
a different port?

Example:
Name Port Identified by:
------ ------ ----------------
website1 80 host header1
website2 80 host header2
Exchange website 8080 port number
(w/ SSL enabled)

Thanks,
Kerry

"Mark Arnold [MVP]" wrote:
 

Alternative SMTP And POP Connectors

Posted: 24 Feb 2005 07:21 PM PST

Just to verify then,
Providing pop and smtp via exchange will not use any of my exchange licensing?

"Mark Arnold [MVP]" wrote:
 

Limit on Incoming Attachments

Posted: 24 Feb 2005 01:01 PM PST



"Lanwench [MVP - Exchange]" wrote:
 


Thanks for your reply. Here is the message that they got for my first
question:

Joe Smith on 2/24/2005 12:35 PM
This message is larger than the current system limit or the recipient's
mailbox is full. Create a shorter message body or remove attachments and try
sending it again.
<exch1.mycompany.local #5.2.3>

I checked Joe Smith's mailbox, and it is not anywhere near capacity. Other
users have much larger mailboxes than he does.

As far as question #2, I will check and see. Thanks

I can't send messages to "some" domains

Posted: 24 Feb 2005 11:13 AM PST

No, I guess I don't. I'm doing it now.
In the form to a new mx record what is the "host or child domain"????

"Toby" escribió:
 

Multiple Mailboxes

Posted: 24 Feb 2005 07:17 AM PST

Have a look at: http://www.lucatec.de/mask
It is a small utility which automates certain routine tasks if you're
working with a Microsoft Exchange Server and have set up public eMail
accounts for individual departments, branches or tasks of your organization.

Greetings
Steffi


"Smurfman" <postalias> wrote in message
news:com... 
as 
and 

Accepting all email

Posted: 24 Feb 2005 07:03 AM PST

Hi Tony,

I used the link you posted and have the system working after a fashion.

Outside people no longer get the Underliverable messages. Admin receives the
Undeliverable message. I can open that message to see the original message
which I can forward... There has got to be an easier way!? Not to worry, this
solution is good for now.

Thanks for the help.
Chris

"Tony Eversole" wrote:
 

160,000 files in the vsi 1\Queue folder - help!

Posted: 24 Feb 2005 06:53 AM PST

It only applies to email coming in during the SMTP session. If the mail is
already in the queue, it will have to go through normal cycles, but all
future email exchanges would honor this setting.

Tony Eversole

"Gerard McGovern" wrote:
 

How to get an alert about free space in private database Exchange

Posted: 24 Feb 2005 06:01 AM PST

Mieke wrote: 

Implement mailbox quotas - default set on the store, exceptions made per
mailbox properties.
That way nobody can go over their limit. You will have to do the math to see
what limits you can allow - # of users * max size of quota. Also include
room for deleted item retention, which I strongly encourage you to
implement. I don't think any Exchange server, regardless of version, should
be operating without quotas for *all* mailboxes.

You have an awful lot of users to be using Exchange Standard, btw. 

1 e-mail domain in 2 AD's?

Posted: 23 Feb 2005 08:13 PM PST

Our issue ended up being our Barracuda spam filter box. It can only queary
one LDAP server per SMTP domain. So since the user's account was in a
different AD domain LDAP would reply with the user doesn't exist. Once we
turned that feature off in the Spam filter AD took care of the problem.

"Toby" wrote:
 

Running OWA on a different machine

Posted: 23 Feb 2005 08:07 AM PST

It would be on a Windows 2003 platform yes, but there is noting to say
it should be a DC at all.