Solved

Mail Queues get backed up

Posted on 2010-11-19
17
812 Views
Last Modified: 2012-05-10
We are getting the following error message several times a day and what we need to do is flush the DNS on the server and retry delivery and it then sends them out. We use Mimesweeper for SMTP and this is were the QUEUES are getting backed up and where we have to flush the DNS and restart the infastructure service. My question is this something wrong with the mimesweeper server or is this a general DNS issue. I have talked with Mimesweeper and we get mixed reviews on if it is a mimesweeper issue or a DNS issue. Just hope someone else out there can shed some light on this problem.

            The e-mail system was unable to deliver the message, but did not report a specific reason.  Check the address and try again.  If it still fails, contact your system administrator.
            < SERVERNAME.DOMAIN.com #5.0.0 smtp; 550-mail.scc-inc.com (SERVERNAME.DOMAIN.com) :2261 is currently    not 550-permitted to relay through this server. Perhaps you have not logged into 550-the pop/imap    server in the last 30 minutes or do not have SMTP 550 Authentication turned on in your email    client.>
0
Comment
Question by:twanderson
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 9
  • 8
17 Comments
 
LVL 9

Expert Comment

by:Barry Gill
ID: 34172978
is it always with the same recipient domain?
how quickly do the queues build?
is other stuff being delivered around these ones that are halting?
Do they always get delivered post restart/flush?
0
 

Author Comment

by:twanderson
ID: 34173021
It seems to get backed up on Yahoo, hotmail and aol the most.
Not to fast, so some seem to get through, some seem to get stuck and others get non delivered
No, the flush does not always work. Sometimes we have to do this step several times.
0
 
LVL 9

Expert Comment

by:Barry Gill
ID: 34173276
ok, then I think it unlikely that this is a problem at the remote side.
I am inclined to start investigations at the DNS side of things as flush clears out your dns and forces a fresh lookup of required domains and a restart of services simply forces queued items to be retried.

What DNS server is your mailsweeper pointing to? Internal or ISP?

Also, are ALL of the queued items to every provider giving you this same delivery failure message?
 
SERVERNAME.DOMAIN.com #5.0.0 smtp;
550-mail.scc-inc.com (SERVERNAME.DOMAIN.com) :2261 is currently    not
550-permitted to relay through this server. Perhaps you have not logged into
550-the pop/imap    server in the last 30 minutes or do not have SMTP
550 Authentication turned on in your email    client.>

The reason I ask is that this is a 550 error. Permanent Fatal. These items should never be re-queued - they should bounce and that is the end of it. (I would assume this is one isolated case and perhaps not the best representation of what is happening in the queue :( )
0
Forrester Webinar: xMatters Delivers 261% ROI

Guest speaker Dean Davison, Forrester Principal Consultant, explains how a Fortune 500 communication company using xMatters found these results: Achieved a 261% ROI, Experienced $753,280 in net present value benefits over 3 years and Reduced MTTR by 91% for tier 1 incidents.

 

Author Comment

by:twanderson
ID: 34173316
Currently mailsweeper is pointed primary to ISP and secondary to one of our nameservers.

No the messages getting queued eventually go through, but we also get the undeliverable messages during this same time for other messages. So it appears some go through, some get stuck and some get undeliverable.
0
 
LVL 9

Expert Comment

by:Barry Gill
ID: 34173452
I would start by pointing primary and secondary to your name servers. That way you can access logs of what is being returned to mimesweeper much easier.
it is normal for messages to behave in this manner, sometimes however when you do have a real problem the normal operation problems throw lots of red herrings your way :(

Ok, I think anything that gets a fatal should be ignored (unless your users are resending the same mail and that is getting delivered)

Just a note - the scc-inc error you posted has SERVERNAME.DOMAIN.com as the reporting server. Is this YOUR server (mimesweeper or Exchange) that you have sanitised?

0
 

Author Comment

by:twanderson
ID: 34173501
What do you think about doing a DNS Flush on our primary and secondary nameservers? This was a suggestion from mimesweeper, but I am not a DNS expert by any means and I am not sure what problems this may cause except websites taking a little longer to come up the first time.
0
 

Author Comment

by:twanderson
ID: 34173511
Oh and I wanted to answer your last post about the fatal messages being ignored. Yes after we flush the DNS on mimesweeper if the user retry the undeliverable message it will go through then.
0
 
LVL 9

Expert Comment

by:Barry Gill
ID: 34173564
flush on your dns would have no adverse affect on your environment unless you were serving multithousands of users/requests.

But point your mimesweeper to your dns before doing that

so there reason I asked about the servername was if these messages are being bounced by your mimesweeper box, perhaps you need to switch off relay after pop services... (smtp after pop - not sure if that is available in your version of mimesweeper...)
0
 

Author Comment

by:twanderson
ID: 34174303
I performed the Clear cache on both nameservers and then performed a flushdns on mailsweeper, I then restarted the server. The Queues are still backing up.
0
 
LVL 9

Expert Comment

by:Barry Gill
ID: 34174392
Please answer these:
Just a note - the scc-inc error you posted has SERVERNAME.DOMAIN.com as the reporting server. Is this YOUR server (mimesweeper or Exchange) that you have sanitised?

and

Does your mimesweeper ahev logs you can post for failed attempts?

and

are you using mimesweeper edge or appliance?


0
 

Author Comment

by:twanderson
ID: 34174424
The scc-inc error was from the mimesweeper server.

Yes, there are logs and they have been sent to mimesweeper.

we are using mimesweeper 5.4 for SMTP, runs on HP Server. No Edge or appliance.
0
 
LVL 9

Expert Comment

by:Barry Gill
ID: 34174510
have you tried routing directly?
0
 

Author Comment

by:twanderson
ID: 34175421
Not sure what you mean?
0
 
LVL 9

Expert Comment

by:Barry Gill
ID: 34177246
delivering direct from exchange, bypassing mimesweeper
0
 

Accepted Solution

by:
twanderson earned 0 total points
ID: 34187295
Thank you Barrulus. We got it working, it appears that it was an issue with our DNS Servers. We redirected Mimesweeper to use difrent DNS servers and all is working properly now. Thanks for your help.
0
 
LVL 9

Expert Comment

by:Barry Gill
ID: 34187311
As I said - I suspected DNS issues from the start :)
Glad you have it working!
0
 

Author Closing Comment

by:twanderson
ID: 34221146
Worked with vendor and got the issue resolved.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Moving on from sbs 2008... 36 86
Exchange 2013 - Outlook 2013 clients lagging 2 36
exchange, squid, proxy, linux 6 43
Removing Exchange 2003 3 17
Resolve DNS query failed errors for Exchange
This article explains how to install and use the NTBackup utility that comes with Windows Server.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question