RE: Delivery Attempt Standard
I pay for a similar service from dyndns.org called mailhop backup mx - about $40 per year. They will store your messages and attempt to deliver them to your mail server for up to 10 days. Ralph -Original Message- From: Dave Wade [mailto:dave.w...@stockport.gov.uk] Sent: Monday, October 04, 2010 9:22 AM To: MS-Exchange Admin Issues Subject: RE: Delivery Attempt Standard Our ISP provides a staging server that's pointed to by lower priority MX records and which holds the e-mail if there are any issues with our servers. Not sure how long for, but presumably it can be tweaked on request... Dave Wade -Original Message- From: Kurt Buff [mailto:kurt.b...@gmail.com] Sent: 04 October 2010 14:17 To: MS-Exchange Admin Issues Subject: Re: Delivery Attempt Standard 5 days. On Mon, Oct 4, 2010 at 05:41, James Kerr cluster...@gmail.com wrote: Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist ** Cut Carbon, Save Money, Save the Environment. Take the climate challenge and reduce your carbon footprint at www.stockport.gov.uk/carboff This email, and any files transmitted with it, is confidential and intended solely for the use of the individual or entity to whom they are addressed. As a public body, the Council may be required to disclose this email, or any response to it, under the Freedom of Information Act 2000, unless the information in it is covered by one of the exemptions in the Act. If you receive this email in error please notify Stockport ICT, Business Services via email.qu...@stockport.gov.uk and then permanently remove it from your system. Thank you. http://www.stockport.gov.uk ** --- To manage subscriptions click here: http://lyris.sunbelt- software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist Confidentiality Notice: -- This communication, including any attachments, may contain confidential information and is intended only for the individual or entity to whom it is addressed. Any review, dissemination, or copying of this communication by anyone other than the intended recipient is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email, delete and destroy all copies of the original message. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Delivery Attempt Standard
Yeah, well, “back in the day” (granted, this is pre-historic for most of y’all) it took 3 days for an email to cross from the east coast of the US to the west coast of the US; as it would transit nine or ten different email systems – usually via dial-up. So…that’s the historical basis. I agree that in today’s well-connected networks, that five days is far too long. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Hutchings [mailto:paul.hutchi...@mira.co.uk] Sent: Monday, October 04, 2010 9:02 AM To: MS-Exchange Admin Issues Subject: RE: Delivery Attempt Standard It really does vary. Personally I prefer a shorter time period as if you send a message you typically want to know if it has (or hasn’t) been sent, not have it sat in a queue for 5 days (I’ve seen plenty of systems set to 120 hours or 5 days or what seems a stupidly high period of time). From: James Kerr [mailto:cluster...@gmail.com] Sent: 04 October 2010 13:41 To: MS-Exchange Admin Issues Subject: Delivery Attempt Standard Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist MIRA Ltd Watling Street, Nuneaton, Warwickshire, CV10 0TU, England Registered in England and Wales No. 402570 VAT Registration GB 114 5409 96 The contents of this e-mail are confidential and are solely for the use of the intended recipient. If you receive this e-mail in error, please delete it and notify us either by e-mail, telephone or fax. You should not copy, forward or otherwise disclose the content of the e-mail as this is prohibited. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Delivery Attempt Standard
We have ours set to 3 days I believe specifically to try to allow for weekend issues like this without getting into the stupid 4-5 day range. At least those whose attempted sends failed should have received delivery failure messages and can try again manually if they care. --- [Sent from my BlackBerry - please excuse spelling/grammar] From: James Kerr cluster...@gmail.com To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Mon Oct 04 07:02:01 2010 Subject: Re: Delivery Attempt Standard Ok, so it looks like we're going to be missing some email then. C'est la vie, it is what it is. Thanks, James - Original Message - From: Michael B. Smithmailto:mich...@smithcons.com To: MS-Exchange Admin Issuesmailto:exchangelist@lyris.sunbelt-software.com Sent: Monday, October 04, 2010 8:54 AM Subject: RE: Delivery Attempt Standard Depends on the mail server. For Exchange, it’s 48 hours. For sendmail, it used to be 72 hours. Can’t speak to any others. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Jonathan Link [mailto:jonathan.l...@gmail.com] Sent: Monday, October 04, 2010 8:49 AM To: MS-Exchange Admin Issues Subject: Re: Delivery Attempt Standard For some reason 24 hours is sticking in my mind... I can't seem to find documentation to that right now, though. On Mon, Oct 4, 2010 at 8:41 AM, James Kerr cluster...@gmail.commailto:cluster...@gmail.com wrote: Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Delivery Attempt Standard
For some reason 24 hours is sticking in my mind... I can't seem to find documentation to that right now, though. On Mon, Oct 4, 2010 at 8:41 AM, James Kerr cluster...@gmail.com wrote: Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Delivery Attempt Standard
Depends on the mail server. For Exchange, it's 48 hours. For sendmail, it used to be 72 hours. Can't speak to any others. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Jonathan Link [mailto:jonathan.l...@gmail.com] Sent: Monday, October 04, 2010 8:49 AM To: MS-Exchange Admin Issues Subject: Re: Delivery Attempt Standard For some reason 24 hours is sticking in my mind... I can't seem to find documentation to that right now, though. On Mon, Oct 4, 2010 at 8:41 AM, James Kerr cluster...@gmail.commailto:cluster...@gmail.com wrote: Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Delivery Attempt Standard
Our ISP provides a staging server that's pointed to by lower priority MX records and which holds the e-mail if there are any issues with our servers. Not sure how long for, but presumably it can be tweaked on request... Dave Wade -Original Message- From: Kurt Buff [mailto:kurt.b...@gmail.com] Sent: 04 October 2010 14:17 To: MS-Exchange Admin Issues Subject: Re: Delivery Attempt Standard 5 days. On Mon, Oct 4, 2010 at 05:41, James Kerr cluster...@gmail.com wrote: Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist ** Cut Carbon, Save Money, Save the Environment. Take the climate challenge and reduce your carbon footprint at www.stockport.gov.uk/carboff This email, and any files transmitted with it, is confidential and intended solely for the use of the individual or entity to whom they are addressed. As a public body, the Council may be required to disclose this email, or any response to it, under the Freedom of Information Act 2000, unless the information in it is covered by one of the exemptions in the Act. If you receive this email in error please notify Stockport ICT, Business Services via email.qu...@stockport.gov.uk and then permanently remove it from your system. Thank you. http://www.stockport.gov.uk ** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Delivery Attempt Standard
5 days isn't too long, IMHO. For exactly the kind of reasons the OP encountered. On Mon, Oct 4, 2010 at 06:06, Michael B. Smith mich...@smithcons.com wrote: Yeah, well, “back in the day” (granted, this is pre-historic for most of y’all) it took 3 days for an email to cross from the east coast of the US to the west coast of the US; as it would transit nine or ten different email systems – usually via dial-up. So…that’s the historical basis. I agree that in today’s well-connected networks, that five days is far too long. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Hutchings [mailto:paul.hutchi...@mira.co.uk] Sent: Monday, October 04, 2010 9:02 AM To: MS-Exchange Admin Issues Subject: RE: Delivery Attempt Standard It really does vary. Personally I prefer a shorter time period as if you send a message you typically want to know if it has (or hasn’t) been sent, not have it sat in a queue for 5 days (I’ve seen plenty of systems set to 120 hours or 5 days or what seems a stupidly high period of time). From: James Kerr [mailto:cluster...@gmail.com] Sent: 04 October 2010 13:41 To: MS-Exchange Admin Issues Subject: Delivery Attempt Standard Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist MIRA Ltd Watling Street, Nuneaton, Warwickshire, CV10 0TU, England Registered in England and Wales No. 402570 VAT Registration GB 114 5409 96 The contents of this e-mail are confidential and are solely for the use of the intended recipient. If you receive this e-mail in error, please delete it and notify us either by e-mail, telephone or fax. You should not copy, forward or otherwise disclose the content of the e-mail as this is prohibited. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Delivery Attempt Standard
5 days. On Mon, Oct 4, 2010 at 05:41, James Kerr cluster...@gmail.com wrote: Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Delivery Attempt Standard
As others have noted it varies widely, but remote sites will usually try to deliver for at least a day or two before giving up. W/o looking I'm pretty confident at least one RFC recommends 3 days as reasonable but it's definitely not adhered to in all cases. If you feel/know there is some mail that is expected from biz partners etc..., research the etrn command. You could telnet to the remote site and try that command against the server so they retry delivery to you. ~JasonG -Original Message- From: James Kerr [mailto:cluster...@gmail.com] Sent: Monday, October 04, 2010 08:41 To: MS-Exchange Admin Issues Subject: Delivery Attempt Standard Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt- software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Delivery Attempt Standard
I always thought that it was 72 hours and that because our server came online before the 72 hours had expired, I was expecting a bunch of mail to flow but I was wrong. Times have changed I've discovered. Well, more reason for facilities to get the backup AC system working as a backup AC. Having it run of the same cooling tower as all the other air handlers hardly seems like a great idea considering most of the reasons the AC has been broke recently has got something to do with the tower. James - Original Message - From: Jason Gurtz jasongu...@npumail.com To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Monday, October 04, 2010 1:06 PM Subject: RE: Delivery Attempt Standard As others have noted it varies widely, but remote sites will usually try to deliver for at least a day or two before giving up. W/o looking I'm pretty confident at least one RFC recommends 3 days as reasonable but it's definitely not adhered to in all cases. If you feel/know there is some mail that is expected from biz partners etc..., research the etrn command. You could telnet to the remote site and try that command against the server so they retry delivery to you. ~JasonG -Original Message- From: James Kerr [mailto:cluster...@gmail.com] Sent: Monday, October 04, 2010 08:41 To: MS-Exchange Admin Issues Subject: Delivery Attempt Standard Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt- software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Delivery Attempt Standard
There is no real standard, other than the standards that the software vendor uses for their own products. 24-72 hours typically as other people have indicated. -- ME2 On Mon, Oct 4, 2010 at 5:41 AM, James Kerr cluster...@gmail.com wrote: Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Delivery Attempt Standard
I've seen 72 hours, but I always change mine down to 24, with warnings kicking off within an hour. I want myself and my users to know about communications problems in a much more timely fashion. -- ME2 On Mon, Oct 4, 2010 at 10:54 AM, James Kerr cluster...@gmail.com wrote: I always thought that it was 72 hours and that because our server came online before the 72 hours had expired, I was expecting a bunch of mail to flow but I was wrong. Times have changed I've discovered. Well, more reason for facilities to get the backup AC system working as a backup AC. Having it run of the same cooling tower as all the other air handlers hardly seems like a great idea considering most of the reasons the AC has been broke recently has got something to do with the tower. James - Original Message - From: Jason Gurtz jasongu...@npumail.com To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Monday, October 04, 2010 1:06 PM Subject: RE: Delivery Attempt Standard As others have noted it varies widely, but remote sites will usually try to deliver for at least a day or two before giving up. W/o looking I'm pretty confident at least one RFC recommends 3 days as reasonable but it's definitely not adhered to in all cases. If you feel/know there is some mail that is expected from biz partners etc..., research the etrn command. You could telnet to the remote site and try that command against the server so they retry delivery to you. ~JasonG -Original Message- From: James Kerr [mailto:cluster...@gmail.com] Sent: Monday, October 04, 2010 08:41 To: MS-Exchange Admin Issues Subject: Delivery Attempt Standard Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt- software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Delivery Attempt Standard
That's what delay warnings are for. On Mon, Oct 4, 2010 at 11:55, Micheal Espinola Jr michealespin...@gmail.com wrote: I've seen 72 hours, but I always change mine down to 24, with warnings kicking off within an hour. I want myself and my users to know about communications problems in a much more timely fashion. -- ME2 On Mon, Oct 4, 2010 at 10:54 AM, James Kerr cluster...@gmail.com wrote: I always thought that it was 72 hours and that because our server came online before the 72 hours had expired, I was expecting a bunch of mail to flow but I was wrong. Times have changed I've discovered. Well, more reason for facilities to get the backup AC system working as a backup AC. Having it run of the same cooling tower as all the other air handlers hardly seems like a great idea considering most of the reasons the AC has been broke recently has got something to do with the tower. James - Original Message - From: Jason Gurtz jasongu...@npumail.com To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Monday, October 04, 2010 1:06 PM Subject: RE: Delivery Attempt Standard As others have noted it varies widely, but remote sites will usually try to deliver for at least a day or two before giving up. W/o looking I'm pretty confident at least one RFC recommends 3 days as reasonable but it's definitely not adhered to in all cases. If you feel/know there is some mail that is expected from biz partners etc..., research the etrn command. You could telnet to the remote site and try that command against the server so they retry delivery to you. ~JasonG -Original Message- From: James Kerr [mailto:cluster...@gmail.com] Sent: Monday, October 04, 2010 08:41 To: MS-Exchange Admin Issues Subject: Delivery Attempt Standard Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt- software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Delivery Attempt Standard
Surely. What Im getting at is an overall reduction in all the timers - especially the final failure. I have worked in a number of places where the defaults were not only problematic, but attributed to measurable loss in productivity. Of course it always depends on your environment and your overall user skill levels. I find users dont understand the concept of delays unless really beaten into them. But failures; they get. -- ME2 On Mon, Oct 4, 2010 at 12:26 PM, Kurt Buff kurt.b...@gmail.com wrote: That's what delay warnings are for. On Mon, Oct 4, 2010 at 11:55, Micheal Espinola Jr michealespin...@gmail.com wrote: I've seen 72 hours, but I always change mine down to 24, with warnings kicking off within an hour. I want myself and my users to know about communications problems in a much more timely fashion. -- ME2 On Mon, Oct 4, 2010 at 10:54 AM, James Kerr cluster...@gmail.com wrote: I always thought that it was 72 hours and that because our server came online before the 72 hours had expired, I was expecting a bunch of mail to flow but I was wrong. Times have changed I've discovered. Well, more reason for facilities to get the backup AC system working as a backup AC. Having it run of the same cooling tower as all the other air handlers hardly seems like a great idea considering most of the reasons the AC has been broke recently has got something to do with the tower. James - Original Message - From: Jason Gurtz jasongu...@npumail.com To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Monday, October 04, 2010 1:06 PM Subject: RE: Delivery Attempt Standard As others have noted it varies widely, but remote sites will usually try to deliver for at least a day or two before giving up. W/o looking I'm pretty confident at least one RFC recommends 3 days as reasonable but it's definitely not adhered to in all cases. If you feel/know there is some mail that is expected from biz partners etc..., research the etrn command. You could telnet to the remote site and try that command against the server so they retry delivery to you. ~JasonG -Original Message- From: James Kerr [mailto:cluster...@gmail.com] Sent: Monday, October 04, 2010 08:41 To: MS-Exchange Admin Issues Subject: Delivery Attempt Standard Quick question.. Does anyone know if there is a standard amount of time that a mail server is usually set to keep retrying to deliver email in the event the destenation server is not responding? Our exchange box was down over the weekend from Friday evening until now, due to enviromental issues [1] and we seem to be missing a lot of mail that I was kind of expecting to start coming in this morning. James [1] Our AC system is a piece of crap. --- To manage subscriptions click here: http://lyris.sunbelt- software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
