Software

Ask something
Discussion Locked

Delivery Status Notification (Delay)

0 helpful
6 replies

by jplace

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are running a Win 2000 Server (SP4) with Exchange 2000 (SP3). Anti Virus software is by Trend and the anti Spam is GFI mailEssentials. I am getting delivery status notification (delay) errors on three particular domains that we send to. I have done the usual nslookup and then attempt to ping the mail server you get details of but I am unable to ping these particular servers either by DNS or IP. I am also unable to telnet onto these servers. I ran the same tests on known OK addresses and got through first time. All messages are currently being CC'd to alternaive private mail accounts (e.g. hotmail) and these get through fine. I've had a trawl through the FAQ's etc here and read Comment from mrwilde Date: 07/05/2004 04:38PM PDT which has helped get me to the point where I am now. My instinct tells me that our server is fine but I'm not 100% sure. Is there anyone out there who can assist?

6 replies

by bfilmfan

The domains which you cannot deliver mail to are hosted on your server or one someone else's server?

If someone hosts the domain and you cannot ping it via IP or name, the issue is with DNS and nost likely on their end, since you said your system otherwise is delivering mail.

by jplace

The domains to which I cannot delivery mail are hosted on someone else's server. I now have five that I can't send to (well, I can send but it takes at least couple of hours to get there and the message also sits in the SMTP queue until it times out.) This problem looks like its getting bigger....
Help!

by rickdavey

Not sure if jplace@... will get a notice of this, but wondered if you got this solved. We are having a similar problem with a few domains as well.
Thanks in advance.

by paulkoppen

Did anyone ever find the reason for this issue?
I'm having the same problem with a single Domain.

I'm running SBS 2003 Exchange, no problems delivering to anyone else. Everything on my side has been boiled over and optimized for months to try and resolve this - most typical DNS and Exchange mods reviewed or applied, but nothing altered the activity. I never found anything that would explain it or was in any way "incorrect" in the first place.

I'm 99% sure it's their Barracuda Spam Filter - it only delay/blocks email with attachments, it holds open an SMTP connection on those until it times out after a few hours, then sends mail without attachments that backed up behind the others. The attachment email kick back, clog the queue until they time out again.

The company with the Spam Filter is not pursuing a solution with Barracuda. They were told update and patch the Spam filter and call us back, but they've chosen not to update it.

I have no idea if there's anything I can do as a work around on my side, as I have no idea why it's happening.

Paul

by rickdavey

Paul,
I did not hear from jplace, but our problem turned out to be our web filter solution (SurfControl).
I created a new rule that allowed our Exchange server to have wide open access to port 25 and all is well now.
The problem stems from another rule that disallows all users access to web-based email (ie: hotmail), hence our server was also disallowed.

Hope this helps.
Rick

This discussion is closed to new replies.