Cant Internally Forward an Attachment from External E-mail in Outl

[Outlook Help!]

Hi,

I just upgraded all our workstations to Office Pro 2003 SP1. Things went
pretty well except I found a big problem.

We can't forward internally any message having an attachment received from
our ISP. If we receive a message without an attachment, we can forward it
with no problems.

We can receive the external message/attachment with no problem. If we
create a new message and attach the same file & send it, it works fine.

The message from the ISP basically says it can't find the recipient. It's
using our internal addr. Any thoughts on why it even goes thru them? I
checked and our Exchange server is set as our default E-mail.

Please Help!

Thanks in Advance
!
Workstation OS:
Mainly XP Pro - SP2
Some XP - Home - SP2
A few W2K - SP4
Server 2000 - SP4
Exchange 5.5

 

[Outlook Help!]

Hi,

I just upgraded all our workstations to Office Pro 2003 SP1. Things went
pretty well except I found a big problem.

We can't forward internally any message having an attachment received from
our ISP. If we receive a message without an attachment, we can forward it
with no problems.

We can receive the external message/attachment with no problem. If we
create a new message and attach the same file & send it, it works fine.

The message from the ISP basically says it can't find the recipient. It's
using our internal addr. Any thoughts on why it even goes thru them? I
checked and our Exchange server is set as our default E-mail.

Please Help!

Thanks in Advance
!
Workstation OS:
Mainly XP Pro - SP2
Some XP - Home - SP2
A few W2K - SP4
Server 2000 - SP4
Exchange 5.5

Just a note, there is not a problem with the Windows 2000 PC. It works fine
as before. So it's only the Win XP machines.

 

[Outlook Help!]

Just a note, there is not a problem with the Windows 2000 PC. It works fine
as before. So it's only the Win XP machines.

I found that I can "Get Around" the issue if when I am in the Forward mode,
I select Accounts from the menu bar then select my Exchange Server instead of
my POP3 ISP. Everything then is deliver as it should be.

Does anyone know of a way to get around having to do this?

I have people ready to come after me with tourches & pitchforks.

Thanks!

 

[K. Orland]

The XP machines are SP1 or SP2? If SP2, did you turn the firewall off?
--
Kathleen Orland

http://www.howto-outlook.com/

 

[Outlook Help!]

The XP machines are SP1 or SP2? If SP2, did you turn the firewall off?

I didn't change anything with the firewall. It is currently on. WXP SP2
has been installed for awhile now and everything was working fine until
Office2003

Should the firewall be turned off?

 

[Brian Tillman]

I found that I can "Get Around" the issue if when I am in the Forward
mode, I select Accounts from the menu bar then select my Exchange
Server instead of my POP3 ISP. Everything then is deliver as it
should be.

Outlook always tries to use the account that received the original message
when you reply or forward. Personally, I'd have Exchange perform the
routing between the ISP and internal mail. Then everything will come
through the Exchange account. Barring that, have the Exchange server handle
all outbound messages and point the POP account's outgoing server settings
at Exchange.

 

[Outlook Help!]

Outlook always tries to use the account that received the original message
when you reply or forward. Personally, I'd have Exchange perform the
routing between the ISP and internal mail. Then everything will come
through the Exchange account. Barring that, have the Exchange server handle
all outbound messages and point the POP account's outgoing server settings
at Exchange.

Hi Brian, Thanks for the info!

I'm a little confused by your suggestion. Under E-mail accounts, I already
have the Exchange server and also my POP3 account. Do I need to change
something there?

In this situation, isn't Exchange already handeling the routing between the
ISP & internal mail?

You also mentioned "have the Exchange server handle all outbound messages
and point the POP account's outgoing server settings at Exchange". Where/How
do I configure it to do that?

This was working with no problems at all before the 2003 Office Upgrade.

Sorry about all the questions!

Thanks for you help!!!

 

[Brian Tillman]

I'm a little confused by your suggestion. Under E-mail accounts, I
already have the Exchange server and also my POP3 account. Do I need
to change something there?

Why are you using a POP account at all? Exchange has the ability to pull
mail from an ISP and place it in the appropriate mailbox.

In this situation, isn't Exchange already handeling the routing
between the ISP & internal mail?

No. You have a POP account that is receiving mail, or at least that's what
you said.

You also mentioned "have the Exchange server handle all outbound
messages and point the POP account's outgoing server settings at
Exchange". Where/How do I configure it to do that?

Tools>E-mail Accounts>Next. Select your POP account and choose Change.
Define the SMTP server there to be the Exchange server's SMTP address. If
you don't have Exchange set up to allow SMTP connections, ask in
m.p.exchange.admin for how.

This was working with no problems at all before the 2003 Office
Upgrade.

Upgrade from what?

 

[Outlook Help!]

Why are you using a POP account at all? Exchange has the ability to pull
mail from an ISP and place it in the appropriate mailbox.


No. You have a POP account that is receiving mail, or at least that's what
you said.


Tools>E-mail Accounts>Next. Select your POP account and choose Change.
Define the SMTP server there to be the Exchange server's SMTP address. If
you don't have Exchange set up to allow SMTP connections, ask in
m.p.exchange.admin for how.


Upgrade from what?

Upgrade from Office/Outlook 2000.

We've been on on WindowsXP Home/Pro SP2, Dell computers for several weeks
with no problems. They have all available Windows/Office patches installed.

This problem does not happen on one remaining Windows2000 SP4 workstation.
It's also running Office2003 like everyone else.

Sorry for not including this earlier!