SBS 2008

I have a SBS2008 Server and SMTP forwarding to the ISP
when it gets a domain that doesn't exists it retries every minute
for hours. How can I change how many times to retry on fail.
Was SP1, now SP2 still no difference

In the Microsoft Exchange Console
Microsoft Exchange -> Server Configuration -> Hub transport
Properties -> Limits
Transient Failure Retries Interval 300 seconds
transient Failure Retry Attempts 1


> RCPT TO:<>
< 250 2.1.0 Ok,
< 450 4.1.2 <>: Recipient address rejected: Domain
not found,

The odd thing is the ISP is sending the 250 AND 450, never the less
still an error, and it retries to infinity.


Am I missing something, or is this just another Microsoft Feature.

son of a bitch wrote:

> I have a SBS2008 Server and SMTP forwarding to the ISP
> when it gets a domain that doesn't exists it retries every minute
> for hours. How can I change how many times to retry on fail.
> Was SP1, now SP2 still no difference
>
> In the Microsoft Exchange Console
> Microsoft Exchange -> Server Configuration -> Hub transport
> Properties -> Limits
> Transient Failure Retries Interval 300 seconds
> transient Failure Retry Attempts 1
>
>
> > RCPT TO:<>
> < 250 2.1.0 Ok,
> < 450 4.1.2 <>: Recipient address rejected:
> Domain not found,
>
> The odd thing is the ISP is sending the 250 AND 450, never the less
> still an error, and it retries to infinity.
>
>
> Am I missing something, or is this just another Microsoft Feature.

The remote mail server is returning a 4xx SMTP code, rather than a 5xx
code. 4xx SMTP codes indicate a *temporary* failure, therefore Exchange
will persist (until the normal timeout occurs after 1 or 2 days).

--
Steve Foster
For SSL Certificates, Domains, etc, visit.:
https://netshop.virtual-isp.net

On 2010/11/04 04:09, Steve Foster wrote:
> son of a bitch wrote:
>
>> I have a SBS2008 Server and SMTP forwarding to the ISP
>> when it gets a domain that doesn't exists it retries every minute
>> for hours. How can I change how many times to retry on fail.
>> Was SP1, now SP2 still no difference
>>
>> In the Microsoft Exchange Console
>> Microsoft Exchange -> Server Configuration -> Hub transport
>> Properties -> Limits
>> Transient Failure Retries Interval 300 seconds
>> transient Failure Retry Attempts 1
>>
>>
>>> RCPT TO:<>
>> < 250 2.1.0 Ok,
>> < 450 4.1.2<>: Recipient address rejected:
>> Domain not found,
>>
>> The odd thing is the ISP is sending the 250 AND 450, never the less
>> still an error, and it retries to infinity.
>>
>>
>> Am I missing something, or is this just another Microsoft Feature.
>
> The remote mail server is returning a 4xx SMTP code, rather than a 5xx
> code. 4xx SMTP codes indicate a *temporary* failure, therefore Exchange
> will persist (until the normal timeout occurs after 1 or 2 days).
>

Problem is: two people enter crap in the same time period the ISP
decides your a spammer and puts you on a 10 minute blocklist.
To get off the Blocklist you have to NOT send anything for 10 minutes,
and exchange just won't shut up so this block goes for half a day.

Eventually it gives up after 5 hours or more than 300 attempts!!
A 450 could be anything from a mailbox full to no bad Domain, so
what's the point of retrying every 57 seconds anyway.

Surely, I can change how often to retry or Max number of retries?
NORMAL servers, have a increasing retry delay, not fixed at 57 seconds
to Infinity and Beyond.

son of a bitch wrote:

> Problem is: two people enter crap in the same time period the ISP
> decides your a spammer and puts you on a 10 minute blocklist.
> To get off the Blocklist you have to NOT send anything for 10
> minutes, and exchange just won't shut up so this block goes for half
> a day.

The primary solution to this would be to get a decent ISP. If they're
providing smarthost facilities where you login (you do have to login,
right?), they should not be identifying you as a spammer for a few bad
messages.

> Eventually it gives up after 5 hours or more than 300 attempts!!
> A 450 could be anything from a mailbox full to no bad Domain, so
> what's the point of retrying every 57 seconds anyway.
>
> Surely, I can change how often to retry or Max number of retries?
> NORMAL servers, have a increasing retry delay, not fixed at 57
> seconds to Infinity and Beyond.

http://www.lmgtfy.com/?q=exchange+2007+retry+limits

--
Steve Foster
For SSL Certificates, Domains, etc, visit.:
https://netshop.virtual-isp.net

On 2010/11/05 01:46, Steve Foster wrote:
> son of a bitch wrote:
>
>> Problem is: two people enter crap in the same time period the ISP
>> decides your a spammer and puts you on a 10 minute blocklist.
>> To get off the Blocklist you have to NOT send anything for 10
>> minutes, and exchange just won't shut up so this block goes for half
>> a day.
>
> The primary solution to this would be to get a decent ISP. If they're
> providing smarthost facilities where you login (you do have to login,
> right?), they should not be identifying you as a spammer for a few bad
> messages.
>
>> Eventually it gives up after 5 hours or more than 300 attempts!!
>> A 450 could be anything from a mailbox full to no bad Domain, so
>> what's the point of retrying every 57 seconds anyway.
>>
>> Surely, I can change how often to retry or Max number of retries?
>> NORMAL servers, have a increasing retry delay, not fixed at 57
>> seconds to Infinity and Beyond.
>
> http://www.lmgtfy.com/?q=exchange+2007+retry+limits
>

I don't consider it a ISP problem, I consider a M$ problem
when I can't stop it retrying every 57 seconds from now to infinity.

If M$ built the SMTP server to Public Domain Standards..., it is a
Public Domain System that M$ has tried to make Propriety and ended up
neutering it.

The sender MUST delay retrying a particular destination after one
attempt has failed. In general, the retry interval SHOULD be at
least 30 minutes; however, more sophisticated and variable strategies
will be beneficial when the SMTP client can determine the reason for
non-delivery.

In article <4cd3e986$>,
says...
>
> On 2010/11/05 01:46, Steve Foster wrote:
> > son of a bitch wrote:
> >
> >> Problem is: two people enter crap in the same time period the ISP
> >> decides your a spammer and puts you on a 10 minute blocklist.
> >> To get off the Blocklist you have to NOT send anything for 10
> >> minutes, and exchange just won't shut up so this block goes for half
> >> a day.
> >
> > The primary solution to this would be to get a decent ISP. If they're
> > providing smarthost facilities where you login (you do have to login,
> > right?), they should not be identifying you as a spammer for a few bad
> > messages.
> >
> >> Eventually it gives up after 5 hours or more than 300 attempts!!
> >> A 450 could be anything from a mailbox full to no bad Domain, so
> >> what's the point of retrying every 57 seconds anyway.
> >>
> >> Surely, I can change how often to retry or Max number of retries?
> >> NORMAL servers, have a increasing retry delay, not fixed at 57
> >> seconds to Infinity and Beyond.
> >
> > http://www.lmgtfy.com/?q=exchange+2007+retry+limits
> >
>
> I don't consider it a ISP problem, I consider a M$ problem
> when I can't stop it retrying every 57 seconds from now to infinity.
>
> If M$ built the SMTP server to Public Domain Standards..., it is a
> Public Domain System that M$ has tried to make Propriety and ended up
> neutering it.
>
> The sender MUST delay retrying a particular destination after one
> attempt has failed. In general, the retry interval SHOULD be at
> least 30 minutes; however, more sophisticated and variable strategies
> will be beneficial when the SMTP client can determine the reason for
> non-delivery.

http://www.simple-talk.com/sysadmin/...nto-transport-
queues-%28part-2%29/

Take a look at that link, it explains it all.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
(remove 999 for proper email address)

On 2010/11/07 04:35, Leythos wrote:
> http://www.simple-talk.com/sysadmin/...nto-transport-
> queues-%28part-2%29/

Thanks

Have managed to change the Retry Interval through the dos prompt
which is odd (but not for Microsoft) as it changes the same settings
as the Console, except the command prompt version actually works.

I can now retry every 10 minutes for 1 hour then abort.