Delivery Error For Internal Accounts Using Exchange

[Guest]

I have a user that cannot send inner office emails unless
the Accounts tab is opened and the Inner office email
account for the user is selected.
The default email address for this person is an external
email SMTP account. Using Office 2003 with Exchange 2000
also have it set up for Exchange Cached mode.

Example: the user receives an external email with the
SMTP account and needs to forward the message to several
employees on the Inner Office Account. All of the
employees that are getting the email are receiving it via
their Inner Office Exchange account but one of the
employees cannot receive the message unless the Accounts
button is selected and the Inner Office account is
selected to send the message.

Outlook 2002 did not seem to have this issue. How can I
set up the account so the user does not need to select
the account that is sending the message when it is for
Inner Office email only?

I can't set the Inner Office account as default because
sooner or later the user will send an External email not
thinking to switch the accounts and will not get a reply
because it is an Inner Office account.

thanks

 

[Lanwench [MVP - Exchange]]

I have a user that cannot send inner office emails unless
the Accounts tab is opened and the Inner office email
account for the user is selected.
The default email address for this person is an external
email SMTP account. Using Office 2003 with Exchange 2000
also have it set up for Exchange Cached mode.

Example: the user receives an external email with the
SMTP account and needs to forward the message to several
employees on the Inner Office Account. All of the
employees that are getting the email are receiving it via
their Inner Office Exchange account but one of the
employees cannot receive the message unless the Accounts
button is selected and the Inner Office account is
selected to send the message.

Outlook 2002 did not seem to have this issue. How can I
set up the account so the user does not need to select
the account that is sending the message when it is for
Inner Office email only?

I can't set the Inner Office account as default because
sooner or later the user will send an External email not
thinking to switch the accounts and will not get a reply
because it is an Inner Office account.

OT, but why not get rid of the Outlook Internet mail - third party POP for
your domain - and host everything on your Exchange server directly? That way
there's no distinction between Internet mail and interoffice mail - there's
just mail, period, and the Exchange server handles it all. This doesn't
address your specific question, I know, but it's the recommended setup - and
it's much easier to administer....if you're interested, post back and I'll
explain how to set it up.

 

[Guest]

-----Original Message-----



OT, but why not get rid of the Outlook Internet mail - third party POP for
your domain - and host everything on your Exchange server directly? That way
there's no distinction between Internet mail and interoffice mail - there's
just mail, period, and the Exchange server handles it all. This doesn't
address your specific question, I know, but it's the recommended setup - and
it's much easier to administer....if you're interested, post back and I'll
explain how to set it up.

anything that makes my job easier.
thanks again

 

[Lanwench [MVP - Exchange]]

anything that makes my job easier.
thanks again

Great - you'll like the new setup a lot better, I think. See
http://www.msexchange.org/tutorials/MF002.html for instructions on how to
get Exchange to receive Internet mail sent via SMTP. It's a very well
written article by an Exchange MVP.

You can do this even with dialup/ISDN (get an ISP who supports ETRN) .

If you have broadband but with a dynamic IP (such as a cable modem/ADSL
account):

You can use a dynamic DNS host such as www.dyndns.org - you set up an
account, such as yourcompany.dnsalias.com, and whomever hosts your public
DNS should set your primary MX record to point to yourcompany.dnsalias.com.
Open up port 25 inbound in your firewall or router, direct all traffic to
your internal IP for the Exchange server.
You run a service on your server (software such as DirectUpdate is
available for download from the dyndns website) and set it up to update
dyndns with your current dynamic IP.

Another thing you might want to look into is having someone else act as
backup - set up a secondary MX in your domain's public DNS that points to
their mail server for "store & forward" - meaning that when your server is
unavailable, they'll queue up mail and automatically retry delivery for X
days. If your ISP won't do this for you, Dyndns.org will (MailHop backup?)
for something like $30/yr USD....while it's true that most (sender's) SMTP
servers will retry delivery for several days themselves, it's better to have
another level of protection.

 

[Guest]

-----Original Message-----
(e-mail address removed) wrote:


Great - you'll like the new setup a lot better, I think. See
http://www.msexchange.org/tutorials/MF002.html for instructions on how to
get Exchange to receive Internet mail sent via SMTP. It's a very well
written article by an Exchange MVP.

You can do this even with dialup/ISDN (get an ISP who supports ETRN) .

If you have broadband but with a dynamic IP (such as a cable modem/ADSL
account):

You can use a dynamic DNS host such as www.dyndns.org - you set up an
account, such as yourcompany.dnsalias.com, and whomever hosts your public
DNS should set your primary MX record to point to yourcompany.dnsalias.com.
Open up port 25 inbound in your firewall or router, direct all traffic to
your internal IP for the Exchange server.
You run a service on your server (software such as DirectUpdate is
available for download from the dyndns website) and set it up to update
dyndns with your current dynamic IP.

Another thing you might want to look into is having someone else act as
backup - set up a secondary MX in your domain's public DNS that points to
their mail server for "store & forward" - meaning that when your server is
unavailable, they'll queue up mail and automatically retry delivery for X
days. If your ISP won't do this for you, Dyndns.org will (MailHop backup?)
for something like $30/yr USD....while it's true that most (sender's) SMTP
servers will retry delivery for several days themselves, it's better to have
another level of protection.


.Looking at it now thanks for the information.