| Author |
Message |
SP
Guest
|
 Posted:
Fri May 27, 2005 2:01 pm Post subject:
exchange basics |
|
|
Hi
Of POP, SMTP, and whatever else, is Exchange one of those ? Or is Exchange
native to itself ? A class of its own - like POP and SMTP ?
I understand Exchange itself can't be POP since it uses POP connector to
connect to some POP server.
Steve
|
|
| Back to top |
|
 |
Al Mulnick
Guest
|
| Posted:
Sat May 28, 2005 1:38 am Post subject:
Re: exchange basics |
|
|
Yikes. That's confusing.
Exchange is a MTA - Message Transfer Agent. SMTP is a message transport
protocol. Exchange uses SMTP to transport messages (by default).
Exchange is a message store. It stores your messages in a database for you
the client using a MUA - message user agent (such as Outlook) to come pick
it up later.
POP3 is a protocol for picking up your mail from a message store utilizing a
MUA. Exchange supports POP3.
POP3 Connectors are for people that want to pick up mail from an ISP mailbox
and put it into Exchange. POP3 is still a message retrieval protocol. It
is not for sending. It never has been. SMTP is a transport protocol which
Exchange uses to transport messages to other servers. When it does this
transaction, it is the 'client' in the client-server terminology used to
describe SMTP transactions. Your MUA, if configured to use POP3 as it's
message retrieval protocol, will also be configured to use a SMTP MTA (all
that really means is that you send your outgoing mail to a host that
understands and listens for SMTP commands on a well known port (usually)) if
you hope to send mail to anybody other than yourself. Not that talking to
yourself is a bad thing, it's just that if you go to the trouble to pick up
your mail, it would seem like a good idea to send something to others so you
can share wit and humor and pictures of the kids doing silly things with
water balloons or mud. I digress. In this situation, your MUA will also be
a client to a SMTP MTA.
Exchange natively speaks SMTP and will communicate as a POP3 host if so
configured. If you go that route, I suggest you utilize front end servers
so you can move mailboxes around without reconfiguring MUA's.
You can read more about Exchange at http://www.microsoft.com/exchange
-al
"SP" <none> wrote in message news:%23jc3pqpYFHA.2756@tk2msftngp13.phx.gbl...
| Quote: | Hi
Of POP, SMTP, and whatever else, is Exchange one of those ? Or is
Exchange native to itself ? A class of its own - like POP and SMTP ?
I understand Exchange itself can't be POP since it uses POP connector to
connect to some POP server.
Steve
|
|
|
| Back to top |
|
|
SP
Guest
|
| Posted:
Sat May 28, 2005 4:04 am Post subject:
Re: exchange basics |
|
|
Thanks very much ... I really appreciate your reply on Exchange for Dummies.
Questions:
1. POP3 host if so configured: Does that mean Exchange is not configured as
a POP3 host out-of-the-box ?
2. If Exchange is not configured as a POP3 host, what does it use as a
message retrieval protocol ? Is it Exchange native ?
3. Of POP3 host and Exchange native host, can Exchange support both at the
same time ? Or just one or the other ?
*In other words, on the MUAs side, say, we have 10 users running Outlook
2003, and we have Exchange configured as POP3 host. Can 5 of the users
configure their Outlook to connect to POP3 server while the other 5 users
configure their Outlook to connect to Exchange server ?
4. Is there any loss or gain of functionalities if Exchange is configured as
POP3 host ?
5. What are other MTAs available out there ?
Thanks again
Steve
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:%23WpTdwvYFHA.612@TK2MSFTNGP12.phx.gbl...
| Quote: | Yikes. That's confusing.
Exchange is a MTA - Message Transfer Agent. SMTP is a message transport
protocol. Exchange uses SMTP to transport messages (by default).
Exchange is a message store. It stores your messages in a database for
you the client using a MUA - message user agent (such as Outlook) to come
pick it up later.
POP3 is a protocol for picking up your mail from a message store utilizing
a MUA. Exchange supports POP3.
POP3 Connectors are for people that want to pick up mail from an ISP
mailbox and put it into Exchange. POP3 is still a message retrieval
protocol. It is not for sending. It never has been. SMTP is a transport
protocol which Exchange uses to transport messages to other servers. When
it does this transaction, it is the 'client' in the client-server
terminology used to describe SMTP transactions. Your MUA, if configured to
use POP3 as it's message retrieval protocol, will also be configured to
use a SMTP MTA (all that really means is that you send your outgoing mail
to a host that understands and listens for SMTP commands on a well known
port (usually)) if you hope to send mail to anybody other than yourself.
Not that talking to yourself is a bad thing, it's just that if you go to
the trouble to pick up your mail, it would seem like a good idea to send
something to others so you can share wit and humor and pictures of the
kids doing silly things with water balloons or mud. I digress. In this
situation, your MUA will also be a client to a SMTP MTA.
Exchange natively speaks SMTP and will communicate as a POP3 host if so
configured. If you go that route, I suggest you utilize front end servers
so you can move mailboxes around without reconfiguring MUA's.
You can read more about Exchange at http://www.microsoft.com/exchange
-al
"SP" <none> wrote in message
news:%23jc3pqpYFHA.2756@tk2msftngp13.phx.gbl...
Hi
Of POP, SMTP, and whatever else, is Exchange one of those ? Or is
Exchange native to itself ? A class of its own - like POP and SMTP ?
I understand Exchange itself can't be POP since it uses POP connector to
connect to some POP server.
Steve
|
|
|
| Back to top |
|
|
Al Mulnick
Guest
|
| Posted:
Sat May 28, 2005 7:17 pm Post subject:
Re: exchange basics |
|
|
In-line:
"SP" <anon@msn.com> wrote in message
news:uWbsTAxYFHA.3572@TK2MSFTNGP12.phx.gbl...
| Quote: | Thanks very much ... I really appreciate your reply on Exchange for
Dummies.
Questions:
1. POP3 host if so configured: Does that mean Exchange is not configured
as a POP3 host out-of-the-box ?
Can't recall at the moment. Bet you can find that information at |
http://www.microsoft.com/exchange/library Even if it's not out of the box,
that's trivial to configure for users. See the help files for exact steps.
| Quote: | 2. If Exchange is not configured as a POP3 host, what does it use as a
message retrieval protocol ? Is it Exchange native ?
MAPI is the de-facto standard. Outlook uses MAPI to communicate with |
Exchange stores. POP3 has the disadvantage of wanting to download the
messages from the central store to the client store. Makes recovery of
messages messy. It also is very basic in it's functionality and although it
has it's uses, has no server side rules, or other rich features that some
users want. Shared calendaring for example. MAPI allows for those
features.
| Quote: | 3. Of POP3 host and Exchange native host, can Exchange support both at the
same time ? Or just one or the other ?
Supports both and then some. Exchange is a great tool to deploy as an |
upgrade from other systems because it can talk so many protocols at the same
time.
| Quote: | *In other words, on the MUAs side, say, we have 10 users running
Outlook 2003, and we have Exchange configured as POP3 host. Can 5 of the
users configure their Outlook to connect to POP3 server while the other 5
users configure their Outlook to connect to Exchange server ?
I think you mean can 5 of the MUA's connect to the Exchange store via POP3 |
(or IMAP right?) and 5 other MUA's connect via MAPI (Outlook corporate
mode). If that's what you meant, then yes. Even a step further: the
clients can switch back and forth between client protocols keeping in mind
where the mail ends up. Best not to do that, but they can. Just for fun,
they can also access via WebDav and/or HTTP. The nice thing about that is
you can use other client types such as Ximian's (Novell now) Linux Outlook
knock-off client (MUA). Gives a richer feature set to the end user.
| Quote: | 4. Is there any loss or gain of functionalities if Exchange is configured
as POP3 host ?
It's not the host to worry about. Think of it as a multi-protocol message |
router. It'll answer for many protocols and provide the mail the way the
protocol requires it. It understands and speaks most of the protocols out
there (might be all of them, but I haven't checked to verify all of them.)
However, you are subject to the limitations of the protocol itself. In the
case of POP3, you are limited to it's abilities such as downloading from the
server else finding another way to deal with the messages. Note that some
MUA's will deal pretty well with POP3 functionality by not strictly
following the RFC and instead allowing things like leaving the messages on
the server-side store and so on.
| Quote: | 5. What are other MTAs available out there ?
For just POP3? Many. Too many to mention. It's usually needs based to |
figure out which one is best for you. Some of it is preference as well.
Even Windows Server 2003 includes a pop and smtp server these days and is
intended for small shop impelementations.
Does that help?
Al
| Quote: |
Thanks again
Steve
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:%23WpTdwvYFHA.612@TK2MSFTNGP12.phx.gbl...
Yikes. That's confusing.
Exchange is a MTA - Message Transfer Agent. SMTP is a message transport
protocol. Exchange uses SMTP to transport messages (by default).
Exchange is a message store. It stores your messages in a database for
you the client using a MUA - message user agent (such as Outlook) to come
pick it up later.
POP3 is a protocol for picking up your mail from a message store
utilizing a MUA. Exchange supports POP3.
POP3 Connectors are for people that want to pick up mail from an ISP
mailbox and put it into Exchange. POP3 is still a message retrieval
protocol. It is not for sending. It never has been. SMTP is a
transport protocol which Exchange uses to transport messages to other
servers. When it does this transaction, it is the 'client' in the
client-server terminology used to describe SMTP transactions. Your MUA,
if configured to use POP3 as it's message retrieval protocol, will also
be configured to use a SMTP MTA (all that really means is that you send
your outgoing mail to a host that understands and listens for SMTP
commands on a well known port (usually)) if you hope to send mail to
anybody other than yourself. Not that talking to yourself is a bad thing,
it's just that if you go to the trouble to pick up your mail, it would
seem like a good idea to send something to others so you can share wit
and humor and pictures of the kids doing silly things with water balloons
or mud. I digress. In this situation, your MUA will also be a client to
a SMTP MTA.
Exchange natively speaks SMTP and will communicate as a POP3 host if so
configured. If you go that route, I suggest you utilize front end
servers so you can move mailboxes around without reconfiguring MUA's.
You can read more about Exchange at http://www.microsoft.com/exchange
-al
"SP" <none> wrote in message
news:%23jc3pqpYFHA.2756@tk2msftngp13.phx.gbl...
Hi
Of POP, SMTP, and whatever else, is Exchange one of those ? Or is
Exchange native to itself ? A class of its own - like POP and SMTP ?
I understand Exchange itself can't be POP since it uses POP connector to
connect to some POP server.
Steve
|
|
|
| Back to top |
|
|
SP
Guest
|
| Posted:
Mon May 30, 2005 12:22 am Post subject:
Re: exchange basics |
|
|
Thank you very much...thank you.
"...keep in mind where the mail ends up. Best not to do that...": Why not
? I'm thinking, the mail will end up in the inbox, right ? Where else ?
Or, is that not the best place for email to be?
POP3 limitations: no server rules, no calendar sharing, downloading of
messages
-What are some serve-side rules that are essential to the day-to-day
messaging operation (the must-have rules)?
-If messages can be stored on server instead of downloading, how do you
deal with storage capacity ? Is it just a matter of setting quota on
individual accounts ? Does Exchange inform users if their accounts approach
limit ? In your experience, how quickly (on average) is the limit of
individual accounts run out ? What would be an optimal limit for a quota ?
Ultimately, we want to run our own Exchange server - migrating our users
from POP3-based to Exchange. I really appreciate your time and valuable
information here.
Steve
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:O$%230u$4YFHA.1412@TK2MSFTNGP12.phx.gbl...
| Quote: | In-line:
"SP" <anon@msn.com> wrote in message
news:uWbsTAxYFHA.3572@TK2MSFTNGP12.phx.gbl...
Thanks very much ... I really appreciate your reply on Exchange for
Dummies.
Questions:
1. POP3 host if so configured: Does that mean Exchange is not configured
as a POP3 host out-of-the-box ?
Can't recall at the moment. Bet you can find that information at
http://www.microsoft.com/exchange/library Even if it's not out of the box,
that's trivial to configure for users. See the help files for exact steps.
2. If Exchange is not configured as a POP3 host, what does it use as a
message retrieval protocol ? Is it Exchange native ?
MAPI is the de-facto standard. Outlook uses MAPI to communicate with
Exchange stores. POP3 has the disadvantage of wanting to download the
messages from the central store to the client store. Makes recovery of
messages messy. It also is very basic in it's functionality and although
it has it's uses, has no server side rules, or other rich features that
some users want. Shared calendaring for example. MAPI allows for those
features.
3. Of POP3 host and Exchange native host, can Exchange support both at
the same time ? Or just one or the other ?
Supports both and then some. Exchange is a great tool to deploy as an
upgrade from other systems because it can talk so many protocols at the
same time.
*In other words, on the MUAs side, say, we have 10 users running
Outlook 2003, and we have Exchange configured as POP3 host. Can 5 of the
users configure their Outlook to connect to POP3 server while the other 5
users configure their Outlook to connect to Exchange server ?
I think you mean can 5 of the MUA's connect to the Exchange store via POP3
(or IMAP right?) and 5 other MUA's connect via MAPI (Outlook corporate
mode). If that's what you meant, then yes. Even a step further: the
clients can switch back and forth between client protocols keeping in mind
where the mail ends up. Best not to do that, but they can. Just for fun,
they can also access via WebDav and/or HTTP. The nice thing about that is
you can use other client types such as Ximian's (Novell now) Linux Outlook
knock-off client (MUA). Gives a richer feature set to the end user.
4. Is there any loss or gain of functionalities if Exchange is configured
as POP3 host ?
It's not the host to worry about. Think of it as a multi-protocol message
router. It'll answer for many protocols and provide the mail the way the
protocol requires it. It understands and speaks most of the protocols out
there (might be all of them, but I haven't checked to verify all of them.)
However, you are subject to the limitations of the protocol itself. In
the case of POP3, you are limited to it's abilities such as downloading
from the server else finding another way to deal with the messages. Note
that some MUA's will deal pretty well with POP3 functionality by not
strictly following the RFC and instead allowing things like leaving the
messages on the server-side store and so on.
5. What are other MTAs available out there ?
For just POP3? Many. Too many to mention. It's usually needs based to
figure out which one is best for you. Some of it is preference as well.
Even Windows Server 2003 includes a pop and smtp server these days and is
intended for small shop impelementations.
Does that help?
Al
Thanks again
Steve
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:%23WpTdwvYFHA.612@TK2MSFTNGP12.phx.gbl...
Yikes. That's confusing.
Exchange is a MTA - Message Transfer Agent. SMTP is a message transport
protocol. Exchange uses SMTP to transport messages (by default).
Exchange is a message store. It stores your messages in a database for
you the client using a MUA - message user agent (such as Outlook) to
come pick it up later.
POP3 is a protocol for picking up your mail from a message store
utilizing a MUA. Exchange supports POP3.
POP3 Connectors are for people that want to pick up mail from an ISP
mailbox and put it into Exchange. POP3 is still a message retrieval
protocol. It is not for sending. It never has been. SMTP is a
transport protocol which Exchange uses to transport messages to other
servers. When it does this transaction, it is the 'client' in the
client-server terminology used to describe SMTP transactions. Your MUA,
if configured to use POP3 as it's message retrieval protocol, will also
be configured to use a SMTP MTA (all that really means is that you send
your outgoing mail to a host that understands and listens for SMTP
commands on a well known port (usually)) if you hope to send mail to
anybody other than yourself. Not that talking to yourself is a bad
thing, it's just that if you go to the trouble to pick up your mail, it
would seem like a good idea to send something to others so you can share
wit and humor and pictures of the kids doing silly things with water
balloons or mud. I digress. In this situation, your MUA will also be a
client to a SMTP MTA.
Exchange natively speaks SMTP and will communicate as a POP3 host if so
configured. If you go that route, I suggest you utilize front end
servers so you can move mailboxes around without reconfiguring MUA's.
You can read more about Exchange at http://www.microsoft.com/exchange
-al
"SP" <none> wrote in message
news:%23jc3pqpYFHA.2756@tk2msftngp13.phx.gbl...
Hi
Of POP, SMTP, and whatever else, is Exchange one of those ? Or is
Exchange native to itself ? A class of its own - like POP and SMTP ?
I understand Exchange itself can't be POP since it uses POP connector
to connect to some POP server.
Steve
|
|
|
| Back to top |
|
|
Al Mulnick
Guest
|
| Posted:
Mon May 30, 2005 6:08 am Post subject:
Re: exchange basics |
|
|
Nope. That's the problem. If you find users switching between client
types, you often find trouble calls to go with it because the user will
often pull the mail to a different store (as in POP3) and then wonder why it
isn't there later. The other protocols do leave it in the central mail
store, so you're right, it wouldn't be a big deal.
| Quote: | -What are some serve-side rules that are essential to the day-to-day
messaging operation (the must-have rules)?
-If messages can be stored on server instead of downloading, how do you
deal with storage capacity ? Is it just a matter of setting quota on
individual accounts ? Does Exchange inform users if their accounts
approach limit ? In your experience, how quickly (on average) is the limit
of individual accounts run out ? What would be an optimal limit for a
quota ?
|
Unfortunately, there are no hard and fast rules here. Every organization
has their own concepts and ideas about storage. As an example, I've seen
some that believe they can do their job with 10MB limits while others
require 1GB limits. Others don't even need limits based on the way their
user population utilizes mail and storage.
Exchange can inform and enforce quotas on mail storage. You can set it for
whatever you want. I think the best approach is to figure out how long you
can be without mail, figure out how large the stores can become and still be
restored from a total melt-down type of disaster (restored to service vs.
played from tape) and work back to the quota limits from there. Balance
that with the way folks use email. I usually go by the 80-10-10 rule. 10%
of the people will use the most space, 80% will use some of it but stay
within whatever limits you set, and 10% when asked will respond "I have
email?"
If you're users are used to sending mail now, you may be able to track the
mail on the system you have and get a feel for the way they do business
today. That might provide some insight into what you're in for.
Server side rules? That is so totally dependent and unique based on users
and organization that it's hard to tell. Many are using the rules today in
their client side activities, but that is only good when that client and
profile are in being used. If you switch to Exchange, they may be using
different protocols to access the server and may want a consistent look and
feel when they access the mail store. That would require some server side
rules so that when they use OWA, the rules are already applied. When they
use MAPI, IMAP, etc the same rules have already been applied and they get
consistency and therefore more productivity (hopefully anyway, right?).
Does that help?
"SP" <none> wrote in message news:O1FUCPIZFHA.2128@TK2MSFTNGP15.phx.gbl...
| Quote: | Thank you very much...thank you.
"...keep in mind where the mail ends up. Best not to do that...": Why
not ? I'm thinking, the mail will end up in the inbox, right ? Where
else ? Or, is that not the best place for email to be?
POP3 limitations: no server rules, no calendar sharing, downloading of
messages
-What are some serve-side rules that are essential to the day-to-day
messaging operation (the must-have rules)?
-If messages can be stored on server instead of downloading, how do you
deal with storage capacity ? Is it just a matter of setting quota on
individual accounts ? Does Exchange inform users if their accounts
approach limit ? In your experience, how quickly (on average) is the limit
of individual accounts run out ? What would be an optimal limit for a
quota ?
Ultimately, we want to run our own Exchange server - migrating our users
from POP3-based to Exchange. I really appreciate your time and valuable
information here.
Steve
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:O$%230u$4YFHA.1412@TK2MSFTNGP12.phx.gbl...
In-line:
"SP" <anon@msn.com> wrote in message
news:uWbsTAxYFHA.3572@TK2MSFTNGP12.phx.gbl...
Thanks very much ... I really appreciate your reply on Exchange for
Dummies.
Questions:
1. POP3 host if so configured: Does that mean Exchange is not configured
as a POP3 host out-of-the-box ?
Can't recall at the moment. Bet you can find that information at
http://www.microsoft.com/exchange/library Even if it's not out of the
box, that's trivial to configure for users. See the help files for exact
steps.
2. If Exchange is not configured as a POP3 host, what does it use as a
message retrieval protocol ? Is it Exchange native ?
MAPI is the de-facto standard. Outlook uses MAPI to communicate with
Exchange stores. POP3 has the disadvantage of wanting to download the
messages from the central store to the client store. Makes recovery of
messages messy. It also is very basic in it's functionality and although
it has it's uses, has no server side rules, or other rich features that
some users want. Shared calendaring for example. MAPI allows for those
features.
3. Of POP3 host and Exchange native host, can Exchange support both at
the same time ? Or just one or the other ?
Supports both and then some. Exchange is a great tool to deploy as an
upgrade from other systems because it can talk so many protocols at the
same time.
*In other words, on the MUAs side, say, we have 10 users running
Outlook 2003, and we have Exchange configured as POP3 host. Can 5 of
the users configure their Outlook to connect to POP3 server while the
other 5 users configure their Outlook to connect to Exchange server ?
I think you mean can 5 of the MUA's connect to the Exchange store via
POP3 (or IMAP right?) and 5 other MUA's connect via MAPI (Outlook
corporate mode). If that's what you meant, then yes. Even a step
further: the clients can switch back and forth between client protocols
keeping in mind where the mail ends up. Best not to do that, but they
can. Just for fun, they can also access via WebDav and/or HTTP. The
nice thing about that is you can use other client types such as Ximian's
(Novell now) Linux Outlook knock-off client (MUA). Gives a richer
feature set to the end user.
4. Is there any loss or gain of functionalities if Exchange is
configured as POP3 host ?
It's not the host to worry about. Think of it as a multi-protocol
message router. It'll answer for many protocols and provide the mail the
way the protocol requires it. It understands and speaks most of the
protocols out there (might be all of them, but I haven't checked to
verify all of them.) However, you are subject to the limitations of the
protocol itself. In the case of POP3, you are limited to it's abilities
such as downloading from the server else finding another way to deal with
the messages. Note that some MUA's will deal pretty well with POP3
functionality by not strictly following the RFC and instead allowing
things like leaving the messages on the server-side store and so on.
5. What are other MTAs available out there ?
For just POP3? Many. Too many to mention. It's usually needs based to
figure out which one is best for you. Some of it is preference as well.
Even Windows Server 2003 includes a pop and smtp server these days and is
intended for small shop impelementations.
Does that help?
Al
Thanks again
Steve
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:%23WpTdwvYFHA.612@TK2MSFTNGP12.phx.gbl...
Yikes. That's confusing.
Exchange is a MTA - Message Transfer Agent. SMTP is a message
transport protocol. Exchange uses SMTP to transport messages (by
default).
Exchange is a message store. It stores your messages in a database for
you the client using a MUA - message user agent (such as Outlook) to
come pick it up later.
POP3 is a protocol for picking up your mail from a message store
utilizing a MUA. Exchange supports POP3.
POP3 Connectors are for people that want to pick up mail from an ISP
mailbox and put it into Exchange. POP3 is still a message retrieval
protocol. It is not for sending. It never has been. SMTP is a
transport protocol which Exchange uses to transport messages to other
servers. When it does this transaction, it is the 'client' in the
client-server terminology used to describe SMTP transactions. Your MUA,
if configured to use POP3 as it's message retrieval protocol, will also
be configured to use a SMTP MTA (all that really means is that you send
your outgoing mail to a host that understands and listens for SMTP
commands on a well known port (usually)) if you hope to send mail to
anybody other than yourself. Not that talking to yourself is a bad
thing, it's just that if you go to the trouble to pick up your mail, it
would seem like a good idea to send something to others so you can
share wit and humor and pictures of the kids doing silly things with
water balloons or mud. I digress. In this situation, your MUA will
also be a client to a SMTP MTA.
Exchange natively speaks SMTP and will communicate as a POP3 host if so
configured. If you go that route, I suggest you utilize front end
servers so you can move mailboxes around without reconfiguring MUA's.
You can read more about Exchange at http://www.microsoft.com/exchange
-al
"SP" <none> wrote in message
news:%23jc3pqpYFHA.2756@tk2msftngp13.phx.gbl...
Hi
Of POP, SMTP, and whatever else, is Exchange one of those ? Or is
Exchange native to itself ? A class of its own - like POP and SMTP ?
I understand Exchange itself can't be POP since it uses POP connector
to connect to some POP server.
Steve
|
|
|
| Back to top |
|
|
SP
Guest
|
| Posted:
Mon May 30, 2005 10:54 pm Post subject:
Re: exchange basics |
|
|
Thank you very much. The information is very helpful.
Steve
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:%23PY4kQLZFHA.3908@TK2MSFTNGP15.phx.gbl...
| Quote: | Nope. That's the problem. If you find users switching between client
types, you often find trouble calls to go with it because the user will
often pull the mail to a different store (as in POP3) and then wonder why
it isn't there later. The other protocols do leave it in the central mail
store, so you're right, it wouldn't be a big deal.
-What are some serve-side rules that are essential to the day-to-day
messaging operation (the must-have rules)?
-If messages can be stored on server instead of downloading, how do
you deal with storage capacity ? Is it just a matter of setting quota on
individual accounts ? Does Exchange inform users if their accounts
approach limit ? In your experience, how quickly (on average) is the
limit of individual accounts run out ? What would be an optimal limit
for a quota ?
Unfortunately, there are no hard and fast rules here. Every organization
has their own concepts and ideas about storage. As an example, I've seen
some that believe they can do their job with 10MB limits while others
require 1GB limits. Others don't even need limits based on the way their
user population utilizes mail and storage.
Exchange can inform and enforce quotas on mail storage. You can set it
for whatever you want. I think the best approach is to figure out how
long you can be without mail, figure out how large the stores can become
and still be restored from a total melt-down type of disaster (restored to
service vs. played from tape) and work back to the quota limits from
there. Balance that with the way folks use email. I usually go by the
80-10-10 rule. 10% of the people will use the most space, 80% will use
some of it but stay within whatever limits you set, and 10% when asked
will respond "I have email?"
If you're users are used to sending mail now, you may be able to track the
mail on the system you have and get a feel for the way they do business
today. That might provide some insight into what you're in for.
Server side rules? That is so totally dependent and unique based on users
and organization that it's hard to tell. Many are using the rules today
in their client side activities, but that is only good when that client
and profile are in being used. If you switch to Exchange, they may be
using different protocols to access the server and may want a consistent
look and feel when they access the mail store. That would require some
server side rules so that when they use OWA, the rules are already
applied. When they use MAPI, IMAP, etc the same rules have already been
applied and they get consistency and therefore more productivity
(hopefully anyway, right?).
Does that help?
"SP" <none> wrote in message news:O1FUCPIZFHA.2128@TK2MSFTNGP15.phx.gbl...
Thank you very much...thank you.
"...keep in mind where the mail ends up. Best not to do that...": Why
not ? I'm thinking, the mail will end up in the inbox, right ? Where
else ? Or, is that not the best place for email to be?
POP3 limitations: no server rules, no calendar sharing, downloading of
messages
-What are some serve-side rules that are essential to the day-to-day
messaging operation (the must-have rules)?
-If messages can be stored on server instead of downloading, how do
you deal with storage capacity ? Is it just a matter of setting quota on
individual accounts ? Does Exchange inform users if their accounts
approach limit ? In your experience, how quickly (on average) is the
limit of individual accounts run out ? What would be an optimal limit
for a quota ?
Ultimately, we want to run our own Exchange server - migrating our users
from POP3-based to Exchange. I really appreciate your time and valuable
information here.
Steve
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:O$%230u$4YFHA.1412@TK2MSFTNGP12.phx.gbl...
In-line:
"SP" <anon@msn.com> wrote in message
news:uWbsTAxYFHA.3572@TK2MSFTNGP12.phx.gbl...
Thanks very much ... I really appreciate your reply on Exchange for
Dummies.
Questions:
1. POP3 host if so configured: Does that mean Exchange is not
configured as a POP3 host out-of-the-box ?
Can't recall at the moment. Bet you can find that information at
http://www.microsoft.com/exchange/library Even if it's not out of the
box, that's trivial to configure for users. See the help files for exact
steps.
2. If Exchange is not configured as a POP3 host, what does it use as a
message retrieval protocol ? Is it Exchange native ?
MAPI is the de-facto standard. Outlook uses MAPI to communicate with
Exchange stores. POP3 has the disadvantage of wanting to download the
messages from the central store to the client store. Makes recovery of
messages messy. It also is very basic in it's functionality and
although it has it's uses, has no server side rules, or other rich
features that some users want. Shared calendaring for example. MAPI
allows for those features.
3. Of POP3 host and Exchange native host, can Exchange support both at
the same time ? Or just one or the other ?
Supports both and then some. Exchange is a great tool to deploy as an
upgrade from other systems because it can talk so many protocols at the
same time.
*In other words, on the MUAs side, say, we have 10 users running
Outlook 2003, and we have Exchange configured as POP3 host. Can 5 of
the users configure their Outlook to connect to POP3 server while the
other 5 users configure their Outlook to connect to Exchange server ?
I think you mean can 5 of the MUA's connect to the Exchange store via
POP3 (or IMAP right?) and 5 other MUA's connect via MAPI (Outlook
corporate mode). If that's what you meant, then yes. Even a step
further: the clients can switch back and forth between client protocols
keeping in mind where the mail ends up. Best not to do that, but they
can. Just for fun, they can also access via WebDav and/or HTTP. The
nice thing about that is you can use other client types such as Ximian's
(Novell now) Linux Outlook knock-off client (MUA). Gives a richer
feature set to the end user.
4. Is there any loss or gain of functionalities if Exchange is
configured as POP3 host ?
It's not the host to worry about. Think of it as a multi-protocol
message router. It'll answer for many protocols and provide the mail
the way the protocol requires it. It understands and speaks most of the
protocols out there (might be all of them, but I haven't checked to
verify all of them.) However, you are subject to the limitations of the
protocol itself. In the case of POP3, you are limited to it's abilities
such as downloading from the server else finding another way to deal
with the messages. Note that some MUA's will deal pretty well with POP3
functionality by not strictly following the RFC and instead allowing
things like leaving the messages on the server-side store and so on.
5. What are other MTAs available out there ?
For just POP3? Many. Too many to mention. It's usually needs based to
figure out which one is best for you. Some of it is preference as well.
Even Windows Server 2003 includes a pop and smtp server these days and
is intended for small shop impelementations.
Does that help?
Al
Thanks again
Steve
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:%23WpTdwvYFHA.612@TK2MSFTNGP12.phx.gbl...
Yikes. That's confusing.
Exchange is a MTA - Message Transfer Agent. SMTP is a message
transport protocol. Exchange uses SMTP to transport messages (by
default).
Exchange is a message store. It stores your messages in a database
for you the client using a MUA - message user agent (such as Outlook)
to come pick it up later.
POP3 is a protocol for picking up your mail from a message store
utilizing a MUA. Exchange supports POP3.
POP3 Connectors are for people that want to pick up mail from an ISP
mailbox and put it into Exchange. POP3 is still a message retrieval
protocol. It is not for sending. It never has been. SMTP is a
transport protocol which Exchange uses to transport messages to other
servers. When it does this transaction, it is the 'client' in the
client-server terminology used to describe SMTP transactions. Your
MUA, if configured to use POP3 as it's message retrieval protocol,
will also be configured to use a SMTP MTA (all that really means is
that you send your outgoing mail to a host that understands and
listens for SMTP commands on a well known port (usually)) if you hope
to send mail to anybody other than yourself. Not that talking to
yourself is a bad thing, it's just that if you go to the trouble to
pick up your mail, it would seem like a good idea to send something to
others so you can share wit and humor and pictures of the kids doing
silly things with water balloons or mud. I digress. In this
situation, your MUA will also be a client to a SMTP MTA.
Exchange natively speaks SMTP and will communicate as a POP3 host if
so configured. If you go that route, I suggest you utilize front end
servers so you can move mailboxes around without reconfiguring MUA's.
You can read more about Exchange at http://www.microsoft.com/exchange
-al
"SP" <none> wrote in message
news:%23jc3pqpYFHA.2756@tk2msftngp13.phx.gbl...
Hi
Of POP, SMTP, and whatever else, is Exchange one of those ? Or is
Exchange native to itself ? A class of its own - like POP and SMTP ?
I understand Exchange itself can't be POP since it uses POP connector
to connect to some POP server.
Steve
|
|
|
| Back to top |
|
|
Asher_N
Guest
|
| Posted:
Tue Jul 19, 2005 5:00 pm Post subject:
Re: exchange basics |
|
|
"SP" <none> wrote in news:O1FUCPIZFHA.2128@TK2MSFTNGP15.phx.gbl:
| Quote: | Thank you very much...thank you.
"...keep in mind where the mail ends up. Best not to do that...":
Why not ? I'm thinking, the mail will end up in the inbox, right ?
Where else ? Or, is that not the best place for email to be?
POP3 limitations: no server rules, no calendar sharing, downloading of
messages
-What are some serve-side rules that are essential to the
day-to-day
messaging operation (the must-have rules)?
|
The big one that comes to mind is the out of office notification. I also
use a number of filing rules, moving messages in folders based on
whatever criteria.
| Quote: | -If messages can be stored on server instead of downloading, how
do you
deal with storage capacity ? Is it just a matter of setting quota on
individual accounts ? Does Exchange inform users if their accounts
approach limit ? In your experience, how quickly (on average) is the
limit of individual accounts run out ? What would be an optimal limit
for a quota ?
|
That a corporate decision. Bear in mind that usng Exchange with MAPI
client (such as Outlook) enables a host of options. Group calendaring,
task assignments, etc. If you enable Outlook Web Access (OWA) your users
will be able to not only check for new mail, but fully access all their
mail from any browser, anywhere. Exchange also has retention on deleted
items. You can recover items that were deleted for as long as you decide
(30 days is default). I wouold not recomend using POP3 inside an
organization.
| Quote: |
Ultimately, we want to run our own Exchange server - migrating our
users from POP3-based to Exchange. I really appreciate your time and
valuable information here.
Steve
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:O$%230u$4YFHA.1412@TK2MSFTNGP12.phx.gbl...
In-line:
"SP" <anon@msn.com> wrote in message
news:uWbsTAxYFHA.3572@TK2MSFTNGP12.phx.gbl...
Thanks very much ... I really appreciate your reply on Exchange for
Dummies.
Questions:
1. POP3 host if so configured: Does that mean Exchange is not
configured as a POP3 host out-of-the-box ?
Can't recall at the moment. Bet you can find that information at
http://www.microsoft.com/exchange/library Even if it's not out of the
box, that's trivial to configure for users. See the help files for
exact steps.
2. If Exchange is not configured as a POP3 host, what does it use as
a message retrieval protocol ? Is it Exchange native ?
MAPI is the de-facto standard. Outlook uses MAPI to communicate with
Exchange stores. POP3 has the disadvantage of wanting to download the
messages from the central store to the client store. Makes recovery
of messages messy. It also is very basic in it's functionality and
although it has it's uses, has no server side rules, or other rich
features that some users want. Shared calendaring for example. MAPI
allows for those features.
3. Of POP3 host and Exchange native host, can Exchange support both
at the same time ? Or just one or the other ?
Supports both and then some. Exchange is a great tool to deploy as
an upgrade from other systems because it can talk so many protocols
at the same time.
*In other words, on the MUAs side, say, we have 10 users running
Outlook 2003, and we have Exchange configured as POP3 host. Can 5
of the users configure their Outlook to connect to POP3 server while
the other 5 users configure their Outlook to connect to Exchange
server ?
I think you mean can 5 of the MUA's connect to the Exchange store via
POP3 (or IMAP right?) and 5 other MUA's connect via MAPI (Outlook
corporate mode). If that's what you meant, then yes. Even a step
further: the clients can switch back and forth between client
protocols keeping in mind where the mail ends up. Best not to do
that, but they can. Just for fun, they can also access via WebDav
and/or HTTP. The nice thing about that is you can use other client
types such as Ximian's (Novell now) Linux Outlook knock-off client
(MUA). Gives a richer feature set to the end user.
4. Is there any loss or gain of functionalities if Exchange is
configured as POP3 host ?
It's not the host to worry about. Think of it as a multi-protocol
message router. It'll answer for many protocols and provide the mail
the way the protocol requires it. It understands and speaks most of
the protocols out there (might be all of them, but I haven't checked
to verify all of them.) However, you are subject to the limitations
of the protocol itself. In the case of POP3, you are limited to it's
abilities such as downloading from the server else finding another
way to deal with the messages. Note that some MUA's will deal pretty
well with POP3 functionality by not strictly following the RFC and
instead allowing things like leaving the messages on the server-side
store and so on.
5. What are other MTAs available out there ?
For just POP3? Many. Too many to mention. It's usually needs based
to figure out which one is best for you. Some of it is preference as
well. Even Windows Server 2003 includes a pop and smtp server these
days and is intended for small shop impelementations.
Does that help?
Al
Thanks again
Steve
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:%23WpTdwvYFHA.612@TK2MSFTNGP12.phx.gbl...
Yikes. That's confusing.
Exchange is a MTA - Message Transfer Agent. SMTP is a message
transport protocol. Exchange uses SMTP to transport messages (by
default). Exchange is a message store. It stores your messages in
a database for you the client using a MUA - message user agent
(such as Outlook) to come pick it up later.
POP3 is a protocol for picking up your mail from a message store
utilizing a MUA. Exchange supports POP3.
POP3 Connectors are for people that want to pick up mail from an
ISP mailbox and put it into Exchange. POP3 is still a message
retrieval protocol. It is not for sending. It never has been.
SMTP is a transport protocol which Exchange uses to transport
messages to other servers. When it does this transaction, it is
the 'client' in the client-server terminology used to describe SMTP
transactions. Your MUA, if configured to use POP3 as it's message
retrieval protocol, will also be configured to use a SMTP MTA (all
that really means is that you send your outgoing mail to a host
that understands and listens for SMTP commands on a well known port
(usually)) if you hope to send mail to anybody other than yourself.
Not that talking to yourself is a bad thing, it's just that if you
go to the trouble to pick up your mail, it would seem like a good
idea to send something to others so you can share wit and humor and
pictures of the kids doing silly things with water balloons or mud.
I digress. In this situation, your MUA will also be a client to a
SMTP MTA.
Exchange natively speaks SMTP and will communicate as a POP3 host
if so configured. If you go that route, I suggest you utilize
front end servers so you can move mailboxes around without
reconfiguring MUA's.
You can read more about Exchange at
http://www.microsoft.com/exchange
-al
"SP" <none> wrote in message
news:%23jc3pqpYFHA.2756@tk2msftngp13.phx.gbl...
Hi
Of POP, SMTP, and whatever else, is Exchange one of those ? Or is
Exchange native to itself ? A class of its own - like POP and
SMTP ?
I understand Exchange itself can't be POP since it uses POP
connector to connect to some POP server.
Steve
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in