RE: Email failed

Hi Crummo,

Thank you for your kind reply.

As you mentioned, the outbound emails cannot correctly deliver to the
recipients, and the inbound emails are downloaded by POP3 Connector, but
also cannot deliver to the local Exchange Mailbox.

1. Please perform the following steps to re-run CEICW:

A. Run the CEICW and go through the Internet, firewall and Web Server
Certificate option.

B. In the Internet E-mail tab, please click to "Enable Internet E-mail"

C. In the E-mail Delivery method page, please choose "Use DNS to route
e-mail" option.

D. In the E-mail Retrieval Method, please choose "Use the Microsoft
Connector for POP3 Mailboxes" option.

E. In the email domain name page, please input the correct email domain
name of your company, such as yourcompany.com. (you could consult your ISP
for this information). Please do not input .local email domain name, since
the .local address is not allowed to use on internet.

F. Input the correct information in the rest page and finish the wizard.
Note: you could just leave the option unchanged, since your Exchange could
receive internet emails fine.

Note: If the issue persists, please choose "forward all email to email
server at ISP" in the E-mail Delivery method page, then input the ISP email
server IP address correctly, you should type the IP address as
"[12.34.56.78]" (without the quotation marks) on the connector's properties
page.

2. Configure the credential for Mail server at your ISP if authentication
is needed.

a. Open Exchange System Manager and navigate to Connectors.

b. Right click the SMTP connector and click properties.

c. In the Advanced tab, please click Outbound security button.

d. Use Basic Authentication and input the correct user name and password.

3. Please run imbreg.exe which is located in the %systemroot%\Program
Files\Microsoft Small Business Server\Networking\POP3 folder to
re-register the POP3 Conn Event Sink, and then check if the issue can be
reproduced.

To get additional information, you may refer to the below KB article:

885685 How to troubleshoot the POP3 Connector in Windows Small Business
Server 2003
http://support.microsoft.com/?id=885685

821910 How to troubleshoot for Exchange Server 2003 transport issues
http://support.microsoft.com/?id=821910

842293 Event 1070 is logged and e-mail messages are not delivered with the
SBS 2003 Connector for POP3 Mailboxes
http://support.microsoft.com/?id=842293

I am appreciated 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: Email failed
>thread-index: AcWTsWc8XdP9hab/TU2qHarSZmUP9A==
>X-WBNR-Posting-Host: 80.229.44.244
>From: =?Utf-8?B?Q3J1bW1v?= <Crummo@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <A5D5656A-76E0-449B-BCA5-C1173EA53C01@xxxxxxxxxxxxx>
<1u9ReA0kFHA.3472@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: Email failed
>Date: Thu, 28 Jul 2005 13:17:40 -0700
>Lines: 228
>Message-ID: <BCABB763-C5A5-4558-94D9-D8ACE3748911@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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:139643
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hi Nathan
>Thanks for taking an interest
>
>Just to clarify the problem a) Internal and external email leaves Outlook
on
>the senders PC but does not arrive either internally or externally, nor
does
>it show up in the Exchange ques. Note: The only emails that are an
exception
>to this are emails generated by the system such as interruption to service
>alerts or System Performance Reports these are both set to send to me at
an
>external email address and are still arriving at my home account. b)
Incoming
>emails are still picked up from our ISP by the POP3 connector but they do
not
>reach any mailboxes they only get as far as the Local Que in the Exchange
>Queues.
>
>1. Checked services yes SMTP service is running.
>With regard to "Task 'Microsoft Exchange Server' reported
error(0x8004011B)
>: 'Unknown error 0x8004011B"
>http://support.microsoft.com/default.aspx?scid=kb;en-us;555049
>I read this article originally but did not take any of the courses of
action
>it suggested but assumed acorruption of Exchange and rather than get into
>ESEUTIL and ISINTEG which I have never used and was warned away from by
more
>experienced people I instead decided to restore an Exchange database from
13
>days earlier. After this we no longer got the above error message when
>Outlook was sending and receiving and so assumed all was well.
>
>2. I disabled Escan/Mailscan and tried email - no change. In a web
>discussion last night MWTI admitted that there had been a problem with an
>update they had sent out last Friday but that this had been corrected by a
>further update. Updates are set to auto install on server and clients.
>
>328841 Exchange and antivirus software - phew, Ive read that lot now.
>
>3. I have excluded the folders from the scan as you suggest, the files
were
>already excluded.
>
>4. There is no error message when a user tries to send an email, it
flashes
>up that it is Sending Receiving and then Complete as usual. No NDR it just
>vanishes (somewhere)
>
>5. Went through settings as you outlined but there is no SmtpSvc1 folder
at
>"%systemroot%\system32\logfiles\SmtpSvc1 the folders there are W3CV1 W3CV3
>W3CV4 I made a copy of W3CV1 if that is correct but what shoul I do with
it?
>It's about 25 A4 pages bu shows nothing in the time frame that I did this
>check.
>
>6. I checked all services as medium logging - Event viewer shows the POP 3
>connector starting a scheduled event and working through to Delivery Event
>1047. No other progs are appearing in event viewer under applications at
this
>time (users gone home it's 21:00) previous events such as me
>stopping/starting SMTP obviously are in there.
>
>Hope that helps.
>
>It has been suggested to me that I should Emerge the data and then
uninstall
>and re-install exchange. There is no facility in Add/Remove programs or
>Windows components or ProgramFiles Exchange to do so and the Dell SBS
>reinstallation disc while having Exchange on Disc 2 also doesnot have an
>uninstall exchange option. So I guess that's a no go or a very tricky
>exercise.
>
>Thanks from a rainy night in England
>Chris
>
>""Nathan Liu [MSFT]"" wrote:
>
>> Hello Crummo,
>>
>> Thank you for posting in the SBS newsgroup.
>>
>> According to your description, I understand that you cannot send
internal
>> email. If I have misunderstood your concern, please don't hesitate to
let
>> me know.
>>
>> To narrow down this issue, please answer and perform the following
>> questions and steps:
>>
>> 1. As you mentioned, you cannot send internal emails, please help me
>> re-confirm if you can send outbound/external emails. If you also cannot
>> send outbound emails, please re-check the running status of the SMTP
Server
>> on the SBS Server.
>>
>> "Task 'Microsoft Exchange Server' reported error (0x8004011B) : 'Unknown
>> error 0x8004011B"
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;555049
>>
>> 2. As you mentioned, you have installed the MWTI Ecsan/Mailscan
antivirus
>> software, please try to temporarily uninstall or disable the program on
the
>> Server side and the Client side, and then check if the issue can be
>> re-produced.
>>
>> 328841 Exchange and antivirus software
>> http://support.microsoft.com/?id=328841
>>
>> 3. Please configure the Anti-Virus software exclude the below folders
and
>> files in scan scope:
>>
>> Folders
>> C:\Program Files\Microsoft Windows Small Business
>> Server\Networking\POP3\Incoming mail
>> C:\Program Files\Exchsrvr
>> C:\Windows\system32\inetsrv
>> C:\Windows\system32\lls
>>
>> Files
>> C:\pagefile.sys
>> C:\windows\system32\licstr.cpa
>>
>> 4. What's the error message when the user tries to send internal
emails?
>> Is there any NDR (Non-Delivery Report)? If yes, Please kindly paste the
>> context in your reply.
>>
>> 5. To further troubleshoot the issue, please help gather SMTP log:
>>
>> 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 7 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".
>>
>> 6. Please also enable the Message Tracking logs:
>>
>> You may try the steps in the following KB articles:
>>
>> 823864 Improved Message Tracking Features in Exchange Server 2003
>> http://support.microsoft.com/?id=823864
>>
>> 821910 How to troubleshoot for Exchange Server 2003 transport issues
>> http://support.microsoft.com/?id=821910
>>
>> I am appreciated 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: Email failed
>> >thread-index: AcWSunu6spK7DE6qSnOJE6mUog5pQg==
>> >X-WBNR-Posting-Host: 80.229.44.244
>> >From: =?Utf-8?B?Q3J1bW1v?= <Crummo@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >Subject: Email failed
>> >Date: Wed, 27 Jul 2005 07:50:08 -0700
>> >Lines: 17
>> >Message-ID: <A5D5656A-76E0-449B-BCA5-C1173EA53C01@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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:139166
>> >X-Tomcat-NG: microsoft.public.windows.server.sbs
>> >
>> >Current problem - Cannot send internal email - message leaves Outllook
but
>> >does not reach destination, also no sign of it in Echange que.
>> >External email is picked up by POP3 connector and only gets as far as
>> >Exchange Local Delivery que where it sits on Retry.
>> >
>> >Problems started with erroneous reporting of emails as containing
viruses.
>> >Antivirus is MWTI Ecsan/Mailscan. Also Outlook would finish a
Send/Receive
>> >with "Unknown Exchange error 0X8004011B. from related knowledge base
>> article
>> >this seemed to link with first problem as one suggested cause was the
>> >scanning of the exchange database by antivirus software.
>> >
>> >Action taken - restored Exchange database to 13 days earlier, when
known
>> to
>> >be ok. Outlook no longer reports errors on Send/Receive but we have
mail
>> >problems as stated above.
>> >
>> >Resolution would be gratefully received
>> >Thanks
>> >
>>
>>
>

.