I am having a problem with Undeliverable POP3 email.

The emails are held by our ISP and downloaded every 15 mins. For all email
accounts that exist the email goes correctly to that account. I have setup
the Undeliverable POP 3 emails to go to a selected user account. This is not
happening. They are bouncing back with a NDR to the sender. I am running
SBS2003 with Exchange 2003.

I dont want these emails to bounce with a NDR. I want them to go to the
assigned account selected in the Undeliverable POP 3 Email section in POP3
Connector.

Any help?

Hi Adam,

Thanks for your posting.

The POP3 Connector supports both individual POP3 mailboxes and global POP3
mailboxes.

1. Individual POP3 Mailboxes - An individual mailbox is where e-mail for an
individual user account is stored in a single mailbox (e.g., a...@ms.com).
This mail is then delivered to a defined user on the Exchange server.

2. Global POP3 Mailboxes - A global mailbox is where e-mail for an entire
domain is stored in a single mailbox (e.g., all e-mail addressed to @ms.com
is stored in a single account). When this mail is delivered to the Exchange
server, the user name defined to the left of the @ symbol must match a
defined Exchange user.

Some ISP's have the ability to setup a global mailbox. This is a single
mailbox that will accept all e-mail for @ms.com regardless of the alias.

When you configure the connector you can tell it that the mailbox is a
global and choose the e-mail domain (ms.com) that it will download e-mail
for.

When the connector downloads the e-mail it will parse the headers for the
e-mail for addresses with @ms.com, if it finds a match it will do an LDAP
query into the AD to try to find an identical match to the address. If that
matches succeeds then it will deliver the e-mail to that user. If it fails,
then it will deliver the e-mail to the undeliverable POP3 mailbox.

The Undeliverable POP3 Mail option won't work in the individual user
mailbox scenario. In this case, the POP3 connector doesn't have to look for
a destination for the e-mail. It knows that any e-mail in this mailbox goes
to this mailbox, so unless that mailbox has been deleted it will bypass the
undeliverable check and attempt CDO delivery of the e-mail. If the e-mail
fails during the CDO delivery stage then the POP3 connector doesn't care.  

The undeliverable option only works if the POP3 connector can't find a
destination for the e-mail. If it finds a place to put the e-mail, it will
hand the e-mail off to CDO for delivery.

Hope this helps. If you have any questions please do not hesitate to let me
know.

Best regards,

Jerry Zhao (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Jerry

Yes I understand all of this. I am using Global POP3 Mailboxes and all
emails for the domain go to a single POP3 account with our ISP.

If the user account exists the emails are being delivered correctly and
there is no problem with that side of it. If there is a spelling error in
the email in the username then instead of directing the email to the mailbox
selected in the Undeliverable Mail section, it is just boucning with a NDR
to the sender. I dont want this to happen. Thats why I selected an account
for all undeliverable POP3 email to go to.

Any thoughts on why unknown username emails are bouncing and not going to
the Undeliverable Mail box which is selected in the POP3 Connector?

Regards

Adam

"Jerry zhao (MSFT)" <v-jer...@online.microsoft.com> wrote in message
news:aGaInAvSFHA.3336@TK2MSFTNGXA02.phx.gbl...

This might or might not help you. I am experimenting with a setup similar to
yours. Long before bringing SBS into the mix, our email host gave us the
option to have all email that was not directed to a recognized address to
another specific mailbox. For example, to "wrongaddr...@mycompany.com".
Alternatively, they could be directed to a bit bucket.
My personal email host, using a completely different system, also offers
those options--either forward to a specific mailbox, or to a bit bucket, so
there is a fair chance that your host might too.

For my personal domain, I use the bit bucket. Too bad for anything that is
misaddressed. For the business domain, we use the "wrong address" mailbox
and a couple of times a week someone scans scan it with mailwasher (a client
side shareware app that does POP3 to a server) to filter out the obvious
spam. About once every couple of weeks we do find a misaddressed but
legitimate (and often critical) email and rescue it from the garbage.

So far, if SBS does pan out, I do plan to keep the same scheme. In other
words, misaddressed mail never makes it to Exchange and we don't have to
worry about some of its less intuitive aspects. One less headache.

--C

news:eHMGOLvSFHA.140@TK2MSFTNGP10.phx.gbl...

a...@ms.com).

I know this can be done through the ISP if they have individual accounts and
can place all unkn...@mycompany.com into one mailbox.

I want exchange to do this. It is a built in feature of SBS2003 but for some
reason it is not working. I have seen other posts on the net from people
with similar problems but no one has given them the solution to fix this
problem. If you do it through exchange and you add 3 new users next week
then you dont make any setting changes with your ISP. All their emails go
into the one POP3 account with your ISP for all emails x...@mycompany.com and
the exchange picks them up, recognises their username is a valid one and
then places this their mailbox. There may have been 1 employee leave and you
have removed their account. I know you can just setup a forwarder for that
direct address but if I didnt, it should forward with all the other
undeliverable email to the account I have selected. This is still not
happening.

Can anyone else help?

Adam

news:vMmdna6IrIXw1vLfRVn-gg@speakeasy.net...

Hi Adam,

Thanks for your update.

As for you scenario, please help me collect the following information to
isolate the issue:

1. Select another user mailbox to receive those undeliverable mails, does
this issue persists?

2. What is the exact content of the NDRs? Could you please post the content
of the NDR in the newsgroup?

3. Please set Logging level of the POP3 Connector to Maximum to get more
verbose information and then reproduce the issue. After that, check in the
event viewer to see if there is any event log related to this issue. To set
logging level:

= a = Click Start, point to All Programs, point to Microsoft Exchange and
then click System Manager.
= b = Expand Connectors, right-click POP3 Connector Manager and click
Properties.
= c = On the Troubleshooting tab, set Logging level to Maximum.
= d = Click OK.
= e = Restart the Microsoft Connector for POP3 Mailboxes. To do so:
  A. Click Start, point to Administrative Tools and click Services.
  B. Locate and right-click the Microsoft Connector for POP3 Mailboxes
service, click Restart.
= f = On Exchange System Manager right-click POP3 Connector Manager and
click Properties, on the Scheduling tab, click Retrieve Now.

For your information:

How to troubleshoot the POP3 Connector in Windows Small Business Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;885685

If you have any concern on this thread, I am glad to be of further
assistance. We look forward to hearing from you.

Best regards,

Jerry Zhao (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Jerry

I have tried using a different mailbox to collect the undeliverable mails but this does not work.

The exact content on the NDRs is as follows:

Sender received an email titled "Delivery Status Notification (Failure)"
The message part of the email says
This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

a...@COMPANY.COM

There are 2 attachments to the email. One is a copy of the original email sent and the other is a text file called details.txt and this text file has the following data:

Reporting-MTA: dns;company.com
Received-From-MTA: dns;company.com
Arrival-Date: Mon, 2 May 2005 13:30:26 +1000

Final-Recipient: rfc822;a...@COMPANY.COM
Action: failed
Status: 5.1.1

I have followed the instructions on the Troubleshooting the POP3 connector in SBS2003 that you provided and I had the following results:

The emails go to the %programfiles%\exchsrvr\mailroot\vsi1\pickup folder when SMTP is stopped.
When I start the SMTP back up the email, SMTP then attempts to deliver the email to the user. Since this user does not exist, the sender is sent a NDR.

The following appears in the event viewer:

Event Type: Information
Event Source: POP3 Connector
Event Category: Download
Event ID: 1017
Date:  2/05/2005
Time:  2:37:40 PM
User:  N/A
Computer: DIGITAL
Description:
The message downloading process started.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Download
Event ID: 1013
Date:  2/05/2005
Time:  2:37:40 PM
User:  N/A
Computer: DIGITAL
Description:
Microsoft Connector for POP3 Mailboxes is attempting to connect to the Internet in order to access POP3 mailboxes.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Delivery
Event ID: 1042
Date:  2/05/2005
Time:  2:37:40 PM
User:  N/A
Computer: DIGITAL
Description:
Delivery Manager has started to monitor the Incoming Mail queue for messages to be delivered to Exchange user accounts.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Download
Event ID: 1032
Date:  2/05/2005
Time:  2:37:40 PM
User:  N/A
Computer: DIGITAL
Description:
The POP3 agent will open the mailbox <xxx [po.xxx.net]> on port 110.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Download
Event ID: 1027
Date:  2/05/2005
Time:  2:37:40 PM
User:  N/A
Computer: DIGITAL
Description:
The POP3 server (mailbox <po.xxx.net [xxx]>) responded to the Microsoft Connector for POP3 Mailboxes connection with: <+OK xxx.Net. POP3 server ready Mon, 2 May 2005 14:37:16 +0800 [ISafe POP3 Proxy]

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Download
Event ID: 1028
Date:  2/05/2005
Time:  2:37:41 PM
User:  N/A
Computer: DIGITAL
Description:
Access was granted to the mailbox <po.xxx.net> logging on as <xxx>.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Download
Event ID: 1031
Date:  2/05/2005
Time:  2:37:41 PM
User:  N/A
Computer: DIGITAL
Description:
There are 1 message(s) with a total of 13785
 byte(s) for mailbox <po.pacific.net.au [xxx]>.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Download
Event ID: 1064
Date:  2/05/2005
Time:  2:37:42 PM
User:  N/A
Computer: DIGITAL
Description:
The message <id:{CEA0DCEB-EE11-4EB0-94FA-6690F1E881F4}> was downloaded from the POP3 server (mailbox <xxx [po.xxx.net]>).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Download
Event ID: 1065
Date:  2/05/2005
Time:  2:37:42 PM
User:  N/A
Computer: DIGITAL
Description:
The message <id:{CEA0DCEB-EE11-4EB0-94FA-6690F1E881F4}> was deleted from the POP3 server (mailbox <xxx [po.xxx.net]>).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Download
Event ID: 1030
Date:  2/05/2005
Time:  2:37:42 PM
User:  N/A
Computer: DIGITAL
Description:
The POP3 session transcript for mailbox <po.xxx.net [xxx]> was:
<S>: +OK xxx.Net POP3 server ready Mon, 2 May 2005 14:37:16 +0800 [ISafe POP3 Proxy]
<C>: USER xxx
<S>: +OK Password required
<C>: PASS <secret password>
<S>: +OK Maildrop has 1 messages (13785 octets)
<C>: STAT
<S>: +OK 1 13785
<C>: {Downloaded and deleted messages if neccessary}
<C>: QUIT
<S>: +OK pob1.xxx.net POP3 server closing connection

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Download
Event ID: 1018
Date:  2/05/2005
Time:  2:37:42 PM
User:  N/A
Computer: DIGITAL
Description:
The message downloading process finished successfully.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Delivery
Event ID: 1050
Date:  2/05/2005
Time:  2:37:50 PM
User:  N/A
Computer: DIGITAL
Description:
The message <id: {CEA0DCEB-EE11-4EB0-94FA-6690F1E881F4}> was routed by a global mailbox mapping as follows:
Original Recipient: a...@company.com.
- routed via domain substitution to a...@company.com.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Delivery
Event ID: 1051
Date:  2/05/2005
Time:  2:37:50 PM
User:  N/A
Computer: DIGITAL
Description:
The delivery process for message <id: {CEA0DCEB-EE11-4EB0-94FA-6690F1E881F4}> finished successfully.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: POP3 Connector
Event Category: Delivery
Event ID: 1047
Date:  2/05/2005
Time:  2:37:50 PM
User:  N/A
Computer: DIGITAL
Description:
The delivery process finished successfully.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This seems like normal messages as if the emails were delivered correctly. The following information comes from the Message Tracking Centre in exchange.

2/5/05 2:41  SMTP: Message submitted to advanced queuing.
2/5/05 2:41  SMTP: Started Message Submission to Advanced Queue
2/5/05 2:41  SMTP: Message Submitted to Categorizer
2/5/05 2:41  SMTP: Message Categorized and Queued for Routing
2/5/05 2:41  SMTP: Non-Delivered Report (NDR) Generated

Any help on why the emails are not being delivered to the selected mailbox and bouncing??

Thanks

Adam

Hi Adam,

Thanks for your posting.

Please also check if the undelivered mails in the following folder:

%systemroot%\Program Files\Microsoft Small Business
Server\Networking\POP3\Failed Mail folder %systemroot%\Program
Files\Microsoft Small Business Server\Networking\POP3\Failed Mail

Meanwhile, please post the entire message tracking log in the newsgroup for
further troubleshooting. The log files located in:

C:\program files\Exchsrvr\domainname.log\

We may also need to enable Exchange diagnostic log and check if there's any
clue. To do so:

Open ESM, expand servers, right click on the server's name, and select
properties. In the diagnostics logging tab, enable all categories to max in
the Msexchange transport service, also enable the mailbox in the
MSexchangeIS to max.

Then reproduce the issue and check the event log to see if there is any
record.

If you have any other problems, please feel free to get back here.

Best regards,

Jerry Zhao (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Adam,

Thanks for the information that you have provided.

Since your issue is a little bit strange, we are still researching on it.

If there is any  progress, i will let you know at the first time.

If you have any other problems, please feel free to get back here.

Best regards,

Jerry Zhao (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Adam,

How are you?

Here I want to collect more information:

1. When did this issue happen? Did the undeliverable mailbox ever work?

2. Run the imbreg.exe to re-register the POP3 Event Sink. To do so, open
Windows Explorer, go to the "C:\Program Files\Microsoft Windows Small
Business Server\Networking\POP3" folder and double click to run IMBReg.exe.

3. Do you have any third party SMTP event sink installed on the SBS server?

Thanks for your time.

Best regards,

Jerry Zhao (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Jerry

I do believe this was working when the SBS2003 box was first setup but it
hasnt been running for a number of months now.

I have run the imbreg.exe and it has not fixed the problem.

The SBS box has a 3rd party program called Firebird 1.5 running on it. This
is a database program that links in with the IIS component of SBS. The
webpage is being hosted on the SBS server and the webpage links directly
into the webpage. There were problems initially with Firebird locking down
due to its port being taken by a Windows process. Since that port number has
been blocked from any other processes picking it up other than Firebird
there have been no more problems with Firebird or the webpage.

I am not sure if this information helps or not. I am getting to the stage
where I might have to spend the $297 AUS to get Microsoft to have a look at
the problem.

Your thoughts?

Regards

Adam

"Jerry zhao (MSFT)" <v-jer...@online.microsoft.com> wrote in message
news:jHGHs6EUFHA.388@TK2MSFTNGXA01.phx.gbl...

Hi Adam,

As for your scenario, I would like to recommend that you reinstall the POP3
connector and then check if there is any change.

To reinstall POP3 Connector:

1. Rename the POP folder to POP.old in the following location:

C:\Program Files\Microsoft Windows Small Business Server\Networking

2. Use regedit, locate the "POP3 Connector" key in the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Network

3. Export the "POP3 Connector" key to the desktop as a backup. Delete the
"POP3 Connector" key and close the registry editor.

4. In Windows Explorer, show hidden and system files by going to "Tools",
"Folder Options" and "Views", and unhide the hidden files, as well as the
system files.

5. Search for and delete all SITxxxxx.tmp folders, you may use SIT*tmp as a
wildcard.

6. Manually execute the POP3.MSI file from the SBS 2003 CD #3, \SBS\POP3
folder. This should show the "Preparing to install" and then some actual
install progress going on.

If you get the error from step 6, perform the following to reinstall
Exchange over itself.

Go to Control Panel, Add/Remove Programs, Select "Windows Small Business
Server 2003" and select Change/Remove. This will enter into the Integrated
Setup and the Component Selection screen. Select Networking and Exchange
Server for "reinstall".

If you have any questions or concerns, please feel free to let me know.

Best regards,

Jerry Zhao (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.