Prev: ABA 2008 POP3 Problem
Next: ICW Fails on Firewall Stage
From: Rick Solomon Rick on 8 Feb 2009 06:58
I've just migrated from Small Business Server 2003 to SBS 2008. Things were
going fine until I set up a POP3 connector. It just won't work. I get an
error in the event log with an Event ID 203. Message Text:

An error occurred while delivering mail to 'Rick(a)libertywrites.com' on the
SMTP server 'localhost'. The error code was 0x800ccc69. Verify that the
mailbox exists and that the Exchange receive connectors are configured
properly.

The mailbox does exist, and an online search on any of the keyword/numbers
gets no hits. I've checked the POP3 parameters, and they're all correct.

Where do I look next?

From: "Robbin Meng [MSFT]" on 9 Feb 2009 02:55


Hi Rick,

Thanks for your post.

Before we go further, is your Exchange server 2007 can send/receive
external emails normally now besides the POP3 connector issue?

If sending and receiving external emails works fine and only POP3 Connector
failed, usually the SMTP Relay if not correctly configured on SBS 2008
server. First, please follow the below article to check you SMTP relay and
Receive Connector settings:

How to Configure Trusted SMTP Relay in Exchange on SBS 2008
http://blogs.technet.com/sbs/archive/2008/09/18/how-to-configure-trusted-smt
p-relay-in-exchange-on-sbs-2008.aspx

Note, make sure the "Windows SBS POP3 Connector" service is running
Automatic and Started.

Also, if you are using certain 3rd party anti-virus/anti-spam software on
the SBS server, this issue may occur if the firewall settings are not
configured correctly on your computer. Please double check if it is
blocking POP3 connector or temporarily turn them off to narrow down this
issue.

By the way, type at least one e-mail address in the To box, in addition to
the other recipients' e-mail addresses in the Bcc box when forwarding POP3
mails to user's Exchange mailbox.

If the issue persists, please enable Verbose logging in the Windows SBS
2008 POP3 Connector paste the detailed log here.

How to enable Verbose logging in the Windows SBS 2008 POP3 Connector
http://support.microsoft.com/kb/958798

More related information:

Understanding the POP3 Connector
http://technet.microsoft.com/en-us/library/cc546479.aspx

Managing the POP3 Connector
http://technet.microsoft.com/en-us/library/cc546066.aspx


Hope this helps. Also, if you have any questions or concerns, please do not
hesitate to let me know.


Best regards,
Robbin Meng(MSFT)

Microsoft CSS Online Newsgroup Support

From: wirelessnut on 9 Feb 2009 11:33

I was getting Exactly the same result here with POP3 Connector on SBS
2008 Premium.

YES this post is long but it does contain a solution right up top here,
the rest of the information may be helpful.

It was an internal SMTP issue. The POP3 connector actually was working,
but did nothing with the mail since it couldn't deliver it to my
internal Exchange Recipient.

*** SOLUTION this issue in my case at least:
In my scenario, creating an Authoritative Accepted Domain in Exchange
Management Console > Organization Configuration > Hub Transport allowed
SMTP to deliver the mail.
*** SOLUTION Above. Details below if you care to read more.

YES- POP3 Connector in SBS 2008 actually works in case anyone needs
that validated. (I was beginning to wonder).

YET- I have another issue with populating the POP3 Connector drop down
mailbox assignment list that I need help with. To keep it simle I'll
post that in another reply.

YES email names were already in the users Email Address lists.
NO there was no mail in the badmail folder.
NO Anti-virus wasn't the problem. I'm using the canned Live One Care
trial version that came with SBS 2008.
Verbose logging is on automatically when you execute Retrieve Now.
There is no need to turn it on.
I get only the same information in the Event Viewer that Rick Solomon
got.
See the log posted below. It's located in:
C:\Program Files\Windows Small Business
Server\Logs\pop3connector\pop3connector.log

******
YES - my configuration was not "standard", but was "supported" as
described below.

I don't know Rick Solomon's configuration, but mine may have been
slightly more complex than an out of the box configuration.

At this point I've followed Microsoft's white paper on Exchange
Segregation found here:
http://technet.microsoft.com/en-us/exchange/bb936719.aspx

We have legitimate need to separate GAL's and have followed the
"recommended" approach listed in that article.

I wonded if Rick Solomon did the same thing, and if that's what broke
his POP3 Connector?
******

One other change to note, I changed my outbound SMTP port to 587. This
has no effect since the inside SMTP port remains port 25.

Before I fixed my issue by adding the appropriate Authoritative
Accepted Domain, If I used one of those original users that appear in
the POP3 Connector drop down list, I ccould log on to OWA and send
messages inside and outside the domain, and I could recieve email from
inside the domain (but not outside since that uses the POP3 connector).
So Exchange transport was apparently working properly to send and
recieve email. But the POP3 Connector appeared to not be working.

It was truly an SMTP issue due to lack of an Authoritative Accepted
Domain entry.

The event log before the fix shows that an SMTP error occurred.

Here is a log excerpt (personally identifyable info masked):

=======================================================
Log opening: 03:30:09 : 02/09/09

-- Pop3Connector --
Options: 0x6031
Beginning "Retrieve Now"...
(AsyncConn[ pop.comcast.net:110 ]) Connecting to 'pop.comcast.net' on
port 110.
(AsyncConn[ pop.comcast.net:110 ]) GetHostByName result: srv_name =
"pop.comcast.net" srv_addr = 76.96.30.119:110
(POP3) [RX] +OK POP3 ready
(POP3) [TX] USER kxxx(a)comcast.net
(POP3) [RX] +OK
(POP3) [TX] PASS ************************
(POP3) [RX] +OK server ready
(POP3) [TX] STAT
(POP3) [RX] +OK 1 1558
Check for new messages: 1 (1.52 KB) total.
(AsyncConn[ localhost:25 ]) Connecting to 'localhost' on port 25.
(AsyncConn[ localhost:25 ]) GetHostByName result: srv_name =
"localhost" srv_addr = [::1]:25
(AsyncConn[ localhost:25 ]) err: WSAGETSELECTEVENT = 0x10,
WSAGETSELECTERROR = 10061
(AsyncConn[ localhost:25 ]) Connection to 'localhost' closed.
(SMTP) [RX] 220 MyServer.mydomain.local Microsoft ESMTP MAIL Service
ready at Mon, 9 Feb 2009 03:30:13 +0000
(SMTP) [TX] EHLO MyServer
(SMTP) [RX] 250-MyServer.mydomain.local Hello [127.0.0.1]
(SMTP) [RX] 250-SIZE 10485760
(SMTP) [RX] 250-PIPELINING
(SMTP) [RX] 250-DSN
(SMTP) [RX] 250-ENHANCEDSTATUSCODES
(SMTP) [RX] 250-AUTH LOGIN
(SMTP) [RX] 250-8BITMIME
(SMTP) [RX] 250-BINARYMIME
(SMTP) [RX] 250 CHUNKING
(POP3) [TX] LIST
(POP3) [RX] +OK 1 messages
(POP3) [RX] 1 1558
(POP3) [RX] .
Downloading message 1 of 1.
(POP3) [TX] RETR 1
(POP3) [RX] +OK message follows
Sending message 1 to the SMTP recipient
Kxxx(a)UhOh-NOT-accepteddomain.com...
(SMTP) [TX] MAIL FROM: <Kxxx(a)UhOh-NOT-accepteddomain.com> RET=FULL
(SMTP) [RX] 250 2.1.0 Sender OK
(SMTP) [TX] RCPT TO: <Kxxx(a)UhOh-NOT-accepteddomain.com>
NOTIFY=FAILURE
(SMTP) [RX] 550 5.7.1 Unable to relay
Failure hrResult (0x800ccc69) trying to deliver message id 1:
SMTPRESPONSE: * * * !Failed! * * *
* * * * * *
* * * 0x800ccc69 * * *
Command: [SMTP_RCPT]
Completed: Yes.
IxpResult:
---> ---> ---> hrResult: 0x800ccc69
pszResponse: 550 5.7.1 Unable to relay
uiServerError: 550
dwSocketError: 0
pwszProblem: <none>
EVENT: An error occurred while delivering mail to
'Kxxx(a)UhOh-NOT-accepteddomain.com' on the SMTP server 'localhost'. The
error code was 0x800ccc69. Verify that the mailbox exists and that the
Exchange receive connectors are configured properly.
(AsyncConn[ localhost:25 ]) Connection to 'localhost' closed.
(POP3) [TX] QUIT
19: (POP3) [RX] +OK sz0097.wc.mail.comcast.net closing connection
19: (AsyncConn[ pop.comcast.net:110 ]) Connection to 'pop.comcast.net'
closed.
19: "Retrieve Now" finished.
[t 1] 02/09/09, 03:30:24: Received STOP command.
24: Leaving _ServiceMain (0).


Log closing: 03:30:24 : 02/09/09
=======================================================


AFTER ADDING THE Authoritative ACCEPTED DOMAIN

Here's the log:

=======================================================
Log opening: 15:43 : 02/09/09

-- Pop3Connector --
Options: 0x6031

Beginning "Retrieve Now"...
(AsyncConn[ mail.comcast.net:110 ]) Connecting to 'mail.comcast.net'
on port 110.
(POP3) [RX] +OK POP3 ready
(POP3) [TX] USER kxxx(a)comcast.net
(POP3) [RX] +OK
(POP3) [TX] PASS ************************
(POP3) [RX] +OK server ready
(POP3) [TX] STAT
(POP3) [RX] +OK 1 1548
Check for new messages: 1 (1.51 KB) total.
(AsyncConn[ localhost:25 ]) Connecting to 'localhost' on port 25.
(AsyncConn[ localhost:25 ]) GetHostByName result: srv_name =
"localhost" srv_addr = [::1]:25
(AsyncConn[ localhost:25 ]) err: WSAGETSELECTEVENT = 0x10,
WSAGETSELECTERROR = 10061
(AsyncConn[ localhost:25 ]) Connection to 'localhost' closed.
(SMTP) [RX] 220 MyServer.mydomain.local Microsoft ESMTP MAIL Service
ready at Mon, 9 Feb 2009 15:57 +0000
(SMTP) [TX] EHLO MyServer
(SMTP) [RX] 250-MyServer.mydomain.local Hello [127.0.0.1]
(SMTP) [RX] 250-SIZE 10485760
(SMTP) [RX] 250-PIPELINING
(SMTP) [RX] 250-DSN
(SMTP) [RX] 250-ENHANCEDSTATUSCODES
(SMTP) [RX] 250-AUTH LOGIN
(SMTP) [RX] 250-8BITMIME
(SMTP) [RX] 250-BINARYMIME
(SMTP) [RX] 250 CHUNKING
(POP3) [TX] LIST
(POP3) [RX] +OK 1 messages
(POP3) [RX] 1 1548
(POP3) [RX] .
Downloading message 1 of 1.
(POP3) [TX] RETR 1
(POP3) [RX] +OK message follows
Sending message 1 to the SMTP recipient kxxx(a)myaccepteddomain.com...
(SMTP) [TX] MAIL FROM: <kxxx(a)myaccepteddomain.com> RET=FULL
(SMTP) [RX] 250 2.1.0 Sender OK
(SMTP) [TX] RCPT TO: <kxxx(a)myaccepteddomain.com> NOTIFY=FAILURE
(SMTP) [RX] 250 2.1.5 Recipient OK
(SMTP) [TX] DATA
(SMTP) [RX] 354 Start mail input; end with <CRLF>.<CRLF>
(SMTP) [TX]
From: wirelessnut on 9 Feb 2009 11:55

The SBS 2008 POP3 Connector drop down list appears to only show exchange
enabled recipients that were created using the Windows SBS Console.

This seems to be the only place to assign POP3 Connect Mailboxes to
deliver to an Exchange user.

None of my other Exchange Mail Enabled users or groups appear in this
the drop down list in the Windows SBS Console POP3 Connector
properties.

Does anybody know a way to populate the POP3 Connector Mailbox list
except by using the Windows SBS Console to add new users?

Is there some group membership or attribute that I could add to
Exchange mail users that were created in other OU's with their own GAL
using Exhange Management Shell?

Is there no other way to populate this list of assignable Exchange
Mailbox users? (Registry, Attribute Editor, Group Membership?)

Is there a way to assign a POP3 Connector to an Exchange mail user or
group besides using the Windows SBS Console to add new users?

In my segregated Exchange environment - SBS 2008 POP3 Connector is
practically useless without some way of adding mailboxes to it's drop
down list that were not created using Windows SBS Console.

Why? Because I can't assign the POP3 Connection to any useful exchange
users! The standard SBS users are all but completely not used in my
scenario!

See http://technet.microsoft.com/en-us/exchange/bb936719.aspx

Does somebody have a work around besides using a 3rd part POP3
Connector?

Lastly - Gasp - getting desperate - Can anyone recommend their favorite
3rd Party POP3 Connector that will work with SBS 2008 / Exchange 2007?

Thanks.


--
wirelessnut
------------------------------------------------------------------------
wirelessnut's Profile: http://forums.techarena.in/members/wirelessnut.htm
View this thread: http://forums.techarena.in/small-business-server/1118709.htm

http://forums.techarena.in

From: wirelessnut on 9 Feb 2009 13:34

Moving right along here..

To add users or groups to the Windows SBS Console views and other
lists:

Please see post:

http://blogs.technet.com/sbs/archive/2008/09/22/why-are-some-of-my-users-not-displaying-in-the-sbs-console.aspx

*** Solution
"If you do not use the SBS provided ways to add new users they will not
show in the SBS Console > Users and Groups > Users tab, because the
user�s Active Directory (AD) attribute msSBSCreationState value is not
�stamped� to Created."
*** Solution

I tried both the Change User Role method (using Add permissions instead
of Replace permissions) and simply changing the msSBSCreationState
attribute on the user.

The Add User Role also changed group memberships and possibly other
attributes (i haven't compared yet)

Both ways populated the user lists and the POP3 Connector Drop down
list.

Both users can now recieve POP3 Connector email.

Finally, I can deliver email to useful Exchange Enabled email boxes
using POP3 Connector.


--
wirelessnut
------------------------------------------------------------------------
wirelessnut's Profile: http://forums.techarena.in/members/wirelessnut.htm
View this thread: http://forums.techarena.in/small-business-server/1118709.htm

http://forums.techarena.in

 | 
Pages: 1
Prev: ABA 2008 POP3 Problem
Next: ICW Fails on Firewall Stage