Re: Outbound Messages sitting in Queue



"Rich Matheisen [MVP]" wrote:

> BrianW <BrianW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >I have Server 03 sp1 installed. I was able to successfully ping as you
> >suggested. Also, the NIC that is on the server will not allow me to change
> >the MTU settings to below 1500. That is the lowest setting, and it is the
> >default.
>
> Change it in the registry -- unless the card offloads a good part of
> the IP stack to its own firmware.
>
> >It appears that the majority of the addresses in the queue that are in a
> >retry state are either invalid e-mail domains, or some type of a spam
> >address.
>
> Well, that's to be expected, then.
>
> >All of the e-mail that is sent to our clients is able to be
> >processed by the server.
>
> So there isn't a problem when sending to legitimate domains? Good.
>
> >Also, I have ran a nslookup on some of the
> >addresses, and they do not come back as valid domain names. Is there a way
> >for me to delete them from the queue at that point?
>
> Sure. But it's really slow. Right-click the queue, display its
> properties. Click the "Find now" button. Select all the messages,
> right-click them and select "Delete (no ndr)". Repeat.
>
> Or you can get the aqadmcli.exe tool from MS. The syntax is kinda hard
> to grasp, but it'll let you clear all the messages in a queue faster
> than the UI (or maybe not, if you count the time it takes to type te
> command line).

I am attempting to use this utility, and I am typing the following syntax.
'I want to remove everything from the queue'

setserver [sn]
delmsg flags=all

I receive the following error. 'GetLinkEnum failed with 0x800706ba'

Any ideas?

Thank you!
Brian
>
> You can eliminate a good deal of this problem by not accepting
> messages that you cannot deliver. Use "Recipient Filtering". See this
> KB article:
> How to configure connection filtering to use Realtime Block Lists
> (RBLs) and how to configure recipient filtering in Exchange 2003
> [823866]
>
> If you have nothing else, install and use the Intellegent Mail Filter
> (IMF) as a spam filter, too.
>
>
>
>
>
> >Thank you in advance for all of your help.
> >Brian
> >
> >"Rich Matheisen [MVP]" wrote:
> >
> >> BrianW <BrianW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> >>
> >> >The majority of the entries with 'Retry' say "The connection was dropped by
> >> >the remote host." There are also some entries that say "The remote server
> >> >did not respond to a connection attempt." and "An SMTP protocol error
> >> >occurred."
> >>
> >> That doesn't sound like an Exchange problem. It sounds more like a
> >> network problem.
> >>
> >> What version of the O/S are you running? Is it Windows 2003? Have you
> >> installed SP1?
> >>
> >> If you've installed SP1, try reducing the MTU size on the NIC on the
> >> Exchange server to something like 1200. If that fixes the problem call
> >> MS and get the hotfix for the tcpip.sys driver. the "broken" driver
> >> (part of MS05-019) was delivered with SP1.
> >>
> >> Even if you're not running SP1 or Windows 2003, try rducing the MTU
> >> size.
> >>
> >> Try a simple (not 100% definitive) test:
> >>
> >> ping -f -l 1472 <target-address>
> >>
> >> That should work (using 1473 should fail). If 1472 fails, keep
> >> reducing the value until you find one that works reliably. Then set
> >> the MTU size to something a bit smaller.
> >>
> >> --
> >> Rich Matheisen
> >> MCSE+I, Exchange MVP
> >> MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
> >> Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
> >>
>
>
> --
> Rich Matheisen
> MCSE+I, Exchange MVP
> MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
> Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
>
.