JanVorster
ISP
Hi all,
I've got a Win2K Server machine that is used as a web server and it sends out emails, never really receives anything. I'm just relying on the IIS to send out the email, my IIS version is 5.0.2195.6713.
On Fridays we send out a newsletter to our subscribers (approx 17,000), but lately we've been having great hassles with this. The mail isn't going out as fast as it has done in the past, and now we have a mailroot\queue folder that countains 7,000 messages and it seems at times that new messages can't be delivered until some of the older messages in the queue have baan delivered. Kind of like a Last-In-Last-Out scenario.
Another one of the symptoms is that some addresses that receive email on a frequent basis fails to be delivered. For instance, an address that gets on average 100 mails per day will have a failure rate of approx 10%.
Here's some of the settings as can be found on the Delivery options tab of the "Default SMTP Virtual Server Properties" (in IIS on my Win2K Server machine).
Outbound:
First retry interval : 20min
Second retry interval : 20min
Third rettry interval : 20min
Subsequent retry interval : 120min
Delay notification : 4 hours
Expiration timeout : 3 days
Under "Advanced"
Maximum hop count : 120
Masquerade domain:
cyberprop.com - this is our main domain and most outgoing email is from something@cyberprop.com. The A-record for this domain is the same as the machine's IP address. (The MX record is not the same...)
Fully-qualified domain name:
usp.onsite.hosting.co.za - the IP address that this resolves to is also the same as the machine's IP address.
Any ideas?
Smart host:
[196.7.147.10] - this is tha same as the MX record for the masquerade domain, cyberprop.com
Thanks!
Jan
I've got a Win2K Server machine that is used as a web server and it sends out emails, never really receives anything. I'm just relying on the IIS to send out the email, my IIS version is 5.0.2195.6713.
On Fridays we send out a newsletter to our subscribers (approx 17,000), but lately we've been having great hassles with this. The mail isn't going out as fast as it has done in the past, and now we have a mailroot\queue folder that countains 7,000 messages and it seems at times that new messages can't be delivered until some of the older messages in the queue have baan delivered. Kind of like a Last-In-Last-Out scenario.
Another one of the symptoms is that some addresses that receive email on a frequent basis fails to be delivered. For instance, an address that gets on average 100 mails per day will have a failure rate of approx 10%.
Here's some of the settings as can be found on the Delivery options tab of the "Default SMTP Virtual Server Properties" (in IIS on my Win2K Server machine).
Outbound:
First retry interval : 20min
Second retry interval : 20min
Third rettry interval : 20min
Subsequent retry interval : 120min
Delay notification : 4 hours
Expiration timeout : 3 days
Under "Advanced"
Maximum hop count : 120
Masquerade domain:
cyberprop.com - this is our main domain and most outgoing email is from something@cyberprop.com. The A-record for this domain is the same as the machine's IP address. (The MX record is not the same...)
Fully-qualified domain name:
usp.onsite.hosting.co.za - the IP address that this resolves to is also the same as the machine's IP address.
Any ideas?
Smart host:
[196.7.147.10] - this is tha same as the MX record for the masquerade domain, cyberprop.com
Thanks!
Jan