all groups > iis smtp nntp > october 2007 >
You're in the

iis smtp nntp

group:

No Delivery Status Notifications in IIS 5 Virtual Server?


No Delivery Status Notifications in IIS 5 Virtual Server? rich lockney
10/24/2007 7:32:53 PM
iis smtp nntp:
Hi,

A minor annoyance, but something I cannot quite figure out... Where I
am, we have a local SMTP server for our outgoing mail, set up on a
Win2k machine, via a virtual server in IIS5. For a while, we'd get
Delivery Status Notifications, either for a delay or failure in
delivery. For some reason, we don't get them any more, yet there is
still the occasional problem mail (user no longer exists at the remote
host, delay in sending, etc.), as entries *are* being logged to System
Events from time to time.

Is there a setting I am overlooking to control whether or not Delivery
Status Notifications are sent from the server? I've set it up to
forward NDRs to a specified address, but it doesn't look like any are
being generated / there is never anything in the BadMail folder.

Any insight appreciated -- thanks!

PS - Apologies for the cross-post, but I noticed that the general IIS
group gets a little more traffic than the .iis.smtp_nntp one, and it's
not entirely out of scope...
Re: No Delivery Status Notifications in IIS 5 Virtual Server? Sanford Whiteman
10/26/2007 1:33:55 AM
[quoted text, click to view]

I'd say "no NDRs" is more than a minor annoyance.

It sounds from your description like a corrupt VS config; there is no
GUI-configured way to disable NDRs completely. My recommendation is to
create a second VS for testing; default setup for fresh VSs is of
course to send from postmaster@<Local_Default_Domain>. Move everything
over to that VS after verifying.

--Sandy



------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
Re: No Delivery Status Notifications in IIS 5 Virtual Server? rich lockney
10/26/2007 7:23:41 PM
[quoted text, click to view]

Thanks for the reply. A new VS was pretty much next (last) course of
action on the list. I was hoping that there was some fix I had
overlooked / wasn't readily apparent. Looks like I did exhaust my
options, and new VS is the way to go.

Thanks again,

Rich
AddThis Social Bookmark Button