Re: Exchange 2003 - Problem: Internal forwarding of external e-mail

On Dec 4, 11:52 am, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
matts68n...@xxxxxxxxxxxx wrote:
The factors are: Exchange 2003 Standard in SBS 2003 R2 / Domain is
@XXX.local / Used for internal e-mail for 25 users / POP3 is setup on
5 clients to connect to ISP for external e-mail / An SMTP address for
the external e-mail has been setup in AD with it being set as
primary. / On the client, Exchange is set as primary / Exchange is set
use DNS

All of this seems to work fine. The issue comes when an external e-
mail is received by the internal client (with or without attachments)
and then is 'forwarded' to an internal recipient. When doing so the
forwarded e-mail is actually sent out through the POP3 connection
rather than through the Exchange server. I then of course get an NDR
specifying that it was caught as spam and expectedly shows the sending
e-mail address of @XXX.local.

Can anyone point out a fix for this. This is an office that relies
heavily on this function. When the information is cut and pasted into
a new e-mail for the internal recipient the e-mail goes fine. However,
some of these forwarded e-mails include several attachments and
cutting and pasting is not a viable option.

This may not be what you want to hear, but stop using POP3 - register an
Internet domain if you don't have one already, host the email directly on
the Exchange server via SMTP, use only Exchange in the Outlook profiles, and
watch this and most of your other mail problems go away.- Hide quoted text -

- Show quoted text -

Thank you for the information and I agree that this would be the
easiest as well as the best way to get rid of the problems. However,
it is also not a viable option in this case due to the can of worms
that could be opened up when opening the server to the outside without
purchasing additional filtering/protection software/hardware for the
server. In addition of not having an IT guy on hand at their office
during the day for major issues.

Can you possible give me an idea on why this is happening. I
understand that it is most likely due to the information within the e-
mail header that points to the ISP. However, there should be a way to
correct this. Any ideas?
.

Relevant Pages

  • RE: Outlook trying to connect.......
    ... does outlook client connect to exchange server ...
    (microsoft.public.windows.server.sbs)
  • RE: Outlook not Sending External Mail
    ... Please follow the wizard to install the updates for all Exchange components. ... Delivery status notifications in Exchange Server and in Small Business Server ... This posting is provided "AS IS" with no warranties, ... >This client originally used POP3 Mail from our public Web URL, ...
    (microsoft.public.windows.server.sbs)
  • Re: Excessive Event ID 9646 in Exchange 2003
    ... I'd suspect an application in the client environment. ... On the Exchange 2003 computer, click Start, click Run, type regedit ... If you use Outlook 2007 to connect your Exchange server, ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.exchange.admin)
  • Re: RPC on Single Exchange Server, not a GC server
    ... client is becoming confused somehow, but I don't have any suggestions. ... with the proxy settings configured to the FQDN of our Exchange ... connection that will work at that point is straight IP. ... The netbios name of the exchange server is resolved properly, ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 - Problem: Internal forwarding of external e-mail
    ... the external e-mail has been setup in AD with it being set as ... Exchange is set as primary / Exchange is set ... mail is received by the internal client ... a new e-mail for the internal recipient the e-mail goes fine. ...
    (microsoft.public.exchange.admin)