RE: POP3 Connector for different domain to CEICW setup

Nathan,

I have now gone through the receipient policy amendments you suggest... no
joy. The system is still not delivering messages sent to either the domain1
or domain2 address, if the domain2 address is set as primary......... however
if the domain1 address is primary then no problem!

Just to re-iterate - the message tracking centre for the "stalled" e-mails
shows three entries:

SMTP: Message submitted to Advanced Queuing
SMTP: Started message submission to advanced queue
SMTP: Message submitted to categorizer

And that's it.....

What now?

Thanks for your time so far,


Michael

""Nathan Liu [MSFT]"" wrote:

> Hi Michael,
>
> Thank you for your quick update.
>
> Considering the current condition, let's configure a specific Recipient
> Policy only for the specific 3 Users, to do so:
>
> 1. Open the Exchange System Manager, go to Recipients -> Recipient
> Policies, right-click Recipient Policies, point to New -> Recipient Policy.
>
> 2. Choose E-Mail Addresses and click OK.
>
> 3. In the General page, input appropriate name in the Name box (i.e.
> Domain2), then click Modify button.
>
> 4. In the "Find Exchange Recipients" page, click Advanced tab, click Field
> and point to User -> Alias.
>
> 5. Input appropriate alias of 3 users, and click "Find Now" button, then
> click OK.
>
> 6. Click E-Mail Addresses (Policy) tab, click New -> SMTP Address, input
> @domain2.com entry in the Address box. Then check or uncheck the "This
> Exchange Organization is responsible for all mail delivery to this address"
> check box based on your current condition. Then click Apply and click OK.
>
> 7. In Exchange System Manager, expand Recipients -> Recipient Update
> Services, and then right-click any Service listed in the right pane to
> choose "Update Now".
>
> NOTE: The 3 user accounts who have been unchecked the option "Automatically
> update e-mail address based on recipient policy" will not receive the new
> added Recipient Policy. Since we have created above specific Recipient
> policy for the specific 3 users, let's check the "Automatically update
> e-mail address based on recipient policy" option.
>
> 8. Run services.msc to bring up the Services Management console, locate
> "Microsoft Exchange System Attendant" and then click Restart.
>
> NOTE: This step is recommended since recipient policy will be updated
> immediately after the SA service restart. Otherwise, it may take a while to
> implement the changes.
>
>
> To get additional detailed information, you may refer to the following KB
> article:
>
> XADM: How to create e-mail addresses based on group membership
> http://support.microsoft.com/?id=317298
>
> 822447 How to Modify an SMTP E-Mail Address by Using Recipient Policies
> http://support.microsoft.com/?id=822447
>
> I appreciate your time and cooperation. If anything is unclear, please feel
> free to let me know. I am looking forward to hearing from you.
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
> ======================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> --------------------
> >Thread-Topic: POP3 Connector for different domain to CEICW setup
> >thread-index: AcX75E3nudGZFE7nTrattAaQfQmSVQ==
> >X-WBNR-Posting-Host: 213.152.56.213
> >From: =?Utf-8?B?TWljaGFlbCBMb2ViZW5iZXJn?=
> <MichaelLoebenberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <D568600D-1FAF-4C70-99FB-68F96BE649B1@xxxxxxxxxxxxx>
> <qFSv0F7#FHA.3764@xxxxxxxxxxxxxxxxxxxxx>
> >Subject: RE: POP3 Connector for different domain to CEICW setup
> >Date: Thu, 8 Dec 2005 02:44:02 -0800
> >Lines: 228
> >Message-ID: <D3954B97-D9BA-41C8-915F-60E147943855@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:228684
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Nathan,
> >
> >Thanks for your reply
> >
> >1. I do not want to add the @domain2.com address to all 8 users, which is
> >why I had previously put the address manually onto the 3 users who use it.
> I
> >have not added the @domain2.com to the receipient policy....
> >
> >I do not understand how the connector can work fine, receiving messages
> for
> >both addresses for these three users, but only if @domain1.org.uk is the
> >primary address..... why does it make any difference to change the primary
> >e-mail address?
> >
> >2. I have e-mailed you the screenshot off-list - usenet client won't let
> me
> >post it!
> >
> >3. If either @domain1.org.uk or @domain2.com is set as the primary address
> >for the user, outgoing messages from them are fine.
> >
> >Haven't managed to do the rest of those things yet - perhaps later tonight
> -
> >but have you any comment thus far?
> >
> >
> >Thanks so much for your time,
> >
> >
> >
> >Michael
> >
> >
> >""Nathan Liu [MSFT]"" wrote:
> >
> >> Hello Michael,
> >>
> >> Thank you for posting in the SBS newsgroup.
> >>
> >> My sincerest apologies for the delay in responding due to high post
> volume,
> >> thanks for the understanding.
> >>
> >> Considering the current condition, please kindly answer and perform the
> >> following questions and steps:
> >>
> >> 1. As you mentioned, you have manually added the SMTP email address
> >> "username@xxxxxxxxxxx" into 3 of these users, did you add this entry
> into
> >> Default Recipient Policy of Exchange Server?
> >>
> >> A. To do so, please open the Exchange System Manager, expand Recipients
> ->
> >> Recipient Policies, right-click Default Policy and select Properties,
> click
> >> E-Mail Addresses (Policy) tab, click New, select SMTP Address, input
> >> @domain2.com entry in the Address box. Then check or uncheck the "This
> >> Exchange Organization is responsible for all mail delivery to this
> address"
> >> check box based on your current condition. Then click Apply and click OK.
> >>
> >> B. In Exchange System Manager, expand Recipients -> Recipient Update
> >> Services, and then right-click any Service listed in the right pane to
> >> choose "Update Now".
> >>
> >> NOTE: The user account who has been unchecked the option "Automatically
> >> update e-mail address based on recipient policy" will not receive the
> new
> >> added Recipient Policy. You should add the e-mail address for those
> users
> >> manually.
> >>
> >> C. Run services.msc to bring up the Services Management console, locate
> >> "Microsoft Exchange System Attendant" and then click Restart.
> >>
> >> NOTE: This step is recommended since recipient policy will be updated
> >> immediately after the SA service restart. Otherwise, it may take a while
> to
> >> implement the changes.
> >>
> >> 2. Please make a screen shot of the Message Tracking, and then attach
> it
> >> in your reply.
> >>
> >> 3. Does this issue occur when you try to send outgoing email by using
> >> username@xxxxxxxxxxx email address?
> >>
> >> 4. Enable Diagnostic Logging to determine the root of the transport
> >> issue. To enable Diagnostic Logging on the MSExchangeTransport service:
> >>
> >> 1). Start Exchange System Manager.
> >>
> >> 2). Navigate to the server object.
> >>
> >> 3). Right-click <Server object>, and then click Properties.
> >>
> >> 4). Click the Diagnostic Logging tab.
> >>
> >> 5). Under Categories, click MSExchangeTransport.
> >>
> >> 6). Under Logging Level, choose maximum for all the items. Restart the
> >> server.
> >>
> >> 7). Let a user send an outbound message and copy all Exchange relative
> >> events in Event Viewer.
> >>
> >> For more information regarding how to troubleshoot Exchange problems,
> >> please refer to the following article:
> >>
> >> General troubleshooting for transport issues in Exchange 2000 Server and
> in
> >> Exchange Server 2003
> >> http://support.microsoft.com/?id=257265
> >>
> >> 5. Enable SMTP logging and gather SMTP log to troubleshoot the issue:
> >>
> >> A. Open Exchange System Manager, expand Servers -> <Server name> ->
> >> Protocols -> SMTP, right-click "Default SMTP Virtual Server" and click
> >> Properties.
> >>
> >> B. Under the General tab, check the option "Enable Logging".
> >>
> >> C. With "W3C Extended Log File Format", click "Properties".
> >>
> >> D. Under "General Properties", make sure "Use local time for file naming
> >> and rollover" is CHECKED.
> >>
> >> E. Switch to the "Extended Properties", and then select to enable All
> the
> >> logging Options.
> >>
> >> F. Click OK to apply the modification.
> >>
> >> G. Right-click Default SMTP Virtual Server and click Stop.
> >>
> >> H. Right-click Default SMTP Virtual Server and click Start to restart
> the
> >> SMTP server.
> >>
> >> I. Reproduce the issue, repeat step G to stop Default SMTP Virtual
> Server,
> >> copy out or zip the SMTP log files in the
> >> "%systemroot%\system32\logfiles\SmtpSvc1" folder, and then restart the
> >> "Default SMTP Virtual Server".
> >>
> >> To get additional detailed information, you may refer to the following
> KB
> >> article:
> >>
> >> 885685 How to troubleshoot the POP3 Connector in Windows Small Business
> >> Server 2003
> >> http://support.microsoft.com/?id=885685
> >>
> >> I appreciate your time and cooperation. If anything is unclear, please
> feel
> >> free to let me know. I am looking forward to hearing from you.
> >>
> >> Best regards,
> >>
> >> Nathan Liu (MSFT)
> >> Microsoft CSS Online Newsgroup Support
> >>
> >> Get Secure! - www.microsoft.com/security
> >> ======================================================
> >> This newsgroup only focuses on SBS technical issues. If you have issues
> >> regarding other Microsoft products, you'd better post in the
> corresponding
> >> newsgroups so that they can be resolved in an efficient and timely
> manner.
> >> You can locate the newsgroup here:
> >> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
> >>
> >> When opening a new thread via the web interface, we recommend you check
> the
> >> "Notify me of replies" box to receive e-mail notifications when there
> are
> >> any updates in your thread. When responding to posts via your
> newsreader,
> >> please "Reply to Group" so that others may learn and benefit from your
> >> issue.
> >>
> >> Microsoft engineers can only focus on one issue per thread. Although we
> >> provide other information for your reference, we recommend you post
> >> different incidents in different threads to keep the thread clean. In
.