Random undeliverable messages

Don S · Joined: 06 Aug 2007 Posts: 1

We are using Exchange 2003 on Server 2003. We are getting random undeliverable e-mails that IMMEDIATELY get returned to the sender stating that ALL recipients could not be found. If the sender re-sends the message, most of the time it sends without error. The exchange server is pointing to an internal DNS server. Why would seemingly random messages be rejected? Why would it not be able to resolve internal e-mail addresses on the same server?

Thanks in advance,

Don

Here is an example with private information modified:

Your message did not reach some or all of the intended recipients.

Subject: Activity Report
Sent: 12/1/2003 4:43 PM

The following recipient(s) could not be reached:

John Smith on 12/1/2003 4:43 PM
The e-mail address could not be found. Perhaps the recipient moved to a different e-mail organization, or there was a mistake in the address. Check the address and try again.

jane.doe@somecompany.com on 12/1/2003 4:43 PM
The e-mail address could not be found. Perhaps the recipient moved to a different e-mail organization, or there was a mistake in the address. Check the address and try again.

I also get this event for each address (again, private content is modified)

Event Type: Error
Event Source: MSExchangeTransport
Event Category: NDR
Event ID: 3009
Date: 12/1/2003
Time: 4:42:55 PM
User: N/A
Computer: MAIL01
Description:
A non-delivery report with a status code of 5.1.0 was generated for recipient x-ex;/O=EXCHANGE ORGANIZATION/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=JSmith (Message-ID ).
Cause: This is categorizer failure caused by a bad address.
For more information, click http://www.microsoft.com/contentredirect.asp.
Solution: Either the recipient address is incorrectly formatted or the categorizer was not able to properly resolve the recipient. Checking the recipient address and re-sending the message is the first step to resolving this error.
Data:
0000: bb f9 ff ff Â»Ã¹Ã¿Ã¿

I have searched for this event ID and not found anything yet.

Archived from group: microsoft>public>exchange2000>connectivity

Doug Blanchard · Joined: 05 Aug 2007 Posts: 3

1) Make sure that your DNS has the .local address configured.
2) Check your Recipient Policies. Do not change the SMTP addresses on the
DEFAULT Rec Pol
3) Set the SMTP VS to default values if not already
4) Remove SMTP connectors
5) Check the Users in the DL to ensure that they have correct email
addresses. I suggest using CSVDE from the Support Tools.

--
Doug Blanchard
Microsoft PSS

Please do not send email directly to this alias. This alias is for newsgroup
purposes only. This posting is provided "AS IS" with no warranties, and
confers no rights.
"Don S" wrote in message@microsoft.com...
> We are using Exchange 2003 on Server 2003. We are getting random
undeliverable e-mails that IMMEDIATELY get returned to the sender stating
that ALL recipients could not be found. If the sender re-sends the message,
most of the time it sends without error. The exchange server is pointing to
an internal DNS server. Why would seemingly random messages be rejected?
Why would it not be able to resolve internal e-mail addresses on the same
server?
>
> Thanks in advance,
>
> Don
>
> Here is an example with private information modified:
>
> Your message did not reach some or all of the intended recipients.
>
> Subject: Activity Report
> Sent: 12/1/2003 4:43 PM
>
> The following recipient(s) could not be reached:
>
> John Smith on 12/1/2003 4:43 PM
> The e-mail address could not be found. Perhaps the recipient
moved to a different e-mail organization, or there was a mistake in the
address. Check the address and try again.
>
>
> jane.doe@somecompany.com on 12/1/2003 4:43 PM
> The e-mail address could not be found. Perhaps the recipient
moved to a different e-mail organization, or there was a mistake in the
address. Check the address and try again.
>
>
> I also get this event for each address (again, private content is
modified)
>
> Event Type: Error
> Event Source: MSExchangeTransport
> Event Category: NDR
> Event ID: 3009
> Date: 12/1/2003
> Time: 4:42:55 PM
> User: N/A
> Computer: MAIL01
> Description:
> A non-delivery report with a status code of 5.1.0 was generated for
recipient x-ex;/O=EXCHANGE ORGANIZATION/OU=FIRST ADMINISTRATIVE
GROUP/CN=RECIPIENTS/CN=JSmith (Message-ID
).
> Cause: This is categorizer failure caused by a bad address.
> For more information, click http://www.microsoft.com/contentredirect.asp.
> Solution: Either the recipient address is incorrectly formatted or the
categorizer was not able to properly resolve the recipient. Checking the
recipient address and re-sending the message is the first step to resolving
this error.
> Data:
> 0000: bb f9 ff ff »ùÿÿ
>
> I have searched for this event ID and not found anything yet.
>

Brian Hampson · Joined: 06 Aug 2007 Posts: 1

We are experiencing the same problem - RANDOM NDR's. The same
message, resent will work fine one time, but not another. Random.
These all result in EventID 3009 with MSExchangeTransport as source
and category NDR.

Doug, would the settings you mention below cause _RANDOM_ NDR's?

Thanks,

Brian Hampson

"Doug Blanchard" wrote in message news:...
> 1) Make sure that your DNS has the .local address configured.
> 2) Check your Recipient Policies. Do not change the SMTP addresses on the
> DEFAULT Rec Pol
> 3) Set the SMTP VS to default values if not already
> 4) Remove SMTP connectors
> 5) Check the Users in the DL to ensure that they have correct email
> addresses. I suggest using CSVDE from the Support Tools.
>
> --
> Doug Blanchard
> Microsoft PSS
>
> Please do not send email directly to this alias. This alias is for newsgroup
> purposes only. This posting is provided "AS IS" with no warranties, and
> confers no rights.
> "Don S" wrote in message
> @microsoft.com...
> > We are using Exchange 2003 on Server 2003. We are getting random
> undeliverable e-mails that IMMEDIATELY get returned to the sender stating
> that ALL recipients could not be found. If the sender re-sends the message,
> most of the time it sends without error. The exchange server is pointing to
> an internal DNS server. Why would seemingly random messages be rejected?
> Why would it not be able to resolve internal e-mail addresses on the same
> server?
> >
> > Thanks in advance,
> >
> > Don
> >
> > Here is an example with private information modified:
> >
> > Your message did not reach some or all of the intended recipients.
> >
> > Subject: Activity Report
> > Sent: 12/1/2003 4:43 PM
> >
> > The following recipient(s) could not be reached:
> >
> > John Smith on 12/1/2003 4:43 PM
> > The e-mail address could not be found. Perhaps the recipient
> moved to a different e-mail organization, or there was a mistake in the
> address. Check the address and try again.
> >
> >
> > jane.doe@somecompany.com on 12/1/2003 4:43 PM
> > The e-mail address could not be found. Perhaps the recipient
> moved to a different e-mail organization, or there was a mistake in the
> address. Check the address and try again.
> >
> >
> > I also get this event for each address (again, private content is
> modified)
> >
> > Event Type: Error
> > Event Source: MSExchangeTransport
> > Event Category: NDR
> > Event ID: 3009
> > Date: 12/1/2003
> > Time: 4:42:55 PM
> > User: N/A
> > Computer: MAIL01
> > Description:
> > A non-delivery report with a status code of 5.1.0 was generated for
> recipient x-ex;/O=EXCHANGE ORGANIZATION/OU=FIRST ADMINISTRATIVE
> GROUP/CN=RECIPIENTS/CN=JSmith (Message-ID
> ).
> > Cause: This is categorizer failure caused by a bad address.
> > For more information, click http://www.microsoft.com/contentredirect.asp.
> > Solution: Either the recipient address is incorrectly formatted or the
> categorizer was not able to properly resolve the recipient. Checking the
> recipient address and re-sending the message is the first step to resolving
> this error.
> > Data:
> > 0000: bb f9 ff ff »ùÿÿ
> >
> > I have searched for this event ID and not found anything yet.
> >

Don S · Joined: 06 Aug 2007 Posts: 2

Doug -

1) The mail01.local address is in DNS (it is not a public
domain, obviously). I assume this is what you meant?

2) The recipient policy has one SMTP address in it - it
is our external e-mail address as we are migrating from
an ISP and still need to download from their POP account

3) I am using two SMTP VS's: one for normal outgoing SMTP
and one for relaying. The one for relaying had anonymous
access disabled. I've removed the realying SMTP server
to see if that was the problem

4) There are no SMTP connectors

5) The messages were not sent to DLs. They were sent to
individuals, both internal and external

Why would a message get rejected, only to go through
minutes later after re-sending to the exact same
recipients?

Thanks for your help,

Don

>-----Original Message-----
>1) Make sure that your DNS has the .local address
configured.
>2) Check your Recipient Policies. Do not change the
SMTP addresses on the
>DEFAULT Rec Pol
>3) Set the SMTP VS to default values if not already
>4) Remove SMTP connectors
>5) Check the Users in the DL to ensure that they have
correct email
>addresses. I suggest using CSVDE from the Support Tools.
>
>--
>Doug Blanchard
>Microsoft PSS
>
>Please do not send email directly to this alias. This
alias is for newsgroup
>purposes only. This posting is provided "AS IS" with no
warranties, and
>confers no rights.
>"Don S" wrote in message
>
2A9B025DD7F1@microsoft.com...
>> We are using Exchange 2003 on Server 2003. We are
getting random
>undeliverable e-mails that IMMEDIATELY get returned to
the sender stating
>that ALL recipients could not be found. If the sender
re-sends the message,
>most of the time it sends without error. The exchange
server is pointing to
>an internal DNS server. Why would seemingly random
messages be rejected?
>Why would it not be able to resolve internal e-mail
addresses on the same
>server?
>>
>> Thanks in advance,
>>
>> Don
>>
>> Here is an example with private information modified:
>>
>> Your message did not reach some or all of the intended
recipients.
>>
>> Subject: Activity Report
>> Sent: 12/1/2003 4:43 PM
>>
>> The following recipient(s) could not be reached:
>>
>> John Smith on 12/1/2003 4:43 PM
>> The e-mail address could not be found.
Perhaps the recipient
>moved to a different e-mail organization, or there was a
mistake in the
>address. Check the address and try again.
>>
>>
>> jane.doe@somecompany.com on 12/1/2003 4:43 PM
>> The e-mail address could not be found.
Perhaps the recipient
>moved to a different e-mail organization, or there was a
mistake in the
>address. Check the address and try again.
>>
>>
>> I also get this event for each address (again, private
content is
>modified)
>>
>> Event Type: Error
>> Event Source: MSExchangeTransport
>> Event Category: NDR
>> Event ID: 3009
>> Date: 12/1/2003
>> Time: 4:42:55 PM
>> User: N/A
>> Computer: MAIL01
>> Description:
>> A non-delivery report with a status code of 5.1.0 was
generated for
>recipient x-ex;/O=EXCHANGE ORGANIZATION/OU=FIRST
ADMINISTRATIVE
>GROUP/CN=RECIPIENTS/CN=JSmith (Message-ID
>).
>> Cause: This is categorizer failure caused by a bad
address.
>> For more information, click
http://www.microsoft.com/contentredirect.asp.
>> Solution: Either the recipient address is incorrectly
formatted or the
>categorizer was not able to properly resolve the
recipient. Checking the
>recipient address and re-sending the message is the
first step to resolving
>this error.
>> Data:
>> 0000: bb f9 ff ff »ùÿÿ
>>
>> I have searched for this event ID and not found
anything yet.
>>
>
>
>.
>

Doug Blanchard · Joined: 05 Aug 2007 Posts: 3

2 SMTP Virtual Servers may have some problems - not always though. When
starting the SMTP service, the server chooses which ever SMTP VS that
responds 1st to its query for configuring the sending VS. This could be
either VS and is not user defined. So the limitations of 1 VS may affect
all users.

I suggest eliminating the second VS and set the default back to the standard
settings. Also, check your clients profile to ensure that they only have 1
service configured (I.E. Microsoft Exchange Server).

As for DNS, just ensure that there is no INTERNAL DNS MX record
(mail01.local -or- domain.com). If so, remove it as there is no need for
internal MX records - only host records.

Doug Blanchard
Microsoft PSS

Please do not send email directly to this alias. This alias is for newsgroup
purposes only. This posting is provided "AS IS" with no warranties, and
confers no rights.
"Don S" wrote in message$ed0ddc10$a401280a@phx.gbl...
Doug -

1) The mail01.local address is in DNS (it is not a public
domain, obviously). I assume this is what you meant?

2) The recipient policy has one SMTP address in it - it
is our external e-mail address as we are migrating from
an ISP and still need to download from their POP account

3) I am using two SMTP VS's: one for normal outgoing SMTP
and one for relaying. The one for relaying had anonymous
access disabled. I've removed the realying SMTP server
to see if that was the problem

4) There are no SMTP connectors

5) The messages were not sent to DLs. They were sent to
individuals, both internal and external

Why would a message get rejected, only to go through
minutes later after re-sending to the exact same
recipients?

Thanks for your help,

Don

>-----Original Message-----
>1) Make sure that your DNS has the .local address
configured.
>2) Check your Recipient Policies. Do not change the
SMTP addresses on the
>DEFAULT Rec Pol
>3) Set the SMTP VS to default values if not already
>4) Remove SMTP connectors
>5) Check the Users in the DL to ensure that they have
correct email
>addresses. I suggest using CSVDE from the Support Tools.
>
>--
>Doug Blanchard
>Microsoft PSS
>
>Please do not send email directly to this alias. This
alias is for newsgroup
>purposes only. This posting is provided "AS IS" with no
warranties, and
>confers no rights.
>"Don S" wrote in message
>
2A9B025DD7F1@microsoft.com...
>> We are using Exchange 2003 on Server 2003. We are
getting random
>undeliverable e-mails that IMMEDIATELY get returned to
the sender stating
>that ALL recipients could not be found. If the sender
re-sends the message,
>most of the time it sends without error. The exchange
server is pointing to
>an internal DNS server. Why would seemingly random
messages be rejected?
>Why would it not be able to resolve internal e-mail
addresses on the same
>server?
>>
>> Thanks in advance,
>>
>> Don
>>
>> Here is an example with private information modified:
>>
>> Your message did not reach some or all of the intended
recipients.
>>
>> Subject: Activity Report
>> Sent: 12/1/2003 4:43 PM
>>
>> The following recipient(s) could not be reached:
>>
>> John Smith on 12/1/2003 4:43 PM
>> The e-mail address could not be found.
Perhaps the recipient
>moved to a different e-mail organization, or there was a
mistake in the
>address. Check the address and try again.
>>
>>
>> jane.doe@somecompany.com on 12/1/2003 4:43 PM
>> The e-mail address could not be found.
Perhaps the recipient
>moved to a different e-mail organization, or there was a
mistake in the
>address. Check the address and try again.
>>
>>
>> I also get this event for each address (again, private
content is
>modified)
>>
>> Event Type: Error
>> Event Source: MSExchangeTransport
>> Event Category: NDR
>> Event ID: 3009
>> Date: 12/1/2003
>> Time: 4:42:55 PM
>> User: N/A
>> Computer: MAIL01
>> Description:
>> A non-delivery report with a status code of 5.1.0 was
generated for
>recipient x-ex;/O=EXCHANGE ORGANIZATION/OU=FIRST
ADMINISTRATIVE
>GROUP/CN=RECIPIENTS/CN=JSmith (Message-ID
>).
>> Cause: This is categorizer failure caused by a bad
address.
>> For more information, click
http://www.microsoft.com/contentredirect.asp.
>> Solution: Either the recipient address is incorrectly
formatted or the
>categorizer was not able to properly resolve the
recipient. Checking the
>recipient address and re-sending the message is the
first step to resolving
>this error.
>> Data:
>> 0000: bb f9 ff ff »ùÿÿ
>>
>> I have searched for this event ID and not found
anything yet.
>>
>
>
>.
>

Don S. · Joined: 06 Aug 2007 Posts: 1

What problems could having multiple accounts on the
clients cause? Our clients still use our ISP's POP
server to download e-mail until we can change our MX
record. That account also uses the ISP's SMTP server as
well. Why would the other SMTP account cuase problems
trying to send mail through Exchange, though?

Don

>-----Original Message-----
>2 SMTP Virtual Servers may have some problems - not
always though. When
>starting the SMTP service, the server chooses which ever
SMTP VS that
>responds 1st to its query for configuring the sending
VS. This could be
>either VS and is not user defined. So the limitations
of 1 VS may affect
>all users.
>
>I suggest eliminating the second VS and set the default
back to the standard
>settings. Also, check your clients profile to ensure
that they only have 1
>service configured (I.E. Microsoft Exchange Server).
>
>As for DNS, just ensure that there is no INTERNAL DNS MX
record
>(mail01.local -or- domain.com). If so, remove it as
there is no need for
>internal MX records - only host records.
>
>Doug Blanchard
>Microsoft PSS
>
>Please do not send email directly to this alias. This
alias is for newsgroup
>purposes only. This posting is provided "AS IS" with no
warranties, and
>confers no rights.
>"Don S" wrote in
message
>$ed0ddc10$a401280a@phx.gbl...
>Doug -
>
>1) The mail01.local address is in DNS (it is not a public
>domain, obviously). I assume this is what you meant?
>
>2) The recipient policy has one SMTP address in it - it
>is our external e-mail address as we are migrating from
>an ISP and still need to download from their POP account
>
>3) I am using two SMTP VS's: one for normal outgoing SMTP
>and one for relaying. The one for relaying had anonymous
>access disabled. I've removed the realying SMTP server
>to see if that was the problem
>
>4) There are no SMTP connectors
>
>5) The messages were not sent to DLs. They were sent to
>individuals, both internal and external
>
>Why would a message get rejected, only to go through
>minutes later after re-sending to the exact same
>recipients?
>
>Thanks for your help,
>
>Don
>
>>-----Original Message-----
>>1) Make sure that your DNS has the .local address
>configured.
>>2) Check your Recipient Policies. Do not change the
>SMTP addresses on the
>>DEFAULT Rec Pol
>>3) Set the SMTP VS to default values if not already
>>4) Remove SMTP connectors
>>5) Check the Users in the DL to ensure that they have
>correct email
>>addresses. I suggest using CSVDE from the Support Tools.
>>
>>--
>>Doug Blanchard
>>Microsoft PSS
>>
>>Please do not send email directly to this alias. This
>alias is for newsgroup
>>purposes only. This posting is provided "AS IS" with no
>warranties, and
>>confers no rights.
>>"Don S" wrote in message
>>
>2A9B025DD7F1@microsoft.com...
>>> We are using Exchange 2003 on Server 2003. We are
>getting random
>>undeliverable e-mails that IMMEDIATELY get returned to
>the sender stating
>>that ALL recipients could not be found. If the sender
>re-sends the message,
>>most of the time it sends without error. The exchange
>server is pointing to
>>an internal DNS server. Why would seemingly random
>messages be rejected?
>>Why would it not be able to resolve internal e-mail
>addresses on the same
>>server?
>>>
>>> Thanks in advance,
>>>
>>> Don
>>>

Don S · Joined: 06 Aug 2007 Posts: 2

I have deleted the 2nd SMTP Server and reset the default
SMTP server to the original setting as best I could.

I also checked, and there are no MX records in our DNS
server.

I am still getting random unresolved emails; both
internal and external. Any other thoughts?

Thanks again,

Don

>-----Original Message-----
>2 SMTP Virtual Servers may have some problems - not
always though. When
>starting the SMTP service, the server chooses which ever
SMTP VS that
>responds 1st to its query for configuring the sending
VS. This could be
>either VS and is not user defined. So the limitations
of 1 VS may affect
>all users.
>
>I suggest eliminating the second VS and set the default
back to the standard
>settings. Also, check your clients profile to ensure
that they only have 1
>service configured (I.E. Microsoft Exchange Server).
>
>As for DNS, just ensure that there is no INTERNAL DNS MX
record
>(mail01.local -or- domain.com). If so, remove it as
there is no need for
>internal MX records - only host records.
>
>Doug Blanchard
>Microsoft PSS
>
>Please do not send email directly to this alias. This
alias is for newsgroup
>purposes only. This posting is provided "AS IS" with no
warranties, and
>confers no rights.
>"Don S" wrote in
message
>$ed0ddc10$a401280a@phx.gbl...
>Doug -
>
>1) The mail01.local address is in DNS (it is not a public
>domain, obviously). I assume this is what you meant?
>
>2) The recipient policy has one SMTP address in it - it
>is our external e-mail address as we are migrating from
>an ISP and still need to download from their POP account
>
>3) I am using two SMTP VS's: one for normal outgoing SMTP
>and one for relaying. The one for relaying had anonymous
>access disabled. I've removed the realying SMTP server
>to see if that was the problem
>
>4) There are no SMTP connectors
>
>5) The messages were not sent to DLs. They were sent to
>individuals, both internal and external
>
>Why would a message get rejected, only to go through
>minutes later after re-sending to the exact same
>recipients?
>
>Thanks for your help,
>
>Don
>
>>-----Original Message-----
>>1) Make sure that your DNS has the .local address
>configured.
>>2) Check your Recipient Policies. Do not change the
>SMTP addresses on the
>>DEFAULT Rec Pol
>>3) Set the SMTP VS to default values if not already
>>4) Remove SMTP connectors
>>5) Check the Users in the DL to ensure that they have
>correct email
>>addresses. I suggest using CSVDE from the Support Tools.
>>
>>--
>>Doug Blanchard
>>Microsoft PSS
>>

Eddie Harris · Joined: 05 Aug 2007 Posts: 2

I think the problem you're having is that you have accounts on the ISP
that are not in Exchange. Since you have multiple profiles in outlook,
sometimes the client (outlook) gets confused and sends mail that you want to
go to the ISP to Exchange.

Using only one account in your profile, or using Outlook XP may solve this
issue.

"Don S" wrote in message$32843b00$a501280a@phx.gbl...
> I have deleted the 2nd SMTP Server and reset the default
> SMTP server to the original setting as best I could.
>
> I also checked, and there are no MX records in our DNS
> server.
>
> I am still getting random unresolved emails; both
> internal and external. Any other thoughts?
>
> Thanks again,
>
> Don
>
> >-----Original Message-----
> >2 SMTP Virtual Servers may have some problems - not
> always though. When
> >starting the SMTP service, the server chooses which ever
> SMTP VS that
> >responds 1st to its query for configuring the sending
> VS. This could be
> >either VS and is not user defined. So the limitations
> of 1 VS may affect
> >all users.
> >
> >I suggest eliminating the second VS and set the default
> back to the standard
> >settings. Also, check your clients profile to ensure
> that they only have 1
> >service configured (I.E. Microsoft Exchange Server).
> >
> >As for DNS, just ensure that there is no INTERNAL DNS MX
> record
> >(mail01.local -or- domain.com). If so, remove it as
> there is no need for
> >internal MX records - only host records.
> >
> >Doug Blanchard
> >Microsoft PSS
> >
> >Please do not send email directly to this alias. This
> alias is for newsgroup
> >purposes only. This posting is provided "AS IS" with no
> warranties, and
> >confers no rights.
> >"Don S" wrote in
> message
> >$ed0ddc10$a401280a@phx.gbl...
> >Doug -
> >
> >1) The mail01.local address is in DNS (it is not a public
> >domain, obviously). I assume this is what you meant?
> >
> >2) The recipient policy has one SMTP address in it - it
> >is our external e-mail address as we are migrating from
> >an ISP and still need to download from their POP account
> >
> >3) I am using two SMTP VS's: one for normal outgoing SMTP
> >and one for relaying. The one for relaying had anonymous
> >access disabled. I've removed the realying SMTP server
> >to see if that was the problem
> >
> >4) There are no SMTP connectors
> >
> >5) The messages were not sent to DLs. They were sent to
> >individuals, both internal and external
> >
> >Why would a message get rejected, only to go through
> >minutes later after re-sending to the exact same
> >recipients?
> >
> >Thanks for your help,
> >
> >Don
> >
> >>-----Original Message-----
> >>1) Make sure that your DNS has the .local address
> >configured.
> >>2) Check your Recipient Policies. Do not change the
> >SMTP addresses on the
> >>DEFAULT Rec Pol
> >>3) Set the SMTP VS to default values if not already
> >>4) Remove SMTP connectors
> >>5) Check the Users in the DL to ensure that they have
> >correct email
> >>addresses. I suggest using CSVDE from the Support Tools.
> >>
> >>--
> >>Doug Blanchard
> >>Microsoft PSS
> >>

jpickerell · Joined: 06 Aug 2007 Posts: 1

We have also recently started migrating our users over to Exchange 2003
using Outlook 2003 as the client. We also reandomy receive the
non-deliverable messages but can instantly click re-send and it goes
through.

Has anyone found any solutions to this problem?

Thanks

Jared

Jared Pickerell
Co-Director/Network Admin
Information Systems
Highland Community College
606 W Main, Highland, KS 66035
jpickerell@highlandcc.edu

--
jpickerell
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message140391.html

loengard · Joined: 06 Aug 2007 Posts: 1

I have the EXACT same issue. Only one domain, default SMTP server,
recipent policy is correct, and no solution. Has anyone actually fixed
this problem???

jpickerell wrote:
> *We have also recently started migrating our users over to Exchange
> 2003 using Outlook 2003 as the client. We also reandomy receive the
> non-deliverable messages but can instantly click re-send and it goes
> through.
>
> Has anyone found any solutions to this problem?
>
> Thanks
>
> Jared
>
> Jared Pickerell
> Co-Director/Network Admin
> Information Systems
> Highland Community College
> 606 W Main, Highland, KS 66035
> jpickerell@highlandcc.edu *

--
loengard
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message140391.html

How to block messages that come with my domain name Dear folks: Recently I am receiving in my Exchange Server 2000 any kind of bulk messages directed to my users coming from the Internet using my domain name. My users know that they don't want to open messages coming from people in other domains, but now

Undeliverable Messages Dear TechNet, I have an Exchange 2003 SP2 server on Win2k3 SP1, all my Outlook clients are Outlook 2003 SP2. I need some advise how to hendle undelivery messages, with these replayes. Please adivse. Thank you. Your message did not reach som

Messages stuck We have had an issue with our outgoing SMTP email (sent to multiple recipients) getting stuck in queues since the first week of April when there were absolutely no changes made to our servers, firewalls, ISPs, etc. I am lost as a goose an

Incoming Messages Do Not Get Recieved By Exchange This message is indended for the managed news group monitors to resolve. I have a Windows Server 2003 SP1 Acitve Directory Domain Controller that is running Exchange 2003 SP1. The server's FQDN is I have a Registered D

message queue in "Messages pending submission" Hi, We have 3 Exchange 2003 server , one for smtp server and the other two server for mail storage. It is work very well. However if we change the smtp server to Front end server then all the message will queue in "Messages pending submission" folder. Ple