Re: exch 2003 will not pass email to external IPS mail server



Some ideas for you in line below:

Here is the story:

The goal is to have all users check their email from home or a place
they may visit.

13 internal member users,
-who use OL at the desktop, connect to your exchange server, good.

1 user that never comes to the office,
-OWA or Outlook Anywhere.

1 technical (can easily set up an outlook account)
-From Where? Home? Traveling NB?

1 can surf the web from anywhere (takes laptop with him at times),
-OWA or Outlook Anywhere

1 laptop user has troubles connecting to free wireless,
-don't know how to help him connect to unknown free wireless. EBKC?

all users want to view mail from home
-RWW to their own desktops in the office, OWA or Outlook Anywhere

2 users want to connect up from computer at secondary job (probably
behind a firewall).
-RWW to desktop, or OWA, depending on rules in force at second job. Also hard to help them.

The mail access from remote locations is primarily "FYI reading
process" to keep caught up with email; 90% of the work is done while
connected to exchange. But some of the time a used has to come back to
work to because his email cannot be accessed from the computer he is
using.

-Need to know more. There is no blanket reason why mail should not be available from any computer that can access the internet by RWW or -OWA, or even Outlook Anywhere.

-OWA or Outlook Anywhere is being connected to Exchange. In fact, OWA is the only supplied way to connect to Exchange in SBS 2008, or -indeed any installation of Exchange 2007.

OWA has worked fine in house but has not been investigated for off-
site use.
-Go for it. Also look at your RWW landing page for how to setup Outlook Anywhere. And for those that have in house desktops, or are willing to share them, use RWW to Connect to My Computer at Work

Distribution list are primarily local on the individual outlook
machines. A future goal is to have global distribution list (2-3 lists
with max of 25 contacts in each) so an admin can keep the one current
instead of 13 users keeping their own list current.

-Don't have the slightest idea what you mean here. If the users are using exchange mail, then the distribution lists should be in the GAL, not in their personal mailbox.

Have not used TS before.
-Probably no need for TS, with most users having their own desktops to connect to via RWW when they are out of the office.


On Dec 4, 4:38 pm, "Larry Struckmeyer [SBS-MVP]" <lstruckme...@mis-
wizards.com> wrote:
Cliff is right, if you want web mail. There are lots of other options.
Assuming that the users who are to get the mail are members of your
organization, you could use Outlook Anywhere, or a Terminal Server with each
having their own Outlook on the TS, or (ugh, last choice) the external users
could pop from your server.

It would really help if we knew the goal here.

Internal User John, who also wants to view the mail from home?

Internal User John, and external User Bill, who is part of your company but
never comes into the office.

Internal User John, and external User Fred, who is a contract worker,
supplier, etc who is not part of the organization and should receive
selected mail?

Distribution List? Mail Enabled Contact?

Help us help.

-Larry

"Cliff Galiher" <cgali...@xxxxxxxxx> wrote in message

news:Jr2dnSNP5_gey6XUnZ2dnUVZ_tninZ2d@xxxxxxxxxxxxxx



> There is no *reliable* way to force this across the organization. You > can
> *ask* users to configure an outlook rule to do this, but that is all you
> can do.

> With that said, you realistically are trying to tackle the problem the
> wrong way. If you want webmail, why not use OWA?

> -Cliff

> "TxLonghornRedRaider" <ppandm...@xxxxxxxxx> wrote in message
>news:a21b93a8-dd3c-4e29-b360-ee8f72d3a555@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> All, I know this issues has been addressed in the past but for the
>> life of me (and my poor eyes from reading/doing, reading/doing) I
>> cannot implement the solution.

>> This seem real simple: Use SBS 2003 exchange and have sent messages
>> appear at the internal client's Outlook 2003 and also have the same
>> message sent to the external ISP pop mail server. Presently exchange
>> mail does not get forwarded to the ISP mail server. Thus all internal
>> exchange mail is not seen by the off -ite user logging into the
>> webmail.

>> How can Exchange be set (or any other app/hardware/firewalls settings)
>> to allow internal exchange mail to also show up on the ISP POP mail
>> server?

>> As you might see from the write up most of this is new to me, but
>> after 2 weeks of reading, changing, changing, reading, changing,
>> changing, etc. I have learned a lot about relays, policies, f&reverse
>> lookup and I am ready to learn more with some additional help.

>> -------------------------------
>> Details:
>> ISP is hosting web and mail
>> Exch has the latest updates. Exchange system ver: 6.5.7638.1
>> Exch BPA shows 2 warnings: 1) Certificate principal mismatch 2) Smart
>> host is set.
>> Not using pop3 connector since testing showed downloading removes all
>> mail from the ISP mail server.
>> Emails work fine to us...@xxxxxxxxx or us...@xxxxxxxxxxxx not set up
>> in exchange
>> Emails thru Outlook pop account works fine. Outlook client has both
>> exchange account and pop account.
>> CEICW: email held at isp..... signal to: Send signal to:
>> mail.theispserver.net
>> CEICW: smarthost set to ISP mailserver mail.theispserver.net also
>> tried DNS
>> CEICW: domain set to mydomain.org
>> SMTP VS properties: unresolved recipients to: mail.theispserver.net
>> AD User setup: email: (same as ISP) us...@xxxxxxxxxxxx, logon name:
>> us...@xxxxxxxxxxxxxx
>> Recipient Default Policy properties: defaults.... SMTP @mydomain.org
>> is primary with Exch Org resp for mail delivery
>> other rule is smtp @mydomain.local with Exch Org resp for mail
>> delivery

>> IPConfig/all and iireset /status
>> C:\Documents and Settings\Administrator>ipconfig/all

>> Windows IP Configuration

>> Host Name . . . . . . . . . . . . : server1
>> Primary Dns Suffix . . . . . . . : mydomain.local
>> Node Type . . . . . . . . . . . . : Unknown
>> IP Routing Enabled. . . . . . . . : Yes
>> WINS Proxy Enabled. . . . . . . . : Yes
>> DNS Suffix Search List. . . . . . : mydomain.local

>> Ethernet adapter Server Local Area Connection:

>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>> Ethernet #2
>> Physical Address. . . . . . . . . : 00-1D-09-FF-8A-40
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 10.0.0.100
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 10.0.0.1
>> DNS Servers . . . . . . . . . . . : 10.0.0.100
>> Primary WINS Server . . . . . . . : 10.0.0.100

>> C:\Documents and Settings\Administrator>iisreset /status

>> Status for World Wide Web Publishing Service ( W3SVC ) : Running
>> Status for Simple Mail Transfer Protocol (SMTP) ( SMTPSVC ) : Running
>> Status for Microsoft Exchange Routing Engine ( RESvc ) : Running
>> Status for Microsoft Exchange POP3 ( POP3Svc ) : Stopped
>> Status for Network News Transfer Protocol (NNTP) ( NntpSvc ) : Stopped
>> Status for Microsoft Exchange IMAP4 ( IMAP4Svc ) : Running
>> Status for HTTP SSL ( HTTPFilter ) : Running

>> ------------------------------------------------

>> I thought a solution was here (link below from 2004) but implementing
>> item2 solution did not fix either.

>>http://groups.google.com/group/microsoft.public.windows.server.sbs/br...
>> Item 2 describes what's happening.
>> 1) When you try to send an email from your domain to one of those
>> addresses
>> you get back an NDR from the SBS saying that the mailbox doesn't
>> exist.
>> 2) When you try to send an email from your domain to one of those
>> addresses
>> the email ends on the Exchange mailbox instead of your ISP.- Hide >> quoted text -

- Show quoted text -

.



Relevant Pages

  • Re: Critical e-mail problem.
    ... I upgraded from Win2K Server to WinSBS2003 on my desktop ... of my POP3 e-mail accounts as an Exchange Server account. ... I found that I was only receiving mail from the Exchange ... your Outlook profile will have Exchange as its default (and this ...
    (microsoft.public.windows.server.sbs)
  • Re: Critical e-mail problem.
    ... I upgraded from Win2K Server to WinSBS2003 on my desktop ... of my POP3 e-mail accounts as an Exchange Server account. ... I found that I was only receiving mail from the Exchange ... your Outlook profile will have Exchange as its default (and this ...
    (microsoft.public.windows.server.sbs)
  • Re: Faxe per Email über Outlook-2003
    ... Der Exchange Server ist ein Groupware- und Messaging-System der Firma ... Microsoft Exchange Server benutzt ein proprietäres RPC Protokoll namens ... Microsoft Office Outlook Web Access ...
    (microsoft.public.de.outlook)
  • Re: Outlook2003 POP3-IMAP Exchange | Confused!?
    ... exchange and sharepoint not being used. ... Folder Re-Direction and roaming profiles. ... with Outlook 2003 as the preferred choice of email client. ... registry to point to the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: exch 2003 will not pass email to external IPS mail server
    ... connected to exchange. ... Distribution list are primarily local on the individual outlook ... Internal User John, who also wants to view the mail from home? ... mail does not get forwarded to the ISP mail server. ...
    (microsoft.public.windows.server.sbs)