Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 832
  • Last Modified:

Mail Queues get backed up

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
twanderson
Asked:
twanderson
  • 9
  • 8
1 Solution
 
Barry GillChief of StaffCommented:
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
 
twandersonAuthor Commented:
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
 
Barry GillChief of StaffCommented:
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
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
twandersonAuthor Commented:
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
 
Barry GillChief of StaffCommented:
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
 
twandersonAuthor Commented:
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
 
twandersonAuthor Commented:
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
 
Barry GillChief of StaffCommented:
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
 
twandersonAuthor Commented:
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
 
Barry GillChief of StaffCommented:
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
 
twandersonAuthor Commented:
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
 
Barry GillChief of StaffCommented:
have you tried routing directly?
0
 
twandersonAuthor Commented:
Not sure what you mean?
0
 
Barry GillChief of StaffCommented:
delivering direct from exchange, bypassing mimesweeper
0
 
twandersonAuthor Commented:
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
 
Barry GillChief of StaffCommented:
As I said - I suspected DNS issues from the start :)
Glad you have it working!
0
 
twandersonAuthor Commented:
Worked with vendor and got the issue resolved.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 9
  • 8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now