We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

How to REMOVE SUSPENDED QUEUE from EXCHANGE 2010?

Medium Priority
7,002 Views
Last Modified: 2012-05-11
Hello,

Due to Open Riley, our Exchange Server 2010 Queue is filled with lot of SPAM messages. I'm able to SUSPEND all the QUEUE, but Can't Remove those.

When I select ALL, it DIDN'T GAVE ME ANY OPTION TO REMOVE ALL AT ONCE

Is there any command to remove all suspended queue from Exchange 2010 at once?

Thanks.
Comment
Watch Question

Technical Manager
CERTIFIED EXPERT
Top Expert 2010
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Shreedhar EtteTechnical Manager
CERTIFIED EXPERT
Top Expert 2010

Commented:

Author

Commented:
It's look like something went wrong...I can't even receive Incoming emails from outside domains...BUT I send e-mails to outside domains.... (i.e. Gmail)

I verified even both Client and Default Receive Connectors.... Everything is Same
Shreedhar EtteTechnical Manager
CERTIFIED EXPERT
Top Expert 2010

Commented:
Restart the Exchange Trasport Service and check.

Author

Commented:
I restarted the Exchange Server... Same...

I tested Inbound SMTP using testexchangeconnectivity.com website. Here is the error message:
--------------------------------------------------------------
Attempting to send a test e-mail message to xxxxx@mydomain.com using MX mail.mydomain.com.
       Delivery of the test message failed.
       
      Additional Details
       The server returned status code 421 - Service not available, closing transmission channel. The server response was: 4.4.1 Connection timed out
Exception details:
Message: Service not available, closing transmission channel. The server response was: 4.4.1 Connection timed out
Type: System.Net.Mail.SmtpException
Stack trace:
at System.Net.Mail.SmtpConnection.GetConnection(String host, Int32 port)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()
------------------------------------------------------------------
Shreedhar EtteTechnical Manager
CERTIFIED EXPERT
Top Expert 2010

Commented:
Go to tools and run Exchange Best Practise analyser tool and see there are any errors pointing to connectors.

Author

Commented:
Well,

I'm receiving this error message again and again:
Connecting to remote server failed with the following error message: The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.

(https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26977070.html)

ACTUALLY I CONTACT MICROSOFT SUPPORT REGARDING ABOVE ERROR AND THEY FIXED IT. BU SUDDENLY IT STARTS SHOWING THE SAME ERROR MESSAGE AND EVENTUALLY THE TRANSPORT SERVICE WON'T RESPOND.

When I try to restart the Transport service, it stopped automatically.
Shreedhar EtteTechnical Manager
CERTIFIED EXPERT
Top Expert 2010

Commented:
- You are doing many things simaltaniously. You do changes one at a time and wait for some time for the changes to take effect.

- Make sure the IPv6 is enabled on the NIC. If it is not enabled, enable it and reboot the server.

Author

Commented:
Okay.

I restarted the server again. And I ran the Best Practices analyzer and it's found any issues.
BUT, I ran Exchange Mail Acceptance Test and it shows two error messages in SMTP:

Error submitting mail
Mail submission failed: Error message: The SMTP host was not specified.

Any idea on this?
Shreedhar EtteTechnical Manager
CERTIFIED EXPERT
Top Expert 2010

Commented:
Does the Send Connector is created on the server?

Are you able to telnet the exchange server on port 25?

Author

Commented:
Yes, Send Connector is already created and enabled.
I telnet the port 25 and it's responding. I shows Microsoft ESMTP Service is ready...

We are able to:
# Receive & Send Emails to Internally
# Send Emails to External Domains
### CAN NOT RECEIVE E-MAIL from External Domains. There is no queue e-mails at this time.
Shreedhar EtteTechnical Manager
CERTIFIED EXPERT
Top Expert 2010

Commented:
Ok,

Where does you mx record pointing. Does it is pointing to your exchange server?

Are you able to telnet public ip address of exchange server on port 25?

Author

Commented:
MX record points to Exchange Server correctly. Also I telnet the port 25 again with the public IP address. It's shows the same success message "Microsoft ESMTP service is ready".

I tested Inbound SMTP using testexchangeconnectivity.com website. Here is the error message:
--------------------------------------------------------------
Attempting to send a test e-mail message to xxxxx@mydomain.com using MX mail.mydomain.com.
       Delivery of the test message failed.
       
      Additional Details
       The server returned status code 421 - Service not available, closing transmission channel. The server response was: 4.4.1 Connection timed out
Exception details:
Message: Service not available, closing transmission channel. The server response was: 4.4.1 Connection timed out
Type: System.Net.Mail.SmtpException
Stack trace:
at System.Net.Mail.SmtpConnection.GetConnection(String host, Int32 port)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()
Shreedhar EtteTechnical Manager
CERTIFIED EXPERT
Top Expert 2010

Commented:
Disable integrated spam filters of the Exchange 2010. Then restart the Exchange Trasport services. After that run the Ibound mail test.

Author

Commented:
How can I do that?
Shreedhar EtteTechnical Manager
CERTIFIED EXPERT
Top Expert 2010

Commented:
Also execute:
Set-receiveconnector -identify "your receiveConnector" -connectiontimeout:00:30:00

Author

Commented:
When I run that command, I received this error message:

VERBOSE: Connecting to exchange2.domain.local
VERBOSE: Connected to exchange2.domain.local.
[PS] C:\Windows\system32>Set-receiveconnector -identify "Default EXCHANGE2" -connectiontimeout:00:30:00
A positional parameter cannot be found that accepts argument 'Default EXCHANGE2'.
    + CategoryInfo          : InvalidArgument: (:) [Set-ReceiveConnector], ParameterBindingException
    + FullyQualifiedErrorId : PositionalParameterNotFound,Set-ReceiveConnector

Author

Commented:
HURRY!

I added FQDN field with: exchange2.domain.local in Client EXCHANGE2 Receive Connector and then restarted both System Attendant and Transport services.

I'm receiving new e-mails not old one!!!

Author

Commented:
TESTEXCHANGECONNECTIVITY.com Inbound SMTP TEST SUCCESSFULL!
Shreedhar EtteTechnical Manager
CERTIFIED EXPERT
Top Expert 2010

Commented:
That's good.
Shreedhar EtteTechnical Manager
CERTIFIED EXPERT
Top Expert 2010

Commented:
As the issue resolved accept one of the comment as answer.

Author

Commented:
Solution:

Extend Receive Connector Time-Out:
Set-receiveconnector -identify "your receiveConnector" -connectiontimeout:00:30:00

Do this for both Client and Default Receive Connectors.
------------------------------------------------------------------
Restart these services:
System Attendeant
Transport
Mailbox Replication
Replication

Then go to to testexchangeconnectivity.com and do the both Inbound and Outbound SMTP tests. If everything is green, you are okay to relax!
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.