Jump to content

Recommended Posts

Posted

Hi there,

 

yesterday Exchange decided not to accept incoming messages (from www) and internally, messages are just sitting in the queue.

 

Looking at the messages in the queue, the error column has 250.2.0.0 OK in it next to messages!?!

 

Also I have asked our spam filtering poeple if they can see anything and they sent me the following info:

 

Jun 7 17:50:00 spamwall/smtp[40486]: 2BFB7250E83: to=, relay=81.134.202.35[81.134.202.35], delay=9383, status=deferred (host 81.134.202.35[81.134.202.35] refused to talk to me: 421 The server has reached the maximum number of threads allowed)

 

We had a similar issue about 6 weeks ago that was down to an an issue with AV but after replicating the fix, AV doesn't appear to be the problem now!

 

Anyone any ideas.

 

Thanks in antisipation.

Posted

1. Which queues are the messages in ?

2. Is the issue ONLY with external>internal or internal>external or internal>internal?

  • Thanks 1
Posted

Thanks for the posts.

 

It was indeed a disk space issue which was discovered when I eventually remoted in at around 2pm.

 

official thanks will be added to posts when I get on a pc later.

 

Cheers

Posted
1. Which queues are the messages in ?

2. Is the issue ONLY with external>internal or internal>external or internal>internal?

 

Hi,

 

the issue was effecting external>internal and internal>internal.

 

Thanks

Posted
Can the Exchange cert have anything to do with this? And does the HDD with your exchange db on it have enough space?

 

Space was the issue.

 

Thanks

Posted
Eventvwr saying anything? have you used exchange toolbox? I can remote in to help if needed

 

Event viewer said bugger all to be honest which surprised me somewhat.

Posted

No it was the log files.

 

I don't normally have anything to do with the Exchange setup but it turns out that the guy responsible for it hasn't been backing things up so the logs just grew. (and grew and grew and grew)

 

Anyway whilst remoting in earlier I deleted the logs and then made sure that the backups were all set to go etc.

Posted
No it was the log files.

 

I don't normally have anything to do with the Exchange setup but it turns out that the guy responsible for it hasn't been backing things up so the logs just grew. (and grew and grew and grew)

 

Anyway whilst remoting in earlier I deleted the logs and then made sure that the backups were all set to go etc.

 

I had log file issues (Not backup related) I d just keep an eye for next few days if increases again

  • Thanks 1
Posted
now that you have deleted the logs, make sure the type of backup you run is full and not any other type, this will fail. After the full backup you may if you wish use incrementals.
Posted
now that you have deleted the logs, make sure the type of backup you run is full and not any other type, this will fail. After the full backup you may if you wish use incrementals.

 

Thanks Sukh. We use BackupAssist and I have a full backup going through as we speak.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...